PlatformBack to platform

Document 07 of 13

Cookie and Tracking Policy

Explains cookies, local storage, SDKs, analytics, consent controls, and Global Privacy Control handling.

Status
Development draft — pending counsel approval
Audience
Website visitors, app users, viewers, and channel teams
Version
0.6
Last updated
September 12, 2026
Not approved for production

This draft is structured for legal review. Counsel must approve the responsible entity, contacts, jurisdictional scope, enforceability, and product implementation before these terms become effective.

1. Scope

This Cookie and Tracking Policy explains how OTT Platform and approved providers may use cookies, local storage, software-development kits, pixels, tags, and similar technology. It is a development draft pending a production cookie scan, consent review, and counsel approval.

The technology actually loaded by a page, player, checkout, authentication flow, channel configuration, or application controls. This Policy must be updated whenever that configuration changes.

2. Technology we may use

  • Cookies: small browser records used for sessions, security, preferences, consent, or provider functions.
  • Local and session storage: browser storage used for preferences, installation state, playback support, and similar client functions.
  • SDK and app identifiers: mobile, television, and web-app identifiers used for push, playback, security, diagnostics, and settings.
  • Pixels, tags, and beacons: requests that can measure delivery, page activity, email events, or campaign interactions.
  • Server logs and event records: request, playback, commerce, security, and operational records generated when the Service is used.

3. Strictly necessary technology

Necessary technology supports login sessions, tenant routing, load balancing, fraud prevention, bot protection, security, checkout, consent records, accessibility preferences, and requested playback. Disabling it may prevent the Service from functioning. Where law permits, it is used without optional-consent controls because it is necessary to provide or secure a requested service.

4. Functional and preference technology

Functional technology remembers choices such as language, captions, volume, playback progress, installed-app state, notification preferences, channel appearance, and device registration. Some functions may be necessary for a requested feature; others should be optional where applicable law requires consent.

5. Analytics and performance

Analytics technology measures visits, navigation, playback quality, watch progress, live attendance, errors, campaign attribution, and feature use. The intended design favors first-party, tenant-scoped, pseudonymous, or aggregated measurements and does not allow a browser event to declare revenue or payment completion.

PostHog supports optional product analytics only after measurement consent. The configured web and app integrations disable IP-based geolocation, automatic capture, session recording, surveys, and unnecessary person profiles; they send a bounded event vocabulary rather than names, email addresses, payment details, or free-form diagnostic messages.

Mux Data or similar playback diagnostics may receive player and device information. Any analytics provider must be contractually restricted, disclosed, and configured to avoid unnecessary identifiable viewing-history disclosure.

6. Advertising and sponsor technology

The current product uses first-party sponsor placement and delivery reporting rather than third-party cross-context behavioral advertising. Sponsor impressions and clicks may be measured using platform event identifiers.

Third-party advertising pixels, retargeting tags, data-broker matching, or cross-channel behavioral profiles must not be enabled without prior privacy review, updated notices, required consent and opt-out controls, and a video-privacy assessment.

7. Provider technology

Depending on configuration, Vercel or another host may support delivery; Supabase and Google may support identity; Stripe may support checkout; Mux may support video; PostHog may support consent-approved product analytics; Cloudflare Turnstile or Google reCAPTCHA may prevent bots; OneSignal may support push; and app stores may support native distribution. A provider may set or read technology necessary for its feature under its own notice.

Resend primarily handles server-sent email and is not represented as a website cookie provider merely because it is a subprocessor.

8. Consent and controls

  • Where required, optional analytics, functional, or advertising technology should remain off until consent is recorded.
  • The consent interface should offer comparably clear accept, reject, and category controls and avoid manipulative design.
  • Users may change choices through a persistent privacy control when implemented, browser settings, device settings, and application permissions.
  • Blocking cookies may sign a user out, reset preferences, or prevent checkout, playback, or other requested features.
  • Consent withdrawal applies prospectively and does not invalidate prior lawful processing.

9. Global Privacy Control and browser signals

We intend to treat a valid Global Privacy Control signal as an opt-out request for the browser or device where applicable law requires. Because there is no universally accepted standard for every other Do Not Track signal, we do not currently respond to unspecified browser DNT signals as a separate legal request.

10. Duration and updates

Cookie and identifier duration should be limited to the shortest period necessary for its category. Session records expire with the session or configured security period; consent and preference records may remain long enough to honor and evidence the choice; analytics retention follows the approved data schedule and provider configuration.

We will update this Policy after material tracking changes. Questions may be sent to dave@badburrito.com.