privacy: what dimmer keeps, and what never leaves your browser
a draft, not legal advice, still being reviewed. last updated .
dimmer is a Chrome extension that makes distracting sites gray, slow and harder to open. most of it works without sending anything anywhere. this page lists everything that does leave your browser, why, and how to make it stop.
what never leaves your browser
- the pages you visit, their addresses and their titles.
- which sites you dim, which ones you added yourself, and the parts of a site you narrowed it to.
- how long you spent on each site, and which sites you opened on which day.
- the sites dimmer suggests you might dim, and the feeds you chose to hide on a site.
- dimmer’s error log: the last 50 things that went wrong in it, with every address taken out. it stays on your computer unless you copy it into an email yourself (“copy for support” in settings).
all of that stays in Chrome’s storage on your computer. if you export your settings, they go into a file you save yourself, and nowhere else.
using dimmer without an account
dimmer works without signing in, and then sends nothing about you. once a day it downloads a public list of site recipes from this website. that request carries nothing about you, though like any web request it reaches our host with your network address.
your account
signing in is optional. it’s needed for a partner, a promise, pro codes and the pro waitlist’s one tap. we keep:
- your email address. you sign in with a 6-digit code we email you; there’s no password.
- your first name, if you add one (your partner’s emails come from it), and your time zone.
- each day’s totals, summed across every site you dim: how many pauses you saw, how often you went back, how often you kept going, and how many minutes you spent. never which sites.
- your promise in your own words, and its two optional limits.
- when dimmer last checked in, and the days of a vacation you set.
- for each browser you sign in on, a random secret, kept only as a scrambled fingerprint, so removing dimmer there can tell your partner once.
- which emails we sent you or your partner, and when, so none goes out twice.
- the sign-in service’s own security records of each sign-in.
your partner
if you invite a partner, we keep their first name and email, and whether they said yes. they get, at most:
- one email asking whether they’re in. nothing more until they say yes.
- a short note on sunday evenings with your week’s totals and whether you kept your promise.
- a note on a day you break your promise, naming at most one of dimmer’s own sites (“instagram”) or just “a site you added”.
- a heads-up if dimmer goes quiet for 2 days, or is removed, and a note when you take a vacation.
they never see which pages you visit. they can stop the emails with the link in any of them, and you can remove them in settings (once they’ve said yes, that takes 24 hours, like every change that turns dimmer down).
the two waitlists
the launch waitlist (on the home page) and the pro waitlist (on /pro, or one tap inside dimmer) keep your email, where you joined, when you joined, confirmed and unsubscribed, and that you said yes (and, if you joined inside dimmer, which account you joined from). on the website you tick a box and confirm by email; inside dimmer, tapping “join” is your yes, and it uses the email you signed in with. we keep a scrambled fingerprint of the code in a confirmation link, never the code itself.
the launch waitlist gets an email when dimmer launches. the pro waitlist gets one when pro opens, with the founding price. that’s all either list is for.
pro codes
if you redeem a code for pro, we keep which code, which account used it, when, and the date pro runs until. there are no payments yet, so we hold no card or bank details. if that changes, this page will say so first.
feedback
“send feedback” in dimmer’s settings sends what you write and its category (bug, idea or other). if you tick the box, it also sends your strength setting, which switches are on and dimmer’s version. never your history, addresses or sites. we store it and email it to the person who builds dimmer. if you’re signed in, it’s linked to your account so we can reply; signed out, it isn’t, and we can’t. nothing is ever offered in exchange for feedback, a review or a rating.
keeping it safe from spam
to limit how often anyone can try a code, join a list or send feedback, we note each try against your account, or against a scrambled fingerprint of your network address, for a day, then delete it. we never store the network address itself.
what this website doesn’t do
- no analytics, cookies, tracking pixels or ads.
- our emails don’t track whether you open them or click their links.
why we keep it
- the waitlists: because you asked to be on them.
- your account, your partner and your promise: to do what you set dimmer up to do.
- the security records and spam limits: to keep dimmer safe for everyone.
we never sell or share any of it, and never use it for advertising.
who handles it for us
- Supabase stores accounts, the waitlists, codes and feedback, and runs the sign-in.
- Resend sends our emails.
- Netlify hosts this website and, like any web host, may keep short-lived server logs.
they may process data outside your country, under their own data protection terms.
how long we keep it
- your account and everything linked to it: until you ask us to delete it.
- a waitlist sign-up: until you unsubscribe or ask us to delete it. after you unsubscribe we keep the address marked as unsubscribed, only so we never email it again, unless you ask us to delete it completely.
- feedback: until you ask us to delete it. deleting your account deletes the feedback linked to it.
- spam-limit fingerprints: one day.
your choices
- every email we send, except sign-in codes, has an unsubscribe link at the bottom.
- sign out in dimmer’s settings, and that browser forgets your account.
- to see, correct or delete what we hold about you, email hello@usedimmer.com.
- if you’re under 16, ask a parent or guardian before you make an account or join a list.
changes
if this changes, we’ll update this page and the date at the top before it applies.