Local tools
Browser-local tools keep files on your device
Tools labelled Browser-local read your file with the browser's File API and process it in JavaScript on your device. The file is never uploaded to our servers.
Privacy
Every tool tells you whether it runs locally in your browser, on our server, or via an AI service. This page collects the rules in one place.
Last updated: 17 October 2026
Local tools
Tools labelled Browser-local read your file with the browser's File API and process it in JavaScript on your device. The file is never uploaded to our servers.
Server tools
Tools labelled Server-side upload your file over HTTPS, process it, return the result, and delete the input within minutes. Retention is capped at 1 hour. We do not train models on your files.
AI tools
Tools labelled AI send the relevant input to our AI provider to produce a response. We use providers with no-training defaults and short retention windows. The badge on each tool names the provider.
Third-party code
To keep our local-first promise honest, we vendor third-party libraries instead of loading them from a CDN at runtime. The bundles below ship from our own origin.
These are the only third-party libraries needed for tool processing. If you accept analytics, Google Tag Manager loads Google Analytics 4, Microsoft Clarity and Clicky. None of these analytics tools load before consent. We do not load third-party fonts or ads.
Cookies
Free use of the tools does not require cookies. Google Analytics, Microsoft Clarity and Clicky can set cookies only after you accept analytics.
Passes
You can buy a Day Pass or Project Pass online through Stripe Checkout. Stripe collects payment and contact details. After payment, this browser stores the pass token locally.
Ads
If we add ads, they will sit below the result area or in sidebars — never inside the upload or download steps.
Reach us
Email hello@niftywebtools.dev for privacy questions, data deletion, or to report a security issue.
First-party measurement
If you accept analytics, our /api/events endpoint adds to daily totals. It does not set cookies or store a persistent visitor ID. We never send file contents, file names, pasted text, QR contents or tool results.
What the endpoint counts
The endpoint stores daily totals for 90 days. It does not store a row for each event. The server uses your network address to limit request rates, but does not save it with the totals.
Google Tag Manager loads Google Analytics 4 after you accept analytics. GA4 measures visits and page use. It never receives your files or anything you type into a tool. Like any web request, requests to Google Analytics, Clarity and Clicky include your network address and basic browser and device details.
GA4 can set _ga and _ga_MVNSE0EX77. The second name follows Google's _ga_<container-id> pattern. These cookies contain a random browser ID and last up to two years by default. Google Analytics keeps this data for 14 months.
Microsoft
Clarity records clicks, scrolling, mouse movement and session replays. We mask all page text and inputs. This keeps tool contents and file names out of recordings.
On our domain, Clarity sets _clck for up to one year and _clsk for up to one day. These cookies connect page views to a browser and session.
Clicky
Clicky records visits and page views. It never receives your files or anything you type into a tool.
Clicky can set _first_pageview and _heatmaps_g2g_* for 10 minutes; _no_tracky_* for one hour; _referrer_og, _utm_og, _custom_data_* and aff for 30 days; and _jsuid for one year.
Your choice
Use the link below to reject analytics again. We delete known Google Analytics, Clarity and Clicky cookies from this site and its parent domain. We also deny Google analytics storage and reload the page, which stops tags that are already running.