RECKN LLC ("we", "us", "our") is committed to protecting the privacy and security of our users' data. This Privacy Policy outlines how we collect, safeguard, and isolate sensitive personal information across the reckn.live ecosystem.
1. Data We Collect
To comply with high-risk payment gateway frameworks, merchant bank aggregators (Zen Payments / NMI), and federal AML protocols, we collect:
- Identity: Legal name, verified residential address, and DOB for 18+ verification.
- Contact: Phone numbers (stored in E.164 format) and email addresses.
- Financial Metadata: Transaction ledgers, stake entries, cash-out routing tokens, and historical prediction accuracy metrics.
- Technical: Cryptographic Mux stream key identifiers, IP-based geolocation, and browser device fingerprints.
2. Data Isolation & Database Security
Row-Level Security: Our database enforces strict RLS across profiles, tier_entries, payment_intents, moment_flags, and appeals_ledger.
Column-Level Grant Isolation: Sensitive operational fields — phone numbers, dates of birth, KYC status, and metrics like total_losses_cents — are blocked at the PostgreSQL grant level. They are inaccessible via standard public API queries or web inspectors.
Profile Gateway Guard: Other users can only query public profile structures (usernames, avatars). Your sensitive fields are read exclusively via a server-verified RPC (current_user_profile()). Public leaderboards omit all financial metrics.
3. Realtime Data Stream Hardening
To eliminate the risk of data sniffing, packet interception, or strategic collusion over open sockets, we have intentionally stripped transactional tables (tier_entries, payment_intents, moment_flags) out of the broad public supabase_realtime publication. Your financial entries, stake amounts, and private transaction responses are never broadcast across open websockets.
4. Third-Party Pipelines & Webhook Integrity
Mux Streaming: Video ingest data flows to Mux. Incoming payloads communicating stream connection, disconnects, or VAR clip readiness are verified via HMAC-SHA256 with timestamp replay protection against our MUX_WEBHOOK_SECRET.
Payment Tokenization: Card and bank data is tokenized client-side directly into our merchant gateway (Zen Payments / NMI). RECKN LLC never reads, processes, or stores raw card numbers.
5. Your Rights
You may request access, correction, or deletion of your personal data at any time by contacting privacy@reckn.live. We retain financial and ledger records as required by AML and tax law even after account closure.
6. California Privacy Rights (CCPA)
California residents have additional rights under the California Consumer Privacy Act including the right to know what personal information we collect, the right to request deletion of personal information, and the right to opt out of the sale of personal information. RECKN LLC does not sell your personal information to any third party. To exercise your California privacy rights contact privacy@reckn.live.