Privacy
Your documents deserve a clear privacy model.
PDFSwipe is designed local-first: supported tools process files in your browser, so those document bytes are not sent to PDFSwipe. This draft explains the account and service data we do handle, and what changes if cloud processing is introduced.
Last updated: August 27, 2026
What PDFSwipe processes locally
For local tools, your browser reads selected files and performs the operation on your device. PDFSwipe does not receive the PDF bytes for that workflow. The output is created in your browser and downloaded by you.
Local processing depends on your device, browser, available memory, and source file. It is not a guarantee against disclosure caused by your own device or browser extensions.
Information we receive
Without sign-in, we aim to keep the interaction local and do not need an account profile. If you create an account, we may receive your email address, Firebase user identifier, verification state, sign-in timestamps, plan state, usage counters, and support communications.
Our Firebase control plane is intended for account, entitlement, usage, reservation, audit, and privacy-request records. It is not a place where local-tool PDF contents are intentionally stored.
Authentication and providers
Current sign-in is email-based through Firebase Authentication. Firebase may process authentication and security data under its own documentation. PDFSwipe uses Firebase for identity and control-plane records; no DodoPayment integration is active at this stage.
We will publish an appropriate subprocessor list before enabling additional providers, analytics, storage, or cloud workers.
Future cloud processing
Some advanced tools may later be offered as an optional cloud workflow. Before enabling that capability, PDFSwipe should show its processing mode, limits, retention period, provider involvement, failure behavior, and deletion controls.
Until those disclosures and controls exist, PDFSwipe does not promise server-side PDF processing, OCR, AI analysis, conversion, or persistent document storage.
Retention and requests
Account and control-plane records may be retained for security, billing reconciliation, abuse prevention, and legal obligations. Retention periods will be documented more precisely as the service and payment model are finalized. We do not claim every backup or operational copy is instantly erased.
For privacy questions, access, or deletion requests, contact PDFSwipe support.
This is a practical founder-reviewed draft for PDFSwipe and is not legal advice. We will have qualified counsel review and update it before paid or cloud-processing launch. If this page conflicts with a later published version, the later version controls.