ZipCount privacy policy
What ZipCount collects, what it does not, and where your text goes. Last updated: 2026-10-18.
Protect drafts with the ZipCount privacy policy: learn about local text processing and browser storage before using a shared device.
Calculation methods →How text processing fits the ZipCount privacy policy
Protect drafts with the ZipCount privacy policy: learn about local text processing and browser storage before using a shared device.
Any text or file you type, paste or open in ZipCount is processed only in your browser's memory.
Counting, keyword extraction and PDF/DOCX parsing all run as browser-side code. No text is ever sent to our servers.
When you close the page, processed data is released with memory. We cannot store your text even if we wanted to.
How the ZipCount privacy policy treats browser storage
Local text processing does not control other applications; check browser storage settings and keep your own copy of the draft.
Local text processing does not control your clipboard, extensions or other applications. For browser storage privacy, keep your own source file and check shared-device settings.
The current version uses no localStorage or cookies to save your input.
If local goal-tracking features ship later, data stays in your browser with a one-click clear option — this page will be updated first.
Data and logs
The current version includes no visitor analytics, advertising or third-party tracking scripts and sets no cookies.
The hosting provider may retain server access logs under its standard practices, including IP addresses, timestamps and request paths. Retention periods depend on the provider’s policy.
If visitor analytics are enabled in the future, we will first update this page and explain the scope of collection.
Which third parties serve ZipCount pages?
If ads or affiliate links are ever introduced, this page will list every third party and their data behavior.
How to contact ZipCount about privacy
Questions about this policy:
Last updated: