Cookie Policy

Current use

PDFDog currently uses necessary authentication session cookies supplied through Supabase so that sign-in, account, and billing features work. Local processing tools do not need a PDFDog cookie to read or upload your files. Some local workflows use temporary browser storage to pass a generated result between tools; that workspace is not sent to PDFDog and is cleaned up or expires.

Advertising and consent

Google AdSense is loaded only for eligible Free ad placements after the required production configuration exists. Google Privacy & messaging provides the official consent and privacy-choice experience; PDFDog does not use a homemade consent banner or consent string. The footer Privacy choices link reopens the provider controls when they are available. PDFDog Plus has no advertising placement.

First-party product measurement is also disabled until the application receives an applicable consent signal. It stores coarse usage categories only, not document contents, filenames, OCR output, generated files, account identity, exact location, or payment details. The owner or legal adviser must confirm the applicable lawful basis and retention periods for the final jurisdiction.

Third-party services

Stripe handles PDFDog Plus billing. Supabase handles authentication and related account data. PDF to Word uses Adobe PDF Services for temporary cloud conversion; see the Privacy Policy for that file-processing exception.

Further information

See the Privacy Policy and Terms of Service. The owner or legal adviser must complete jurisdiction-specific cookie and advertising disclosures before public launch.