Privacy Policy
This policy explains what PDFPipe collects when you use the website, the dashboard, and the API, and what we do with it. It is written to be read, not skimmed past.
Last updated: 23 August 2026
1. Who we are
PDFPipe is a PDF-URL-to-text API. Our infrastructure runs in AWS EU (London), eu-west-2. For anything in this policy, contact privacy@pdfpipe.dev.
2. What we collect
Account data. When you sign up we store your email address, name, a bcrypt hash of your password (or, if you sign in with Google or Microsoft, the identity your provider returns), your plan, billing currency, and team membership. If you enable multi-factor authentication we store the secret needed to verify your codes.
API request data. For every conversion we record the PDF URL you submitted, the output format, the processing type, timestamps, the request status, the page count, the API key ID used, and the IP address and User-Agent of the caller. We hold the fetched PDF in memory only while converting it and do not store the original file. The converted output is stored temporarily so you can download it (see retention below).
Dashboard test requests. Conversions run from the dashboard are recorded in the same way as API requests.
AI Help conversations (Starter, Pro, and Business). The messages you send to the dashboard assistant and its replies are stored against your user for 30 days after the last activity, and are sent to Anthropic to generate the reply.
Public converter. The try-it converter on this site runs a small number of conversions per visitor without an account. It uses Cloudflare Turnstile to block bots, and we record the URL, the result, and your IP address to enforce the per-visitor limit.
Contact form and support email. Your name, email address, and message, so we can reply.
Website analytics. We use Plausible, which records page views without cookies and without identifying individual visitors.
Error reports. Sentry captures errors from the website and API, which may include the request ID and technical details of what failed.
3. Why we collect it
- To run the service: authenticate you, fetch and convert the PDFs you ask for, and deliver the result.
- To enforce plan limits and detect abuse, including the SSRF and rate-limit checks on every request.
- To bill you, through Stripe, if you are on a paid plan.
- To send you account emails: verification, team invites, usage alerts, billing notices, and security notices such as a new API key being created. Product news is sent only if you opt in, and you can turn it off in account settings.
- To understand, in aggregate, how the website is used and to fix errors.
We do not sell your data, and we do not use your PDFs or their contents to train anything.
4. Who we share it with
We use the following providers to run PDFPipe. Each only receives what it needs for its job.
| Provider | Purpose | Data |
|---|---|---|
| Amazon Web Services (eu-west-2, London) | Hosting, compute, storage, queues, database, transactional email infrastructure | All account, request, and processing data |
| Stripe | Subscription billing and payments | Email, plan, billing currency, usage counts. PDFPipe never sees your full card number. |
| Resend | Sending account emails (verification, invites, usage alerts, billing notices) | Email address, name, the email content |
| Anthropic | Dashboard AI Help (paid tiers only) | The questions you type into AI Help and the conversation history for that thread |
| Cloudflare Turnstile | Bot check on the public try-it converter | Browser signals Cloudflare uses to tell humans from bots; your IP address |
| Plausible Analytics | Privacy-friendly website analytics | Page views and referrers. No cookies, no cross-site tracking, no personal identifiers. |
| Sentry | Error monitoring for the website and API | Error reports, which may include a request ID, route, and browser/runtime details |
When you submit a PDF URL, PDFPipe makes a request to that URL on your behalf. The host of that URL will see our server's request, not yours. We do not send your account details or API key to third-party PDF hosts.
We will disclose data if required to by law or to protect the service from abuse.
5. How long we keep it
- Converted output: downloadable for your plan's retention window after the request (1 hour on Free, 24 hours on Starter, 7 days on Pro, 30 days on Business). Storage lifecycle rules then delete the file; nothing is kept beyond 33 days.
- Original PDFs: never stored. Held in memory during conversion only.
- Request records (URL, status, timestamps): 90 days, then expired automatically.
- Usage counts per month: for the life of the account, for billing.
- AI Help conversations: 30 days after the last message.
- Account data: until you delete your account. Deleting your account cancels any Stripe subscription and removes your account data; billing records are kept as long as tax law requires.
- Support messages: as long as needed to resolve the request.
6. Cookies and local storage
The dashboard stores a signed session token in your browser so you stay logged in (24 hours). The pricing page stores your chosen currency. Plausible analytics does not use cookies. We do not use advertising or cross-site tracking cookies.
7. Your rights
You can view and update your account details in the dashboard, see your usage on the usage page, and delete your account from Account Settings. If you are in the UK or EU you also have the right to request access to, correction of, or erasure of your personal data, to object to or restrict processing, and to complain to your data protection authority. Email privacy@pdfpipe.dev and we will respond within 30 days.
If you use PDFPipe to process documents that contain other people's personal data, you are the controller for that data and PDFPipe is your processor. Our Data Processing Agreement covers that relationship.
8. Security
Traffic is encrypted in transit, data is encrypted at rest, API keys are stored only as bcrypt hashes, and result files are reachable only through short-lived presigned links scoped to your account. The full list is on the Security page.
9. Changes
If we change this policy in a way that matters, we will update the date at the top and, for significant changes, email account holders. Continued use after a change means you accept the updated policy.