No cookies
SnapToolz doesn't set HTTP cookies. There's nothing for them to track because there's no server-side session.
Loading…
Short version: SnapToolz uses no cookies. The few things stored in your browser are listed below — every one of them stays on your device.
Last updated: May 7, 2026
SnapToolz doesn't set HTTP cookies. There's nothing for them to track because there's no server-side session.
A handful of small string values store your preferences (theme, language, favorites). Listed in full below.
No third-party analytics by default. No ad pixels. No fingerprinting. Read the privacy page for the full story.
Open DevTools → Application → Local Storage to verify.
snaptoolz.localeYour selected interface language
Why we store it: So the site stays in your chosen language across visits
Example value: "hi" or "en"
snaptoolz.user-prefs.v1Your favorite tools, pinned tools, recent tool views, and recent searches
Why we store it: Powers the homepage shelf and the command palette suggestions — entirely client-side, never sent anywhere
Example value: { "favorites": ["/pdf/merge"], "recentSearches": ["pdf"] }
snaptoolz.install-prompt.dismissed-atTimestamp of the last time you dismissed the install prompt
Why we store it: So we don't keep nagging you for 14 days after you say no
Example value: "1717718400000"
themeYour light / dark mode preference
Why we store it: So your theme choice survives page reloads
Example value: "dark"
SnapToolz uses a service worker (the standard web platform feature) to cache the app's own JavaScript, CSS, fonts, and icons. This is what makes SnapToolz work offline and load instantly on repeat visits.
The cache contains no user data— only SnapToolz's own files. You can clear it at any time from your browser's Site Settings or by reinstalling the PWA.
We may eventually add a privacy-respecting analytics service (Plausible or Umami) to count tool views in aggregate. If/when we do, we will update this page beforeturning it on, the analytics will be cookieless and respect Do Not Track, and there will be no individual user tracking. The architecture is already in place; it just isn't wired up yet.
Your browser is in charge: