Business Ops Toolkit uses browser storage -- primarily localStorage and sessionStorage, not traditional HTTP cookies -- to operate the product. This page explains what we store, why, and how to control it.
| Category | Examples | Purpose | Opt-out |
|---|---|---|---|
| Strictly necessary | botk-auth-token, botk-session-user, botk-workspace-id |
Keep you signed in and scope data to your workspace. The product cannot function without these. | Not available -- required for operation. |
| Preferences | botk-theme, botk-profile, botk-settings, botk-cookie-consent, other botk-* keys |
Remember your theme, profile, integration connections, draft content, onboarding progress. | Clear via your browser's storage tools or sign out. |
| Analytics / telemetry | None currently. | When Sentry error monitoring is enabled in a future release, it will use its own storage for breadcrumbs. Enablement will be opt-in. | Decline via the cookie banner on first visit; we will respect that choice for analytics-class storage. |
| Third-party | OAuth provider cookies on their domains. | When you connect Google, Slack, Stripe, Meta, LinkedIn, etc., those providers may set their own cookies during the OAuth flow. | Manage via each provider's settings. |
botk-cookie-consent = accept or decline.To clear all Business Ops Toolkit storage in your browser:
We currently do not run third-party analytics or advertising trackers. If that changes we will honor the browser Do-Not-Track signal for analytics-class storage.