Booee

Privacy Policy

Effective October 30, 2026

BOOEE is a Chrome extension built to interrupt unhealthy browsing habits before they turn into regret — a pause, a verse, and the option to reach someone you trust. This page explains, plainly, what information that requires, why, and what say you have over it.

What we collect

Your account

An email address and password, handled by Supabase, our authentication provider. We never see your password in plain text — Supabase stores it hashed and BOOEE only ever receives a session token proving you're signed in.

Flagged-site activity

When you visit a site on your own blocked-sites list, or one on BOOEE's bundled default list of known adult sites, we log: the domain (for example, "example.com" — never the full page address), a one-way hash of the specific page visited (not reversible, and not the page's content), the time, and which option you chose — leave the site, contact a partner, lock your browsing, or continue anyway (continuing isn't available on sites from the bundled default list — see "Site and search filtering" below). If you answer the optional "what are you actually needing right now?" prompt, that one-word answer (e.g. "Comfort") is stored too — answering is always optional. Your dashboard's streak, "urges interrupted," and Trends figures are calculated entirely from this log, nothing separate.

Accountability partners

The name, and the email and/or phone number, of anyone you choose to add as a partner — plus your confirmation that you've already talked to them about it before adding them. We also keep a simple record each time a partner is contacted or notified — when it happened, which partner, and by which method — but not the text of what you wrote to them.

Bug reports

If you use the "Report a bug" button, we receive the message you write, the page you were on, and your account email, so we can look into it.

What we don't collect

Worth saying plainly
  • Your general browsing history. BOOEE only checks whether the current page matches a list or filter it's watching for — your own blocked-sites list, the bundled default list, Safe Search enforcement, or the explicit-keyword filter, all described below. Anything that doesn't match is never recorded, transmitted, or stored, in any form.
  • The content of pages you visit.
  • What you search for. Even when the keyword filter or Safe Search enforcement acts on a search, the search terms themselves are never sent to or stored by BOOEE — see below.
  • Advertising or analytics trackers. No Google Analytics, no Meta Pixel, no ad network of any kind.
  • A market for your data. It is never sold, rented, or shared for advertising purposes.

Site and search filtering

Beyond your own blocked-sites list, BOOEE ships these protections:

  • Bundled default adult-sites list. A maintained list of well-known adult domains, checked in addition to your own list. It is always on and can't be turned off. Sites on it are blocked at the network level — before the page loads at all — with no "Continue to Site" option, unlike your own custom list.
  • Forced Safe Search. Google, Bing, DuckDuckGo, and YouTube are locked into their own strict filtering modes on every search, using each platform's own published mechanism for network-level enforcement (the same one schools and libraries use) — not a setting on those sites you could just switch back.
  • Explicit-keyword filter. Any page whose address contains one of a small set of explicit terms is blocked before it loads, on any site — not just ones on a list. This is the one layer that can catch a site BOOEE has never seen before.
  • Explicit-search check. BOOEE also reads the words of a search — on search engines and inside sites like X, Reddit, and TikTok, where a search doesn't load a new page — and stops an explicit one the moment it's made. Searches that look like you're looking for help (for example "quit porn") are left alone, so you can research your own recovery. This runs in the same on/off setting as the explicit-keyword filter.
How this stays private

The list, Safe Search, and address checks run inside Chrome's own network-request engine (the declarativeNetRequest API), directly on your device. The search check runs in BOOEE's own code inside your browser, which does read the address of the page you're opening to decide whether it's an explicit search. In every case that happens on your device only: the URL, the domain, and the search words are not logged, stored, or sent to BOOEE or anyone else. All that's recorded is that an incident happened, when, and (for the bundled list) which known site it was. A keyword- or search-triggered block is recorded with no domain or URL at all, anywhere, including in the blocked page's own address bar.

Forced Safe Search and the explicit-keyword and explicit-search filters can each be turned off in Settings if you'd rather rely on your own list and the bundled list.

How we use it

  • The pause screen's verse comes from a public Bible reference lookup, matched to the translation you've chosen — no personal information is sent to look it up.
  • Dashboard numbers (streak, urges interrupted, weekly incidents) are computed from your own incident log and shown only to you.
  • Contacting a partner by email sends a message through our email provider, Resend, using the email you gave us.
  • Removing a site from your blocked list, or removing a partner, notifies your partner(s). When you remove a blocked site, each accountability partner is told which site you removed and, if you chose to write one, the reason you gave. When you remove a partner, that partner is sent a short notice that you removed them. Email goes through Resend; a partner who prefers text gets a pre-filled message opened in your own messaging app. The reason you type is only put in that message — we don't store it.
  • Contacting a partner by text opens your own phone's messaging app with the message pre-filled — that text is sent straight from your device. BOOEE's servers never see or transmit it.

Who we share it with

BOOEE runs on a small number of infrastructure providers, each of whom only receives what they need to do their specific job:

ProviderWhat they receiveWhat for
SupabaseAccount credentials, and all app data described aboveAuthentication and database hosting
RailwayThe requests your extension sends while you use BOOEEHosts BOOEE's server
ResendYour partner's email address, plus the site name and optional reason when you remove a blocked site, when we email themDelivers that email
CloudflareNormal web request details (such as your IP address) when you open booee.app, including the two hidden Incognito pages above; and email sent to [email protected]Hosts the BOOEE website and passes email sent to our support address on to our inbox
bible-api.comA verse reference (e.g. "Mark 4:39") and translation code — no personal dataLooks up the verse text

As with any web service, our hosting providers (Railway, Supabase, and Cloudflare) log standard technical information — like IP addresses — as a normal part of running a server. That logging happens at the infrastructure level, not something BOOEE's own code separately collects or uses.

Your controls

  • Add or remove sites from your blocked list at any time, in the dashboard.
  • Add or remove accountability partners at any time. A removed partner is sent a short notice that you removed them. Removing a blocked site also notifies your partner(s), and you can add a reason.
  • Turn the pause screen's verse on or off, and adjust your lockout duration, from Settings.
  • Turn forced Safe Search or the explicit-search filter on or off individually, from Settings. The bundled default adult-sites list is always on.
  • Delete your account entirely — see below.

Deleting your account

This is permanent

Deleting your account removes your profile, settings, blocked sites, partners, and incident history — immediately. There's no recovery window and no soft-delete. Once it's gone, it's gone.

Incognito windows

Chrome disables every extension in Incognito windows by default, and BOOEE is no exception — it won't run there unless you specifically turn on "Allow in Incognito" for it from chrome://extensions.

If you do, Chrome won't let an extension open its own pages inside a private tab, so there BOOEE shows its blocked and lockout screens on two hidden pages of our website, booee.app (/blocked and /lockout), and draws the screen over them. Loading those pages is a normal web request to our website host, Cloudflare, so it receives the usual request details such as your IP address and which of those two pages was opened. It does not receive the name of the site you tried to visit or what you searched: those details travel in the part of the address after the "#", which a browser never sends to any server.

Not for children

BOOEE deals with adult-content accountability and isn't intended for anyone under 18. We don't knowingly collect information from minors, and we'll delete any account we learn belongs to one.

Security

  • All traffic between the extension and our server, and between our server and its providers, is encrypted in transit (HTTPS/TLS).
  • Database access is restricted by row-level security, keyed to your own account — your data isn't reachable by other users' sessions.
  • The secret keys our server uses are kept as server-side settings, never inside the extension, and we replace them whenever a provider reports a security incident.
  • No system is perfect, and we can't promise absolute security, but we treat this information as sensitive and design around that.

Changes to this policy

If this policy changes, we'll update the effective date at the top of this page. We won't apply a meaningful change retroactively without telling you first.

Contact

Questions about this policy, or about your own data, can go to [email protected].