No consent sheet

Nothing asks the user anything: src/lib/consent.ts is a re-export of the core shim, so an undecided category reads as consented and the analytics / crash SDKs start on the first launch. What the user did say still counts: the Settings "Do not sell or share" switch (shown when an analytics module is selected) turns analytics off, and an explicit false in the consent store (src/stores/consent.ts) is honoured - a later bun run setup --consent consent keeps both. Setup picks this option when no analytics or crash module is selected; pick it by hand (--consent none) only when your app never ships to a region with consent rules.

SetupCopy Anchor Link

bun run setup --consent none

That's it - there's nothing to configure.

UsageCopy Anchor Link

import { consent } from "@/lib/consent";

consent.get(); // { analytics: true, crash: true } until "Do not sell or share" is on
consent.setDoNotSell(true); // → { analytics: false, crash: true }
consent.needsPrompt(); // always false

GotchasCopy Anchor Link

• With analytics/* or crash/sentry selected, this option means events flow from the first launch and there are no per-category switches in Settings (only "Do not sell or share", which covers analytics). In the EU/UK that needs a consent mechanism of your own; consent/consent ships one, and setup selects it for you unless you pass --consent none.

ReferenceCopy Anchor Link

Everything below is generated from modules/consent/none/module.json - the same file bun run setup reads, so it is what actually lands in your repo.

InstallCopy Anchor Link

bun run setup --consent none

Module id: consent/none.

FilesCopy Anchor Link