RIVALFITSupport

Updated May 27, 2026

Privacy Policy

How RivalFit treats account, training, creator, referral, billing, and proof data in the public MVP.

MVP boundary

Self-published MVP policy. RivalFit is public, but this copy is not a substitute for legal, medical, tax, or financial advice.

Data We Collect

RivalFit collects account information, onboarding answers, challenge and workout activity, creator applications, referral touches, checkout metadata, webhook status, abuse-prevention signals, and proof submissions needed to run the MVP.

Billing is handled through Lemon Squeezy. RivalFit stores provider ids, subscription state, entitlement state, conversion records, and accounting ledger entries, but does not store full card details.

Proof Privacy

Proof is private by default. MVP proof may include text check-ins and private photo uploads; public proof media, health notes, and body photos are not shared by public receipt routes.

Private proof objects are stored behind server-issued upload/read/delete paths. Public share routes must use safe receipt fields only, not private proof media or health notes.

Operational Use

RivalFit may use data for authentication, workout delivery, challenge state, creator review, fraud review, rate limiting, support, billing reconciliation, and product safety.

MVP analytics and public creator/referral stats must stay preview-labeled unless provider-backed records and owner approval support the claim.

Deletion and Support

Users can request account, proof, creator, or billing-data review through the support route. Some billing, fraud, tax, or security records may need to be retained when required for legitimate operations.

This MVP policy is conservative and may be replaced by counsel-reviewed copy before broader scale.

Support and review

These pages define RivalFit's conservative public MVP policy. Formal counsel review, live-card refund operations, and public support mailbox deliverability remain operational review items.