Privacy
Privacy promise
Blockk is designed for a sensitive use case. The MVP avoids accounts, databases, and browsing-history upload. Launch emails are optional and collected only if you choose to submit the website waitlist form.
| Data | Saved? | Location | Uploaded? | Delete |
|---|---|---|---|---|
| Personal blocked sites | Yes | chrome.storage.local |
No | Options > Data |
| Submitted NSFW domain | Only when you submit it | Blockk review queue |
Yes, domain only | Contact support |
| Block count and streak | Yes | chrome.storage.local |
No | Options > Data |
| Full URL path/query | No | Not stored |
No | Nothing to delete |
| Page title | No | Not stored |
No | Nothing to delete |
| Launch waitlist email | Only if you submit it | Blockk waitlist file |
Yes, by opt-in | Contact support |
Local by default
Settings, streaks, custom domains, and capped local event summaries are stored in chrome.storage.local.
Community submissions are intentional
If you submit a missed NSFW site, Blockk stores only the normalized domain and your optional review note. It does not attach the current tab URL, browsing history, page title, email, or account details.
No full URL logging
Blockk does not store the full path, query string, page title, or search text from blocked pages.
Delete anytime
The plugin Options page includes a data tab that clears local Blockk settings and progress.
Launch waitlist is optional
If you join the website waitlist, Blockk stores the email address, optional name, selected topic, and optional message you submit so we can notify you when the extension is live or reply about your request.