Privacy Policy

Last updated: 17 June 2026

TL;DR — DomainSentry collects zero data. Everything stays on your device. No servers, no accounts, no tracking, no analytics. Ever.

Data Collection

We collect nothing. DomainSentry does not collect, store, transmit, or share any personal data of any kind. Specifically:

No browsing history is recorded or transmitted
No analytics or telemetry is sent to any server
No user accounts are required or created
No cookies are set by the extension
No third-party tracking scripts are included
No data is sold, rented, or monetised in any way

Local Storage Only

All data the extension uses is stored locally on your device using Chrome's built-in storage APIs (chrome.storage.local and chrome.storage.sync). This includes your settings, your PIN hash (SHA-256 — the raw PIN is never stored), your custom blocked/allowed domain lists, and block-count statistics displayed in the popup.

This data never leaves your browser. If you use Chrome Sync, your settings may sync to other Chrome profiles you are signed into — this is handled entirely by Google's infrastructure. DomainSentry has no access to synced data and no servers to receive it.

DNS-over-HTTPS Queries

DomainSentry may optionally perform DNS-over-HTTPS (DoH) lookups to check whether an unlisted domain is categorised as adult content. These queries are sent to CleanBrowsing Family Filter and Cloudflare Family DNS.

Each query contains only the domain name being checked — no user identifiers, no browsing history, and no personal information of any kind. Results are cached locally in your browser for 24 hours and are never logged by the extension. Please see CleanBrowsing's and Cloudflare's own privacy policies for how they handle DNS query data.

Blocklist Sources

DomainSentry uses publicly available, open-source domain blocklists (StevenBlack/hosts, hagezi/dns-blocklists, blocklistproject/Lists, and others). This blocklist data is bundled with the extension at build time and processed entirely on your device. No data is fetched from these sources at runtime and no personal data is sent to them.

Permissions Explained

DomainSentry requests the following browser permissions, each used solely for its stated purpose:

Permission	Why it is needed
`declarativeNetRequest`	Applies URL blocking and redirect rules at the network level
`storage`	Saves your settings and PIN locally on your device
`tabs`	Opens the onboarding page on first install only
`alarms`	Manages temporary unlock timers (site unlocked for N minutes)
`host_permissions (<all_urls>)`	Required by Chrome for declarativeNetRequest redirect rules to work

DomainSentry does not request permissions for: browsing history, bookmarks, cookies, clipboard, notifications, webcam, microphone, or location.

Children's Privacy

DomainSentry is designed as a personal content filtering tool for adults who want to limit their own access to certain websites. It is not specifically directed at children. Because the extension collects no data from anyone, no data is collected from children either.

Changes to This Policy

If this policy is updated, the revised version will be published at this URL with an updated "Last updated" date. Significant changes will be noted in the extension's release notes on the Chrome Web Store.

Contact

For questions or concerns about this privacy policy, please open an issue on the GitHub repository: github.com/CyberSec-Sagar-Security/DomainSentry/issues

DomainSentry has no backend servers and no contact email address — all support is handled via the public GitHub issue tracker.