1. Data Architecture: What We Collect
Rixander operates on a creator-aligned structural protocol[cite: 1]. Unlike traditional web distribution channels that harvest and sell behavioral profiles, our data collections are functional and minimized[cite: 1]:
- Account Registration & Identity: Account registration data, including names, contact emails, and voluntary user profile tags[cite: 1].
- Dynamic Telemetry & Performance Logs: Interaction tracking, including reading speeds, game state completions, and custom workshop metadata, used to calibrate ecosystem metrics and subscription pool allocations[cite: 1].
- Ledger & Web3 Wallet Data: For Lightning Network transactions, we log public wallet identifiers, invoice strings, and transaction states[cite: 1]. Rixander does not collect, store, or access your private cryptographic keys[cite: 1].
- The Forge Creator Submissions: User-generated content (UGC), including 3D asset proofs, rendering parameters, and textual manuscripts submitted to public ledger nodes[cite: 1].
2. How Data is Processed & Shared
We do not sell or monetize user data profiles[cite: 1]. Your data is used strictly to run platform utilities[cite: 1]:
- Stripe Fiat Integration: Transaction logs are shared with Stripe for card subscription processing[cite: 1]. Stripe’s privacy policy governs your credit/debit card data[cite: 1].
- Lightning Payment Integration: Wallet transaction states are processed through integrated Lightning payment rails to execute Satoshi-based micro-deposits and payouts[cite: 1].
- Influencer Telemetry Matching: Aggregate, non-identifying telemetry (such as target player genres and asset velocity) is processed to match design campaigns with active streamers without tracking personally identifiable metrics[cite: 1].
- Legal Compliance & Protection: We cooperate with law enforcement and government regulators when legally required to protect platform integrity, prevent fraudulent transactions, or comply with applicable laws[cite: 1].
3. Data Security & Node Isolation
Rixander uses digital and operational security controls to protect platform data[cite: 1]. Personal profile registries are separated from financial transaction records[cite: 1]. However, because no system can guarantee absolute security, you are responsible for maintaining the privacy of your local tokens, keys, and browser cache files[cite: 1].
4. User Autonomy & Control
Under applicable privacy frameworks (including GDPR and CCPA), you may request to view, export, or delete your account and telemetry records by contacting our support pipeline[cite: 1].