Cookies
What this browser keeps, and nothing else
The current version sets no cookie at all. Two entries may be written to this browser's own storage and, after a Deep OCR read, one cache entry for the model — all of them readable by you and removable in one tap.
What is stored, exactly
Two names, and only if you do something that needs them — plus one cache entry, only if you start a Deep OCR read.
sf-consent holds your answer to the consent question, where one is required, so you are not asked again. It contains the word “granted” or “denied” and nothing else.
steadypdf.local holds what you asked this browser to remember about the tools: the tools you pinned, the last few you opened, and the settings inside a tool's options panel — a resolution, a page size, a checkbox, and which of the two Pro prices this browser was shown. It is written only when you pin something, open a tool or change a setting.
steadypdf-deep-aea46198f09e is a browser cache entry, not a cookie: the Deep reader's 660 MB model, stored in 64 MB pieces after you start a Deep read so that the next one opens without downloading it again. It holds model weights and nothing about you or any document. The Clear what this browser remembers button removes it with the rest.
It is not an account
Nothing in that entry is sent anywhere. It is never read by the page-view counter described below, it is never put into a request, and it exists only in this browser, on this device; it is not shared with another browser you use. There is nothing to sign in to, no identifier is generated, and no profile is built. The tool list on the front page carries a Clear what this browser remembers button that removes the whole entry immediately.
Your documents
Files are held in memory while the page is open and are never written to browser storage. None of the entries above ever contains a document, a file name, text taken from a document, a search term or a password — those exist only in the tab, only while you are using it.
Advertising storage, later
No advertising code runs on this build. When it does, Google AdSense and its partners may use cookies or similar storage for delivery, frequency capping, fraud prevention and measurement. In the EEA, the United Kingdom and Switzerland Google’s certified consent platform will ask first, and refusing is one tap, in the same place, in the same style as accepting.
Analytics storage
None — and that is the reason our analytics is not in the list above. Every page loads a page-view counter from our own service at analytics.pagefabrica.com, but it sets no cookie, writes no local-storage entry, keeps no session value and stores no analytics identifier in this browser. There is no client-side analytics record to clear.
The page-view fields and the eight property-free event names — work_started, work_completed and the Deep OCR preview's six — are set out in full on the privacy page. The tracker honours your browser's Do Not Track setting, and the event bridge receives no document input or result property.
Last updated when the tools change. Questions: support@steadypdf.com