1. Who is responsible
This draft describes the platform’s current data handling. It does not certify compliance with any particular privacy law.
To confirm — placeholder
- Data controller’s legal identity, address, privacy contact and applicable jurisdictions — being updated.
2. Information processed
Depending on your use, records can include account and profile information, profile photos, contact submissions, training access, coaching bookings, event registrations, community posts/files, referral attribution, payment references and partner payout records.
RENDIVA does not need your cryptocurrency wallet’s private key or seed phrase. Never include those details in a contact message.
3. Purposes and communications
Data supports account access, delivery of purchased services, community moderation, support, payment reconciliation and auditable partner records. Transactional messages are distinct from marketing subscriptions.
To confirm — placeholder
- Legal basis for each purpose, consent wording and marketing opt-out procedure.
4. Service providers and security
The platform uses Lovable Cloud for hosting, accounts and data, NOWPayments for cryptocurrency payment processing, and Brevo for app transactional email. Coaching calls may use Daily. Brokers and any linked external community service have separate privacy practices.
Access controls and private storage protect restricted records. No internet service can promise absolute security.
To confirm — placeholder
- Complete provider list, processing locations, international-transfer safeguards and incident notification process.
5. Storage on your device
The site remembers your language preference using a cookie and local storage. Account sessions use browser storage for sign-in. Server API keys are not intended for browser storage.
To confirm — placeholder
- Verified cookie/storage inventory, durations, analytics usage and any required consent settings.
6. Retention and your requests
Use the contact page to ask about your information. Do not send passwords or sensitive identity documents through the general contact form.
To confirm — placeholder
- Retention periods by data category, deletion/export workflow, identity checks, request deadlines and competent supervisory authority.
Questions about this draft? Contact Tim Capital