1. About this draft
This draft covers the Flash2Hub website, customer dashboard, partner portal, and related APIs. Flash2Hub is the service name. The legal operator, business address, country of establishment, and privacy contact must be identified before this policy takes effect.
2. Information handled by the service
- Account information: name, username, email address, password hash, account role, and account status.
- Verification activity: selected services and numbers, order history, incoming SMS content, verification codes, timestamps, and delivery status.
- Payments: wallet balances, deposit and withdrawal records, wallet addresses, transaction hashes, and review information.
- Partner information: business and contact details, location, inventory, and operating information supplied during onboarding.
- Support: ticket subjects, messages, and chat history submitted through the service.
- Session and preference data: authentication cookies and browser storage used for features such as language preferences and saved services.
3. Purposes and legal grounds
These records support account access, SMS delivery, order processing, payment reconciliation, partner operations, support, and security. The final policy must map each purpose to an appropriate legal basis under the laws that apply, such as providing a requested service, meeting a legal obligation, or obtaining consent where required.
4. Access, service providers, and public transactions
SMS delivery involves the partner infrastructure providing the number. Account, order, message, and transaction records may also be accessible to staff handling operations or support according to their permissions. The final policy must identify the relevant provider categories, their purposes, hosting locations, and any international transfer arrangements.
Blockchain transactions can expose wallet addresses, amounts, and transaction hashes publicly. Removing a Flash2Hub record does not remove a transaction from a public blockchain.
5. Cookies and browser storage
Flash2Hub uses an authentication cookie to maintain browser sessions and browser storage for application preferences and continuity. Blocking cookies or clearing storage can affect login and saved settings. This draft does not establish permission for advertising or optional tracking; any such use must be assessed and disclosed before activation.
6. Retention and security
The retention periods for accounts, SMS content, verification codes, support conversations, transaction records, and backups are still being finalized. This draft does not promise automatic deletion after a fixed period. The final schedule must account for operational needs and applicable recordkeeping requirements.
Passwords are stored as hashes, and authenticated functions use access controls. No system can guarantee absolute security. Keep credentials private and avoid including unrelated sensitive information in support messages.
7. Your requests
Depending on applicable law, you may have rights concerning access, correction, deletion, restriction, objection, portability, or withdrawal of consent where consent is the basis for processing. Identity verification and lawful retention requirements may affect a request.
Existing account holders can raise privacy questions through account support. An accessible privacy contact for people without account access, the request procedure, response periods, and relevant complaint authority must be confirmed before publication as a final policy. See Contact & Support.
8. Details to finalize
Operator identity and address; privacy contact; legal bases; hosting and service providers; transfer arrangements; retention and backup deletion schedules; request handling and complaint procedures; and the effective date.