DATA HANDLING · SIMULATION / TESTNET

Beta Privacy Notice

Version dated October 16, 2026 · Beta information, subject to operator review

This notice explains the information used by the current beta application. It is a technical beta notice and must be reviewed and finalized by the responsible operator before broader public onboarding.

1. Information processed

Registration may collect name, email address, mobile number and referral code. The platform also processes login credentials through authentication services, account and security settings, simulated wallet balances, transactions, positions, referral events and administrative activity. The USDT workspace also records requested and verified amounts, receiving instructions, payment references, review status and administrator notes to reconcile deposits. USDT rewards additionally record deposit eligibility rates, spin results, Binance UIDs, payout requests, payment references, and review/audit records for manual payment reconciliation. Binance passwords, OTPs and API credentials are not required for this flow. Referral rewards record the inviter and referred account, saved attribution, review decisions, valuation rate and XLM reward ledger. Referral awards also record their credit into the main account XLM wallet. Withdrawals use the standard Account XLM workflow, which records held XLM, the saved USDT quote, Binance UID and payment decisions. Referral owners see the referred member’s name and status; email addresses are restricted to administrator review in this workspace.

2. Why data is processed

Information is used to provide member access, maintain security, simulate project activity, operate eligibility and promotional-credit features, diagnose errors, and administer the service. Current member flows do not request identity documents. Do not send passwords, OTPs or government identification through support messages.

3. Infrastructure and third parties

The current application uses Vercel for application hosting and Supabase for authentication/database services. Public market information may be requested from external providers such as Binance or CoinGecko. Media assets may be served by external image or video providers. Their processing may occur in different jurisdictions.

4. Cookies and sessions

The application uses essential authentication cookies to maintain signed-in sessions. Session cookies can contain tokens and must be protected by secure transport and appropriately configured browser settings.

5. Security and limitations

Access restrictions, server-side checks and auditing are intended to protect accounts. No service can guarantee complete security. Never share account passwords or transaction PINs in support messages or screenshots.

6. Access, deletion and retention

Account record management and retention periods need to be confirmed in the final privacy policy. Requests for access, correction or deletion should be handled by the verified platform operator through an official published contact channel. Until that contact channel is published, do not treat this beta as ready for broad collection of personal information.

7. Updates

This notice may change as integrations and operational policies evolve. Material changes should be communicated to registered members before additional collection or processing.