Cookie Policy

Cookies are small text files stored by your browser when you visit a website. They let the site remember things between visits — like whether you're logged in. Websites can also keep data in your browser's local storage, which works similarly but never travels with requests. We treat both with the same transparency and list both below.

That's the complete list. No personalized-advertising or remarketing cookies. No cross-site behavioral tracking. No social-media embed cookies (we don't embed any). We do not sell or share cookie data with anyone.

The consent banner governs one thing: Google ad-click measurement. Analytics needs no consent because it's cookieless and stores nothing on your device — but you can still switch it off (see below). Visitors in the UK and Europe see an equally-prominent Accept / Rejectfor ad measurement; elsewhere it's on by default and you can turn it off in Manage cookies. Closing the banner with the ✕ chooses nothing and we may ask again on a later visit.

Change your mind any time via “Cookie settings” in the page footer. The Analytics toggle there is on by default — switch it off to opt out of analytics; the Ad-click measurement toggle turns Google measurement on or off. You can also clear the _gcl cookies in your browser to remove them immediately.

The web app also uses your browser's local storage. This data stays in your browser — it is not sent to us:

• dukpdf_analytics_optout — set only if you switch analytics off, so we remember to keep it off.
• dukpdf_usage_cache… and dukpdf_pro_cache… — a local copy of your recent usage counts and plan status so the app can respond instantly and work offline; the authoritative copy lives in your account.
• pdf-signatures — signatures you save in the Sign PDF tool, stored only on your device.
• dukpdf_anon_id (fallback) — only if your browser blocks cookies entirely, the anti-abuse ID is kept here instead.
• Checkout session keys — short-lived entries that prevent a purchase from being counted twice in analytics and remember an in-progress checkout.
• Offline tool cache — a service worker caches the WebAssembly engines (for example the Office-to-PDF converter) so tools load fast and work offline. This is application code, not your data.

The desktop app uses no cookies. It does send cookieless, content-free product analytics (which tools you use — never your files or file names) by default, which you can turn off in the app's settings. It keeps a few local files in its own app-data folder (usage counts, plan cache, preferences) and stores your sign-in session in your operating system's keychain or credential manager. All of it stays on your machine, and all of it is described in the Privacy Policy.

You can block or delete cookies in your browser's settings at any time. File processing is local and doesn't depend on cookies, so the tools keep working. What's affected:

• Staying signed in— blocking the Supabase cookies means you'll need to log in each visit.
• Free-tier limits— the anti-abuse ID falls back to local storage; blocking both may make free-tier counting stricter, since we can't tell your visits apart.
• Ad measurement— stops entirely. If you've rejected it in the banner, it was never running anyway. (Analytics is cookieless, so blocking cookies doesn't affect it — opt out in Cookie settings instead.)

If we add, remove, or change the cookies or storage we use, we'll update this page and the “Last updated” date at the top. For material changes, we'll notify account holders by email.

Questions about cookies or anything in this policy? Email support@dukpdf.com. We read every message.