Draft · public registration remains closed

Your account.
Your control.

This is not yet a complete, reviewed privacy notice. Before public activation, the controller, address, specific service providers, legal bases, storage locations, rights and complaint channels must be completed and reviewed.

Account data in the local prototype

The prototype stores a stable member ID, random alias, registration status, consent versions and timestamps, optional update preference and invitation relationship. Email addresses are stored encrypted; lookup values use secret-keyed hashes. With Solana sign-in, only an identity lookup value is stored permanently; the wallet address appears temporarily in the signature challenge, valid for at most five minutes.

Team / downline

Confirmed members can view their own referral structure up to five levels and a maximum of 100 entries. The view shows pseudonymous member identifiers and relationships, not other members' email or wallet addresses. Pseudonymous relationship data remains personal data; access and purpose must be reviewed before launch. No commissions or guaranteed future entitlements are created.

Sessions and retention

One-time email access links are valid for 15 minutes and sessions for at most 24 hours. Session tokens are held in HttpOnly cookies; the server stores hashes. Unconfirmed accounts are cleaned up after 24 hours. Confirmed community accounts remain until deletion; a specific inactivity and retention policy must be defined before activation. The prototype retains security events for 90 days. No advertising pixels or address-book imports are present.

Language selection, invitation links and local assistant

Language selection does not use location detection or language cookies. Valid public referral identifiers and known campaign channels can be carried in landing-page URLs when changing language or opening sign-up. The prototype includes request limits using secret-keyed lookup values derived from network identifiers; providers, legal bases and retention must be documented before launch. The backoffice assistant is rule-based and runs in the browser, without an external AI service or persistent chat storage. Do not enter personal information or secrets.

Planned bot protection with Cloudflare Turnstile

The sign-in interface includes a prepared Turnstile integration. Cloudflare is not loaded in the closed preview. Only after the service is enabled and you click to load bot protection are technical connection and browser data sent to Cloudflare. The server validates the response for email access requests and wallet challenges. Access remains blocked without successful validation. The specific Cloudflare contracting entity, purposes, legal basis, data locations, retention and any transfer safeguards must be reviewed and completed before activation; this is not a completed privacy assessment.

Export, deletion and the official system

In the signed-in backoffice you can export your data and delete your account. Deletion removes active sessions and identity data; other members keep their accounts without a relationship to you. A later import into the official system is not yet implemented and will not happen automatically. An export does not grant access rights.

Backups, logs, delivery and complaint suppression, international transfers and additional rights-handling processes must be reviewed in practice and legally before publication. Local encryption cannot prevent access by a compromised running server.