PRIVACY.

WHAT WE COLLECT

• Submission fields: legal first and last name, public display name, optional X handle, project name, tagline, normalized destination, video metadata, and acceptance versions.
• Operational data: private management-token hash, provider identifiers, status history, abuse signals, reports, and owner audit records.
• Payment status and identifiers from Stripe. We do not store card numbers or copy Stripe billing and email fields into the product database.
• Privacy-minimized playback, visit, device, consent, and security events needed for public aggregate metrics and abuse prevention.

HOW WE USE IT

• To process and publish submissions, calculate rank, deliver media, measure views and watch behavior, handle payments/refunds, moderate content, prevent abuse, and meet legal obligations.
• Legal founder names and private provider/payment details are not returned by the public API.
• Analytics never decide rank, payment fulfillment, or moderation automatically.

STORAGE + PROVIDERS

• Structured records are stored in Cloudflare D1 and normalized videos/posters in private Cloudflare R2.
• Cloudflare Stream temporarily processes uploads; Stripe handles payment; DataFast may measure consent-aware site and business events.
• Retention is minimized, but payment, dispute, security, moderation, and legal-hold records may need to be kept longer.

YOUR CHOICES

• Founders can request a copy of founder-visible project data or submit a removal request from the private management page.
• A removal request does not require immediate deletion of financial, fraud, audit, dispute, or legal records.
• Where required, non-essential analytics load only with consent. Essential aggregate/security processing remains limited to operating the service.

BEFORE LAUNCH

Add the operating company identity, privacy contact, lawful bases, processor list, international-transfer terms, exact retention periods, and jurisdiction-specific rights before enabling live payments.