01Scope and responsibility
This draft concerns information associated with portal accounts, authentication, orders, and support. The final policy would identify the organisation responsible for that information and explain how to contact it. References to a company or offering do not by themselves identify the data controller. Different organisations involved in an offering may have separate responsibilities and privacy notices.
To be confirmed
- Responsible organisation, privacy contact, applicable locations, and related notices.
02Information used by the portal
Account features use information such as your name, email address, profile details, and authentication records. Order features use selected amounts, payment methods, payment references, status, and allocation records. Support includes messages you choose to send. Depending on the enabled features, wallet addresses and account security settings may also be recorded. Avoid including private keys or unnecessary sensitive information in support messages.
To be confirmed
- Complete data inventory, collection sources, and any additional verification information.
03Purposes and account communications
The proposed purposes include creating and authenticating accounts, sending verification codes, maintaining order records, matching payment information, responding to enquiries, and investigating misuse. The final policy would connect each purpose to its applicable legal basis and explain required and optional information. Acknowledging this policy would not itself provide permission for every use of personal information or for marketing communications.
To be confirmed
- Purpose-specific legal bases, required fields, communications, and any optional permissions.
04Service providers and public records
Operating the portal may involve hosting, database, email, payment, or other service providers. The final policy would identify relevant recipient categories, their roles, and any international processing arrangements. Blockchain payments can create publicly accessible transaction records outside the portal's control. Portal account access and public blockchain visibility are separate matters; the final notice would explain this distinction for supported payment methods.
To be confirmed
- Recipients, provider responsibilities, processing locations, and transfer arrangements.
05Sessions, security, and retention
The portal uses session information to maintain authenticated access and security records to support account controls. Browser storage may retain purchase choices or payment retry information. When enabled, optional analytics uses site-specific visitor and session identifiers in browser storage and records page paths, engagement, referrer origin, campaign tags, and named button clicks. The final policy would describe the storage technologies actually deployed, their purposes and duration, and any required choices. Retention and deletion rules for accounts, orders, support messages, and security records remain to be specified.
To be confirmed
- Storage inventory, security responsibilities, retention periods, and deletion procedures.
06Requests, rights, and updates
The final policy would explain the rights available under applicable law, how to make a request, and how identity is checked before information is disclosed or changed. It would also describe any exceptions, complaint channels, and how material updates are communicated. No particular response deadline, deletion outcome, or regulatory jurisdiction is established by this preview.
To be confirmed
- Request channel, applicable rights, complaint authority, update process, and effective date.