Legal
TBC Cookie Policy
What cookies and similar technologies TBC uses on its website and mobile apps, and how you can control them.
TBC uses a deliberately small set of storage technologies. We do not run any third-party advertising, analytics, or attribution cookies on the website or in our apps today. This policy explains what we do use, where, and how you can control it.
1. At a glance
- Strictly necessary only. The TBC website sets cookies only when they are required to keep you signed in or to remember a preference you have set on the site itself.
- No third-party advertising cookies. We do not use Google Ads, Meta Pixel, or any other third-party advertising or attribution cookie.
- First-party product analytics. We measure how Cliffs and StoryWorlds perform on TBC (plays, reactions, follows, comments, continuations) to compute the Serial Momentum Index and run our recommendations. This activity is recorded by our own backend, not by a third-party tracker, and is described in our Privacy Policy.
- The mobile apps don't use cookies. They store your sign-in token in the operating system's secure local storage; nothing is set in a browser.
- You can clear or block cookies at any time through your browser. Some site features may stop working if you do.
2. What cookies are
A cookie is a small text file that a website saves on your device so it can remember information about you between visits — for example, that you are signed in. “Similar technologies” include things like localStorage, sessionStorage, and IndexedDB inside your browser, and the secure key-value stores our mobile apps use on iOS and Android. This policy covers all of those.
3. What we use today
The TBC website (2bc.app) uses the following first-party storage. They are all set by TBC, not by a third party.
| Name | Where | Purpose | Category | Lifetime |
|---|---|---|---|---|
auth_token | Browser localStorage | Holds the Firebase ID token so you stay signed in between page loads. | Strictly necessary | Until you sign out or it expires (≈1 hour, refreshed in the background) |
auth_refresh | Browser localStorage | Long-lived Firebase refresh token used to obtain a new ID token without re-prompting for your password. | Strictly necessary | Until you sign out |
tbc_theme | Browser localStorage | Remembers your light/dark theme preference. | Preference | Until you change it or clear site data |
tbc_csrf | HTTP cookie (first-party, HttpOnly, Secure, SameSite=Lax) | Cross-site request-forgery protection on form submissions. | Strictly necessary | Session |
We do not use cookies to follow you around the web, build advertising profiles, measure third-party ad campaigns, or share information with data brokers. The activity-based analytics that power TBC's Serial Momentum Index and recommendations are computed on our own backend from your in-app actions, not by storing identifiers in your browser.
4. Mobile app storage
The TBC mobile apps do not run a web browser, so no cookies are set. Instead, the apps use the operating system's secure local storage to keep:
- Your Firebase ID and refresh tokens, so you don't have to sign in every time.
- A small set of UI preferences (e.g., theme).
- A queue of uploads in progress, so a Cliff resumes if the app is closed mid-upload.
This data is removed when you sign out, when you delete the app, or when you delete your account.
5. Third-party storage
A small number of third-party providers we use to operate the Services may set or read their own storage when you interact with them:
| Provider | Where it appears | What it sets |
|---|---|---|
| Google Firebase Authentication | When you sign in or reset your password from the website | First-party storage controlled by the Firebase JavaScript SDK to manage your sign-in state. Governed by Google's Privacy Policy. |
| Cloudflare | Whenever a video or thumbnail is loaded from media.2bc.app | Cloudflare may set a security cookie (__cf_bm) to distinguish humans from automated traffic. It does not identify you and is not used for advertising. |
6. What we don't use
For clarity, TBC does not currently use any of the following on its website or in its apps:
- Google Analytics, Mixpanel, Amplitude, Segment, PostHog, or any other product-analytics SDK or pixel.
- Google Ads, Meta Pixel, TikTok Pixel, Reddit Pixel, or any other advertising or attribution pixel.
- Sentry or any other crash- or error-reporting SDK.
- A/B testing or feature-flag SDKs that store identifiers in the browser.
- Session-replay tools (e.g., Hotjar, FullStory, LogRocket).
- Apple's IDFA or Google's Advertising ID — the apps do not request access.
If we add any of these in the future we will update this policy, present a cookie banner on the website, present an App Tracking Transparency prompt on iOS where required, and respect your choice.
7. Your choices and controls
In your browser
You can view, block, or delete cookies and site data through your browser settings. Common shortcuts:
- Chrome:
Settings → Privacy and security → Cookies and other site data - Safari:
Settings → Privacy(desktop), orSettings → Safari → Advanced → Website Data(iOS) - Firefox:
Settings → Privacy & Security - Edge:
Settings → Cookies and site permissions
Blocking the cookies and storage listed in §3 will sign you out of the site and prevent you from staying signed in on subsequent visits.
In the mobile apps
Sign out from Profile → Sign out to clear local tokens, or uninstall the app to remove all of its locally stored data.
Global Privacy Control
We honor the Global Privacy Control signal as a valid opt-out of any “sale” or “sharing” of personal information. We do not currently sell or share, but if that changes the GPC signal will be respected automatically.
Do Not Track
Browsers' “Do Not Track” signal has no industry-standard meaning, so we do not respond to it specifically. Our default is to behave as if Do Not Track is on for every visitor.
8. Changes to this policy
We may update this Cookie Policy from time to time. When we make material changes — for example, if we ever introduce analytics or advertising cookies — we will notify you on the website and through our other communication channels, and we will offer a cookie banner with granular consent where required by law.
9. Contact us
Questions about cookies or this policy?
TBC Media, LLC
4700 Belleview Avenue, Suite 300
Kansas City, Missouri 64112
Privacy: privacy@2bc.app
Related policies: Privacy Policy · Terms of Use · Cookie Policy · Content Policy