NotNow · privacy policy
What NotNow knows about you
Last updated 8 July 2026
Nothing. NotNow runs entirely inside your browser and makes no network requests, so there is no server to hold anything and no copy for anyone to ask us for.
The promise
- No personal information is collected.
- No data is transmitted to a server.
- No analytics or tracking services are used.
- Nothing is sold or shared with a third party.
- No account or login is required.
What is stored, and where
Everything NotNow saves goes into Chrome's extension storage on this device. That is the complete list:
- Your blocked websites.
- A salted PBKDF2 hash of your PIN (the PIN itself is never stored).
- Your optional PIN hint, if set, and the expiry time of any temporary unlock.
Why it asks for each permission
- Host permission (all sites)
- You choose which sites to block, so the rules cannot be limited to hosts known in advance. NotNow only checks whether an address is on your list.
- declarativeNetRequest
- Redirects blocked addresses to its own notice page instead of loading them.
- alarms
- Re-blocks a site when a temporary parent unlock runs out, which a service worker cannot do with a plain timer.
- storage
- Stores your blocklist, the hashed PIN and salt, an optional hint, and any temporary unlocks — all locally.
Children
NotNow is a tool for a parent to use. It records nothing about a child — no name, no profile, no browsing history — and transmits nothing about anyone. The only thing that exists is the list you set, on this device.
Third parties and remote code
There are none. All code, styles and fonts are bundled inside the extension. No SDK, no tracker, no advertising network, and nothing is fetched at runtime.
Keeping and deleting
You can clear the data from inside the extension at any time, and removing the extension deletes everything it stored. Because none of it ever reached us, we cannot access or recover it for you either.
Changes
If this policy changes, this page and the date at the top change with it.
Questions
Ask on X at @oxrajesh.