Privacy
A clear account of what Gizlet processes in your browser and what separately configured services may receive.
Local Gizlets
When a Gizlet is marked Local on its tool page, the file or text you provide to that Gizlet is processed in your browser on this device. Gizlet does not upload that marked tool input to a Gizlet server for the tool to do its job.
This promise is specific to Gizlets marked Local. It is not a blanket claim about every current or future Gizlet, and it does not prevent separate analytics or advertising requests described below.
Analytics and advertising
Analytics and advertising are separate from Gizlet processing. Aggregate analytics is measured for gizlet.app by Cloudflare, which adds its measurement script at the edge rather than from this site’s code and uses no cookies. Google Analytics is separate again: it uses cookies, it is only present when a production build configures it, and it is only loaded once you have allowed it. Advertising is disabled during development and only added to a production build when its public configuration is enabled. The current provider details are listed below so they can stay in step with the services Gizlet uses.
- Analytics: Cloudflare Web Analytics: Enabled for gizlet.app at the Cloudflare edge, it measures aggregate page views and page performance. It uses no cookies or other client-side state and does not log URL query strings. Gizlet sends it no tool events, so entered or generated tool payloads cannot reach it.
- Analytics: Google Analytics: Loaded only for a production build that configures it, and only after you allow analytics. It uses cookies. Gizlet sends it page views and a fixed list of events — a Gizlet opening, finishing, failing with a category, a download, and a step in a Flow — whose values are fixed names, whole numbers, or Gizlet identifiers. No field can carry your file, its name, its size, its format, a result, or the text of an error.
- Advertising: Google AdSense: When enabled for a production build, it serves and measures clearly labelled advertisements. Gizlet does not put tool inputs, files, results, or error messages into ad tags.
- Consent management: Google Consent Management Platform: When advertising is enabled, it presents consent choices for visitors in the EEA, United Kingdom, and Switzerland before Google serves ads that require consent.
Cloudflare Web Analytics may receive the page path, referrer, browser, operating system, device type, country, and page-performance timings for aggregate reporting. It does not log URL query strings and uses no cookies or other client-side state. When advertising is enabled, Google and its advertising partners may process a page request and information needed to serve and measure ads, including cookies or other local storage where applicable.
Analytics consent choices
Where Google Analytics is configured, Gizlet asks before it measures anything. Until you choose to allow it, and if you refuse, no request is made to Google at all — not a reduced or cookieless one. Refusing and simply not answering are treated the same way.
Your answer is remembered in your own browser and is never sent anywhere. Clearing this site’s data clears it and Gizlet asks again. Advertising storage and personalisation stay switched off whatever you choose here, and Google Analytics advertising features are disabled.
Advertising consent choices
When advertising is enabled, Gizlet uses Google’s consent management platform for visitors in the European Economic Area, the United Kingdom, and Switzerland. The consent message provides clear choices to accept, refuse, or manage advertising consent before ads that require consent are served.
Your choice may control ad storage, ad personalisation, and the use of data for advertising measurement. You can use the message’s manage-options control to review the available purposes and providers before making a choice. Gizlet’s local tool inputs and generated outputs are not used for advertising.
What Gizlet does not send as analytics
Gizlet does not send file contents, filenames, file sizes, dimensions, formats, JSON contents, generated passwords, tool results, error messages, or other entered or generated tool payloads to analytics. This is not only a policy: the events Gizlet may report are a fixed list, and every value in them is a fixed name, a whole number, or the identifier of a Gizlet. There is no field any of the above could be placed in, and an event carrying anything unrecognised is discarded rather than sent in part.
When a Gizlet fails, Gizlet may report that it failed and one of four broad categories — an input it does not support, an input too large, processing that did not succeed, or a feature your browser does not offer. It does not report the message you were shown, which can name your file.
Gizlet requests
The request-a-Gizlet form does not send its idea, use case, or optional contact field to Gizlet. It prepares a new issue on GitHub for you to review and submit yourself. If you continue and submit that issue, GitHub handles the information under its own privacy policy.
Changes to this notice
We may update this page when Gizlet’s tools or configured providers change. The current provider list and descriptions above will be updated with the service change.