First-party analytics
818 uses first-party analytics to understand site traffic, subscriptions, and how members use our content and tools. We set a random visitor cookie and a 30-minute session cookie. The visitor identifier is hashed before it is stored in our database.
We record page paths, landing pages, referring domains, campaign labels, broad device and browser categories, country, account and checkout milestones, payment lifecycle events, and aggregate interactions with 818 content and tools. We do not use advertising profiles, fingerprinting, session replay, or third-party analytics.
Information we intentionally do not retain
Analytics does not retain raw IP addresses, full browser user-agent strings, URL fragments, arbitrary query strings, or free-form Play Finder search text. Administrative, coach, API, local-development, preview, bot, and Do Not Track traffic is excluded.
Retention
Raw behavioral events are retained for 90 days, session records for 13 months, and daily aggregate reports for 25 months. Stripe commerce ledger entries are kept as needed for billing, reconciliation, accounting, fraud prevention, and legal obligations.
Accounts, billing, and service providers
Account, membership, content-progress, Discord connection, and billing records are used to provide the 818 service. Payments are processed by Stripe, and application data is stored in Neon Postgres. These providers process information under their own privacy and security terms.
Uploaded video transcripts and captions
When an 818 coach uploads an instructional video directly to the service, 818 may use Vercel Blob, Vercel Workflow and Sandbox, and OpenAI to extract its audio and create a readable transcript and closed captions. Externally hosted videos are not sent through this audio-transcription process.
When a coach uses Vimeo, 818 may use Vimeo's authenticated API to retrieve an existing English caption track, copy that track to Vercel Blob, and create a readable transcript from the caption text. The Vimeo video itself is not copied or sent to OpenAI. YouTube and other externally hosted videos remain manually managed unless this policy says otherwise.
Temporary audio and processing chunks are deleted when processing finishes or reaches a final failure. The original video, final transcript, captions file, integrity hashes, and limited job records are kept with the related 818 content for playback, editing, accessibility, reliability, and cost control. Job logs and analytics do not include transcript text or private processing paths.
Partner links, codes, and attribution
When you visit an approved 818 Partner link, 818 may set a first-party referral cookie that expires after 30 days. We record the Partner code, a hashed random visitor identifier, the safe 818 landing path, an optional campaign label, and the time the referral expires. We do not give Partners customer names, email addresses, payment details, protected member activity, or raw visitor identifiers.
A valid Partner code entered on Subscribe takes priority over an older referral-link cookie. The finalized checkout and invoice determine whether the first-payment discount and Partner attribution are eligible. We use these records to apply the offer, prevent self-referrals and duplicates, calculate commissions, handle refunds or disputes, reconcile Stripe records, and investigate fraud.
Partner program and payout records
For Partner accounts, 818 keeps versioned agreement and disclosure acknowledgments, public Partner-profile details, campaign and link activity, anonymized conversion reporting, compliance actions, earnings-ledger entries, statements, transfers, and payout status. Stripe or another approved payout provider collects legal identity, bank, and tax information; 818 does not store raw bank-account or tax-ID values. Financial, contract, compliance, and payout metadata may be retained under the published retention matrix even after an eligible account closure request.
Support and lifecycle communications
We keep account-linked support messages, membership confirmations, delivery outcomes, billing-state notices, Discord fulfillment records, and privacy-request history so we can provide the service, investigate failures, answer disputes, and show what happened to an account. Transactional messages are not used to create advertising profiles. Optional marketing messages, if introduced, use separate preferences.
Data requests
Signed-in members can request an export, correction, or deletion from the Privacy & Data center. Deletion requires a recent verified sign-in. Some payment, fraud-prevention, dispute, security, and legal records may be retained when necessary even after eligible account data is deleted. Requests have a visible status and resolution history.
Your choices
Browser Do Not Track requests are honored by our analytics endpoint. You may also block or remove first-party cookies in your browser; sign-in and other account features may still require essential cookies. Use the signed-in Privacy & Data center for a verified request, or contact 818 Supportif you cannot access your account.