Privacy Policy for FocusGuard Pro
Last Updated: September 9, 2025
Your privacy is critically important to us. FocusGuard Pro is designed to be a simple, effective, and private tool. This policy outlines what data the extension handles and, more importantly, what it does not.
1. Data We Do Not Collect
FocusGuard Pro is built on a “privacy-first” principle. We do not collect, store, transmit, or sell any of your personal information. This includes, but is not limited to:
- Your browsing history.
- Your search queries.
- Data you enter into forms.
- Your IP address or location.
- Any personally identifiable information (PII) like your name or email address.
The extension operates entirely on your local computer and does not communicate with any external servers.
2. Data Handled by the Extension
The only data the extension uses is stored locally on your own computer and is essential for its functionality:
- Blocklist: The extension contains a built-in, predefined list of websites to block (e.g.,
facebook.com). This list is part of the extension’s code and is not modified based on your browsing habits. - Snooze Timer State: When you use the “Snooze” feature, the extension uses the
chrome.storage.localAPI to save a single piece of information: the timestamp when your snooze period will end. This data is stored only on your local machine, is not transmitted anywhere, and is automatically deleted once the snooze period is over. This is necessary for the snooze feature to work correctly even if you restart your browser.
3. Permissions and Their Use
FocusGuard Pro requests a minimal set of permissions to function. Here is an explanation of why each one is needed:
declarativeNetRequest: Used to block the websites in the predefined blocklist. This is a privacy-safe method provided by Chrome that does not allow the extension to see or read your network traffic.storage: Used solely to save the “snooze” timer timestamp locally on your device.alarms: Used to wake the extension up after the snooze period has ended to re-enable blocking.tabs: Used to reload blocked websites that may have been left open in a tab after a snooze period ends.host_permissions: Required to redirect blocked sites to the internalblocked.htmlpage and to reload tabs. This permission is not used to read page content.
4. Changes to This Policy
We may update this privacy policy in the future. Any changes will be reflected in an updated version of the extension. We encourage you to review this policy periodically.
5. Contact Us
If you have any questions about this privacy policy, please contact us.
