Last updated: March 19, 2026
This Privacy Policy describes how Zenito ("the Extension"), developed by Zenito Team ("we", "us"), handles user data.
Zenito is a browser extension designed to block websites based on user-defined rules, such as domain lists, time limits, and active hours. All configuration is fully controlled by the user.
We take user privacy seriously. The Extension is designed to work locally on the user's device and does not collect or transmit personal data by default.
The Extension does not collect, track, or store any personal data.
Specifically, we do not collect:
Separate from the Extension, our website may offer a voluntary contact form. If you use it, you choose to provide your email address, a reason category (e.g. support, bug report), and a message. We process this information only to respond to your inquiry, improve the product where relevant, and meet legal or security obligations.
Storage (contact form): submissions are stored in Google Firebase Firestore, a managed database service provided by Google (typically Google LLC and/or Google Ireland Limited, depending on how your data is processed under Google's terms). Google acts as a subprocessor (processor) for us solely to host those records so we can read and reply to messages. How Google handles data in connection with Firebase is described in Google's and Firebase's documentation and terms.
Legal basis (where applicable, e.g. GDPR): your consent when you submit the form (and tick the confirmation), and our legitimate interests in operating support and defending against abuse.
Retention: we keep contact submissions only as long as needed to handle your request and for a limited follow-up period, unless a longer retention is required by law. If we add further processors (for example email delivery), we will describe them here when relevant.
The Extension stores the following data locally on the user's device using the browser's storage APIs:
This data never leaves the user's browser and is not accessible to us.
When you open a blocked website, the Extension redirects you to a hosted "blocked" page (e.g. on our web app) that shows which rule blocked the URL and lets you temporarily unblock the site. When a site is temporarily unblocked, the Extension may inject a small in-page countdown overlay (e.g. "Temporarily unblocked — X:XX left") on that page. We do not use the browser's notification or alert APIs; the blocked screen and countdown are either our web page or minimal UI injected by the extension, and no visit data is sent to our servers.
For the Extension and your local configuration:
The Extension operates locally; a normal external request is loading the hosted blocked page when you are redirected there.
If you use the website contact form, the information you submit is stored in Google Firebase Firestore so we can reply (see Section 2 — Website contact form). We do not sell contact form data. Website hosting may involve additional providers that process technical data (e.g. HTTP requests) as part of normal operation.
The Extension requires the following browser permissions in order to function:
Used to save your block rules, user preferences, and activity history locally (sync and local storage). Nothing is sent to any server.
Used to detect when you navigate to a URL so we can apply blocking rules and redirect you to the blocked page when needed.
Used to redirect you to the blocked page or open the dashboard, and to re-apply blocking when a temporary unblock expires.
Used to restore blocking after a temporary unblock (e.g. "Unblock for 5 minutes") expires.
Manifest-declared content scripts are used to show the temporary-unblock countdown on pages and to communicate with the extension background. No browsing data is sent to us.
Required so the Extension can run on any site you visit: to detect navigation, redirect to the blocked page when needed, and show the countdown on temporarily unblocked pages. Blocking is based only on your rules.
These permissions are used only to provide the core functionality of the Extension.
The Extension does not use:
The website (not the Extension) uses Google Firebase only for the optional contact form, as described in Section 2. The Extension itself does not load Firebase or send your block rules or browsing data to Firebase.
If you contact us through the website contact form, you voluntarily provide an email address so we can respond.
Our website (e.g. the Zenito landing and dashboard) currently does not use cookies for tracking or analytics. We do not set first-party cookies for advertising or profiling.
If we introduce analytics, install-click tracking, or other features that use cookies or similar technologies in the future, we will update this section and may add a cookie notice or consent mechanism where required by law (e.g. in the European Union).
In the future, the Extension may introduce optional features such as:
If any feature requires collecting or transmitting data, this Privacy Policy will be updated accordingly, and users will be informed before such changes take effect.
We may update this Privacy Policy from time to time. Any changes will be published on this page, and the "Last updated" date will be revised.
If you have any questions about this Privacy Policy, please reach out using the contact form on our website.
This policy is for transparency and does not constitute legal advice. If you need advice for your situation (especially in the EU/UK or other regulated regions), consult a qualified professional.
By using Zenito, you agree to this Privacy Policy.