Privacy · launch draft

The local app stores account identifiers and private research drafts. The prepared managed-auth integration uses Supabase for verified email, Google or phone identities when enabled. Phone verification requires an SMS provider. These production services are not configured in the local preview.

Research and payments

Saved drafts include selected observed sports lines, timestamps and source evidence. Public research snapshots exclude personal entry receipts and stakes. The prepared BTCPay integration records invoice identifiers, membership terms and verification evidence. It does not request wallet seed phrases or private keys.

Sessions

Managed sessions use browser session storage. The local development login can optionally remember its session in local storage. Signing out clears the app’s stored session. Operational logs may contain account or request metadata; credentials must not be logged.

Launch requirements

Before accepting customers, the operator must publish its legal identity and privacy contact, actual service providers, retention periods, data export/deletion process, applicable rights and transfer disclosures. No production privacy or deletion workflow is represented as complete here.