Privacy Policy

Local file processing

BitePDF is designed so PDF compression, previewing, editing, merging, extracting, and signing happen in your browser. For normal use, your PDF is not uploaded to our servers before export.

When a file leaves your browser

A file leaves your browser only when you choose a workflow that needs it: optional email delivery, file-link creation, storage-backed sharing, or a support case where you intentionally send a reproduction file. We do not ask you to email private PDFs for ordinary troubleshooting.

Information we process

We process only what is needed to run the service:

• Account email and sign-in status from Clerk.
• Payment status, plan, checkout, and subscription records from Stripe.
• Support messages, refund requests, and optional email export delivery through AgentMail.
• Basic technical data such as request time, browser details, and error information from hosting logs.

Support and owner notifications

Customer support messages are routed through support@bitepdf.com. Internal owner alerts are designed to include event type, workflow, route, status, counts, and safe error context only. Owner alerts should not include PDF attachments, PDF text, customer email addresses, card numbers, identity numbers, or raw filenames.

Account and payments

Clerk handles sign-in. Stripe handles payment checkout, receipts, subscriptions, disputes, and billing records. BitePDF stores only the minimum entitlement data needed to unlock paid features in the app.

Email delivery

If you request or complete paid export delivery, the finished file may be sent to your signed-in email address through AgentMail. Email delivery is optional operational delivery, not long-term file storage.

Product updates and weekly workflow emails are separate from transactional export, billing, and support emails. Marketing emails require opt-in/consent checks and include a way to stop future marketing messages.

Share links

The File Links feature is different from local PDF compression. When you choose to create a link, the selected file is uploaded to storage so a public URL can be generated. Anyone with that URL may be able to access the file, so do not create links for documents you are not comfortable sharing.

AI document agent

Pro features may send document metadata, page counts, size results, workflow settings, visible-page context, and your typed instruction to OpenAI to generate a document workflow plan. Raw filenames are minimized before the remote planner receives metadata. Full PDFs are not stored by BitePDF for AI use, and AI requests are made with response storage disabled where supported.

Cookies and local storage

Clerk uses cookies and browser storage to keep you signed in. BitePDF may use browser storage for recent work, tool state, and export context so the workspace feels fast. Clearing browser data may remove that local state.

Retention

Local files stay in your browser unless you choose email delivery, create a share link, or send files to support. Account, billing, support, share-link, and delivery records may be retained as needed for security, refunds, dispute handling, tax, and operational records.

Privacy requests

Depending on where you live, you may have rights to request access, correction, deletion, portability, opt-out, or limits on certain uses of personal information. Contact support@bitepdf.com with the request type. We will verify the request in a reasonable way before changing account, billing, or support records.

Support

Support and feedback emails go to support@bitepdf.com. Do not send highly sensitive documents over email unless you are comfortable with email delivery risk.

Your choices

You can avoid email delivery by downloading locally, cancel subscriptions through Stripe billing links, and contact support@bitepdf.com for account, support, or deletion requests.