← Quietsite

Quietsite

Privacy policy

The short version: blocking runs entirely in your browser and there is no Quietsite account. We collect anonymous usage statistics about which features get used, and nothing about where you go.

What we collect

Anonymous usage statistics, and only these: which feature was used (for example that a block was added, a focus session was started, or the block page was shown), the kind of entry added (a site, a path, or a keyword), the length of a focus session, the extension version, and a randomly generated identifier that is not linked to you or to any account. This is what tells us which parts of Quietsite are worth improving.

What is never collected: the sites on your block list, any address you visit, the content of any page, your reflections, and your strict-mode PIN. These cannot be transmitted: the reporting code accepts only a fixed list of feature names and values, so anything else is discarded before it is sent.

We honor Do Not Track, and you can turn statistics off entirely in Settings, under "Anonymous usage statistics". Statistics are processed by PostHog on our behalf.

What stays on your device

Quietsite saves these in your browser's own extension storage so it can do its job. They stay on your device and (if you use Chrome sync) sync privately through your own Google account, the same way your bookmarks do. We never receive any of it:

• Your block list and allow list.
• Your settings: schedule, focus options, themes, intention text, strict PIN (stored only as a one-way hash).
• A private count of how many blocks you hit, kept locally for the insights view.
• A custom background image, if you add one, stored locally on your device only.

What leaves your device

• In normal use, nothing. Blocking and the block page make no network requests; site icons come from Chrome's own local cache.
• Chrome Sync (optional, yours): if you have Chrome Sync turned on, Chrome syncs your settings through your own Google account, the same way it syncs your bookmarks. That is between you and Chrome; it never reaches us.
• A Pro purchase (only if you buy): the optional one-time unlock is handled by our payment provider, which receives only what is needed to complete the purchase. We never see your payment details, your browsing, or your block list.

Permissions, and why

• Host access (read and change data on websites): required to redirect a blocked site to the Quietsite block page. It is used only to apply your own block rules; pages are never read or sent anywhere.
• Storage: to save your list and settings, as above.
• Tabs: to block or unblock the current tab from the popup, and to close a blocked tab when you ask.
• Alarms: to turn scheduled blocking and focus sessions on and off at the right time.
• Favicon: to show a blocked site's icon from Chrome's own local cache. This reads only icons your browser already has, and makes no network request.

Third parties

In normal use, none. Quietsite makes no network requests for blocking, and a blocked site's icon comes from Chrome's own local favicon cache, not from any server. Nothing about your browsing or your block list is ever sent to us or anyone. The one exception is the optional one-time Pro unlock: if you choose to buy it, the purchase is handled by the payment provider named below, which receives only what is needed to complete it.

Payments

If a paid version is offered, payment is handled by a third-party processor that receives only what is needed to complete the purchase. Quietsite itself never stores or sees your payment details. This section will name the processor when a paid version ships.

Changes

If this policy ever changes, the date below will change with it.

Contact

Questions: hello@epiphani.com.

Quietsite is an Epiphani Studios app. Last updated June 2026.