A free, no-account, no-server toolkit for making yourself a harder, more expensive target
for surveillance and data-harvesting. Static site (Astro + Svelte islands) — nothing you
enter here is ever transmitted anywhere. Your profile and progress live only in this
browser's local storage. (The one exception: aggregate, cookie-free page-view analytics —
see ANALYTICS.md for exactly what that does and doesn't collect.)
This is the umbrella site: Opt-Out (data broker removal — the first section, and the one this repo currently implements) sits alongside planned sections on hardening your own devices (phone, laptop/desktop) and other tools for reducing your footprint. It replaces an earlier single-purpose opt-out-only tool of the same name.
The broker dataset the Opt-Out section consumes lives in its own repo,
data-broker-registry — deliberately
separate so it can be reused by other tools, run locally, or forked independently of this
site.
- No server touches PII. Fully static; all logic is client-side. The one thing that
does leave the browser is an aggregate, anonymous page-view ping (see
ANALYTICS.md) — it never carries anything fromprofileStoreorprogressStore, and no event is ever tied to which broker or hardening item a visitor interacted with. - Verifiable. Open source, and the broker dataset's content hash is pinned into this
build and checked against the fetched data on every load — see
src/lib/dataset/fetchAndVerify.ts. - No account, no signup.
- The dataset is a commons, decoupled from this app — see the
data-broker-registryrepo'sdata/brokers/andbroker.schema.json. This app only ever fetches the compiled, hash-pinned artifact, never the raw source. - PII never enters a URL. No query-param prefills, anywhere, ever.
npm install
npm run dev # localhost:4321
npm run build # static output to ./dist/
npm run test # vitest — crypto, dataset integrity, CCPA template, badge contract
npm run astro checksrc/lib/crypto/exportImport.ts— WebCrypto (PBKDF2 + AES-GCM) profile/progress backup, encrypted by default.src/lib/dataset/fetchAndVerify.ts+src/data/dataset-manifest.ts— fetches the broker dataset and verifies its content hash against the pin baked into this build. Fails loud (a visible banner), not closed — a stale pin shouldn't deny service to real users.src/lib/templates/ccpaRequest.ts— composes the auto-tier CCPA opt-out email; falls back to a downloadable.emlwhen the request is too long for amailto:link.src/stores/profile.ts,src/stores/progress.ts— the two local-storage-backed Svelte stores everything else reads from.src/components/BrokerRow/— one row-shell + three tier-specific action components (auto/assisted/guided), plus the purebadgeContract.tsthat the unverified-badge contract test checks against.
public/data/brokers.json is a copy of the compiled artifact from the
data-broker-registry repo's dataset
pipeline. Updating it is a deliberate two-step process: copy the new data/brokers.json,
then update src/data/dataset-manifest.ts's datasetVersion/contentHash to match — never
one without the other.
See ANALYTICS.md — aggregate, cookie-free page-view analytics via
Plausible. Page views only; no event is ever wired to broker-row or hardening-checklist
interactions.
See DEPLOYING.md — static, hosted via GitHub Pages at
become-expensive.transparencycascade.org.
See CONTRIBUTING.md for the constraints that shape this codebase (PII-in-URL rules,
dataset-pin update process, the badge-contract test) before opening a PR.
MIT. See LICENSE. The broker dataset itself is licensed separately (CC BY-NC-SA 4.0) in
the data-broker-registry repo.