The short, honest version.

Last updated: 14 July 2026 · Applies to SimpleQuiet Studio and every tool we make; per-tool specifics below.

We do not collect, store, sell, or transmit your personal data or your browsing activity. Full stop. That is the standard for every SimpleQuiet tool. This policy has two parts: the commitments that apply to all of our software, then the specifics for each individual tool (today, that's just Blinkers).

Part 1 · Applies to all SimpleQuiet tools

What we collect

Nothing. We run no analytics that can see what you browse, embed no third-party tracking scripts, and operate no server that receives your data. We have no user accounts, so there is nothing for us to hold about you.

Where your data lives

Everything our tools need is stored locally in your own browser, on your device. If you enable Chrome's built-in settings sync, your preferences may sync across your own signed-in browsers through Google — never through us.

Payments

If you buy a paid upgrade, the transaction is handled entirely by Lemon Squeezy as the seller (merchant of record). They collect and process your payment details; we never see or store your card information. We receive only what's needed to issue and honour your licence. Lemon Squeezy's handling of your payment is covered by their own privacy policy.

Children

Our tools are general-purpose and not directed at children under 13. We collect no data from anyone, children included.

Changes

If this policy ever changes, we'll update the date above. Our direction is fixed: collect nothing, track nothing, respect you.

Contact

Questions about privacy? Email hello.simplequiet@proton.me.

Part 2 · Blinkers, specifically

Blinkers is built so that it cannot see the sites you visit — not merely so that it promises not to. Here is exactly what it can and cannot access.

Where Blinkers stores your data

Your blocklist, timer settings, hard-mode preference, and focus streaks are stored locally in Chrome's storage area, on your device — as described in Part 1.

Permissions, and exactly why each one exists

declarativeNetRequest — lets Blinkers block the sites on your blocklist using Chrome's own rules engine, on your device. This mechanism deliberately does not reveal to us — or to the extension — which sites you visit.
storage — saves your settings and stats locally, as described above.
browsingData — used for one narrow purpose: clearing the cached service-worker data of sites on your blocklist, so a cached copy can't slip past a block. It is scoped to those blocked sites only and never touches your cookies, history, passwords, or any other site's data.
alarms — used by scheduled blocking (a Pro feature) to turn blocking on and off at the times you set.

Blinkers requests no host permissions and no access to your history, tabs, or the content of pages you visit. It cannot read them.

Network activity

The free version of Blinkers makes zero network requests. It does not call any server, ours or anyone else's.

The only time Blinkers ever contacts the network is if you buy the optional Pro upgrade: once, to verify your licence key. That single check is handled by Lemon Squeezy, who validates the key. It confirms only that a licence is valid — it carries none of your browsing data.