Privacy Policy

Tiếng Việt

Draft pending legal review. This page is a working draft of CrawlPipe's Privacy Policy. It is not legal advice and has not yet been reviewed by a qualified Vietnamese lawyer. The operator must have this document reviewed (including for compliance with PDPL 91/2025 and any other applicable data protection law) before relying on it for a commercial launch.

Last updated: 2026-07-26.

This Privacy Policy describes what data CrawlPipe ("we", "us", "our") collects through the CrawlPipe API, MCP server, and portal (the "Service"), why we collect it, and how you can exercise your rights over it.

What we collect

Account data. When you sign up, we store your email address, a password hash (never your plaintext password), and your organization membership(s) and role (owner/admin/member).
API keys. Keys are generated in the format dp_live_…. We store only a sha256 hash of each key, never the key itself — the full key is shown to you exactly once at creation and cannot be recovered or displayed again afterward.
Usage and billing data. Every metered API/MCP request generates a usage_event row (endpoint, unit cost, HTTP status, timestamp) and rolls up into monthly usage counters shown on your dashboard, used for quota enforcement and billing.
Query telemetry. We separately record telemetry about which endpoints and query shapes are used (see the dedicated section below).
Webhook configuration. If you configure a webhook, we store the URL you supply and the signing secret we generate for it, so we can deliver HMAC-signed event payloads to that URL.
Emails you send us. Support or contact correspondence you send to [email protected] is retained to respond to and resolve your request.

Why we collect it (purpose)

We process this data to: operate your account and authenticate your requests; meter and bill usage against your plan; detect and prevent abuse of quotas, rate limits, and metering; deliver webhook notifications you configured; send you transactional communications about your account; and understand aggregate usage patterns so we know what to build next. We do not sell personal data, and we do not use your account or usage data for advertising.

Query telemetry — pseudonymized, not anonymous

To understand how the API and MCP server are actually used, we retain telemetry for each query: the endpoint called, normalized request parameters, the caller's plan, response latency, and result count. To identify repeat callers without storing your API key or account identifier directly in this telemetry table, we compute a caller hash using sha256 salted with a value that rotates monthly (telemetry_query.caller_hash). This lets us tell "the same caller queried X twice this month" apart from "two different callers each queried X once," and lets us see usage trends across months without a single persistent identifier following a caller indefinitely.

We want to be direct about what this means: this is pseudonymization, not anonymization. A monthly-salted hash of a caller identifier is not the same as removing the ability to distinguish callers — it is a technique to limit unnecessary correlation and reduce the sensitivity of the retained data, not a claim that the telemetry is impossible to link back to an account. If required (for example, in response to a verified data subject request or a legal obligation), we can correlate a given month's caller hash back to the account that generated it, because we control the salt and the hashing process.

Payment processing via PayPal

Paid subscriptions are processed by PayPal. When you subscribe, PayPal collects and processes whatever payment information it requires to run the subscription (card or bank details, PayPal account information). CrawlPipe does not receive, process, or store your card or bank account details — we receive only subscription status, identifiers, and billing lifecycle events (activated, past due, cancelled) from PayPal via its API/webhooks, which we use to keep your plan and quota in sync. Your relationship with PayPal for payment purposes is governed by PayPal's own privacy policy and terms.

Cookies

The portal sets two functional cookies: dp_session (your signed-in session) and a CSRF protection cookie used to validate state-changing form/API submissions from the portal. Both are strictly functional — required for the portal to work — and neither is used for advertising, cross-site tracking, or third-party analytics. We do not currently load third-party advertising or analytics cookies on the portal.

We share data with the minimum set of parties needed to run the Service: PayPal for payment processing (see above); infrastructure/hosting providers that run our database and application servers; and, if you configure one, the webhook endpoint URL you supply, which receives the event payloads you asked to receive. We do not sell personal data to third parties or share it for their independent marketing purposes.

Retention and deletion

Account, key, usage, and webhook data are retained for as long as your organization exists, to support billing history, usage dashboards, and reconciliation. Deleting an organization (available to owners from Settings) revokes and removes its API keys, removes its webhooks, and removes its pending invites and members — this is immediate and applies to the records tied to that organization. Query telemetry rows are identified only by the monthly-salted caller hash described above, not by a directly reversible account identifier, and are retained separately from account records for product-usage analysis. To request deletion or correction of your account data outside of deleting your whole organization, contact us as described below.

PDPL 91/2025 — your rights

Vietnam's Personal Data Protection Law (Nghị định/Luật số 91/2025), in force from 1 January 2026, gives individuals rights over their personal data, including rights to access, correct, and request deletion of personal data held about them, and to be informed about how it is processed. To the extent PDPL 91/2025 applies to data we hold about you (primarily your account data: email, name, organization role), you can exercise these rights by contacting us at [email protected]; we will respond to verified requests within the timeframe the law requires.

Corpus exclusion of documents naming individuals

Separately from account/personal data above: the legal-document corpus itself is filtered so that văn bản cá biệt (individual/case-specific administrative decisions that name private individuals — e.g. a decision addressed to one named person) are excluded from ingestion. This filter exists specifically to keep the corpus limited to normative legal documents (laws, decrees, circulars and similar general-application instruments) and to avoid processing personal data about private individuals through the corpus pipeline. If you believe a document naming an individual has nonetheless been ingested, please report it to us so we can investigate and remove it.

Security measures

We apply the following measures, among others: API keys are never stored in plaintext, only as a sha256 hash; webhook payloads are signed with HMAC using a per-webhook secret so receivers can verify authenticity; all API, MCP, and portal traffic is served over TLS; and database access is restricted to the application's own service layer. No security measure is perfect, and we cannot guarantee absolute security of any transmission or storage system, but we design around these controls as a baseline.

Contact and complaints

Questions, data subject requests, or complaints about this Privacy Policy can be sent to [email protected]. We aim to acknowledge inbound privacy requests promptly and to resolve them within the timeframe applicable law requires.