Cookie policy

Small, purposeful use of browser storage.

PDFSwipe aims to use only storage and cookies needed to operate local tools, authenticate accounts, protect sessions, and remember settings.

Last updated: August 27, 2026

Local browser storage

Local tools may use temporary browser memory, object URLs, cached application code, or browser storage to display files and prepare downloads. These artifacts are controlled by your browser.

Clearing storage can remove preferences or interrupt a workflow. It does not necessarily remove files downloaded to your device.

Authentication cookies

When you sign in, PDFSwipe may use necessary session cookies to maintain your application session and protect account routes. Firebase Authentication may use its own necessary storage. These are not optional advertising cookies.

Analytics and advertising

No DodoPayment checkout, advertising cookie program, or current cross-site advertising system is represented by this draft. If optional analytics or advertising is introduced, this page and consent experience will be updated where required.

Your choices

You can block or clear cookies and site storage through your browser. Blocking necessary storage may prevent sign-in or account features, while supported local tools may continue without an account.

Questions

For a storage or cookie question, use Contact PDFSwipe.

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.