DAWNBLOOM Token Privacy Policy

1. Scope

This policy applies to the DAWNBLOOM Token mobile app, its official in-app browser, and official DAWNBLOOM interfaces used for authentication, device binding, and account security.

2. Our privacy principles

We follow data minimization, purpose limitation, default denial, and security by design. We do not sell personal data or use Token data for third-party advertising or cross-app tracking.

3. Data the Token actually processes

We may process the account name, linked email, verification results, session state, app version, platform and OS version, binding identifier, device public key, biometric availability, and necessary login and security logs.

3A. Country/region and city-level security data

For account recovery and protection against malicious unbinding, we may process the country/region and city-level registration location actively selected by the user and city-level historical login information derived from lawful server security records. The Token does not read GPS or precise location, store coordinates, streets, or exact addresses, or request Location permission in the background.

4. Information we do not read

The Token does not read the following by default. If you actively upload something, only the item you explicitly select is processed.

• Contacts, SMS, call history, or calendar
• Precise location, camera, or microphone
• Your full photo library or private file directories
• Browser history, clipboard history, or installed-app list
• Advertising ID, IMEI, IMSI, SIM serial, MAC address, or device serial number

5. Account and authentication data

Registration and sign-in use the unified DAWNBLOOM Account and process the account name, linked email, and password and email-code verification results. The app supports quick registration. Passwords and codes are excluded from ordinary logs, and the dynamic code is not used to sign in to the app.

6. Dynamic codes and device keys

After binding, a protected secret generates codes locally with a standard algorithm. The secret is never displayed or exposed to web pages, advertisers, or third parties. The server receives only the public key and necessary verification results.

7. Secure storage

iOS uses Keychain and Secure Enclave-compatible device keys. Android uses Keystore and encrypted secure storage. Refresh tokens, dynamic-code secrets, and private keys are not stored in ordinary files, plaintext preferences, or ordinary databases.

8. Browser and Web SSO

A signed-in app may establish an official web session with a short-lived, one-time ticket. On Android, the community and museum open in DAWNBLOOM Browser when installed; otherwise they use the in-app browser. No sensitive native bridge is exposed to JavaScript. The in-app browser shows third-party domains before opening them in the system browser.

9. Photo and file uploads

The app never scans photos or files. Only an item actively selected through the system Photo Picker or Document Picker is provided to the current official page for Community, Support, or another user-invoked function. Uploads are not used for AI training, advertising, or profiling without separate lawful authorization.

10. Camera and microphone

The current product requests neither camera nor microphone permission. Camera, microphone, and geolocation requests from web content are denied by default.

11. Minimal device information

Only the minimum app version, platform and OS version, binding identifier, public key, and biometric availability needed for security, codes, binding, and compatibility is processed. It is not used for advertising, sale, or cross-app tracking.

12. Network and security logs

To prevent abuse, troubleshoot, and protect accounts, we record necessary request times, network addresses or security digests, authentication outcomes, failure reasons, and security events. Logs exclude passwords, OTPs, dynamic codes, binding codes, refresh tokens, and private keys.

13. Cookies and web sessions

The in-app browser retains necessary dawnbloom.net security cookies, with third-party cookies disabled by default. Signing out of DAWNBLOOM Token clears its in-app browser cookies. A separately installed DAWNBLOOM Browser manages its own cookies and sign-in state; signing out of Token does not automatically erase that browser’s data.

14. Retention

One-time SSO tickets normally expire within 60 seconds and become invalid immediately after use. Sessions end on expiry, sign-out, or revocation. Login, IP, and network-security logs are retained for security and applicable legal requirements, including at least six months where Chinese cybersecurity log rules apply. Security-incident evidence remains for the investigation and 180 days after closure, or longer when law or disputes require. Account, Support, and Community records follow the corresponding unified Privacy Policy periods.

15. Deletion and account deletion

Account Management lets users request account deletion, review or revoke devices and sessions, and manage their own Community content. After lawful completion, related data is deleted or anonymized under the unified deletion process except records that must be retained by law.

Account and data deletion steps ↗

16. Third-party services

Apple and Android/Google system services provide WebView, system pickers, and biometric outcomes. Alibaba Cloud DirectMail sends email verification codes. Tokyo production infrastructure provides official account and security services. The app does not send player data to Tencent TTS and includes no advertising or tracking SDK.

17. Minors

The current formal account flow requires users to be at least 18. We do not intentionally collect minors’ data through DAWNBLOOM Token.

18. Cross-border processing

Unified DAWNBLOOM services may process data in different regions depending on registration region and formal infrastructure. Where applicable, the unified account flow provides a separate notice and required consent, with encryption, access control, and minimization.

19. Security

We use TLS, short-lived one-time tickets, purpose separation, rate limits, secure storage, device keys, log redaction, session revocation, and least privilege. No system can guarantee absolute security; contact official Support immediately if you detect risk.

20. Your rights

Through Account Management, users can review and correct supported profile data, manage devices and sessions, request account deletion, manage Community content, and submit access, correction, deletion, restriction, or complaint requests.

21. Policy updates

Material changes, such as adding location or camera use or a new sharing purpose, will receive clear notice and renewed consent where legally required. Minor editorial changes update the version or date.

22. Contact

For privacy or account-security matters, use the DAWNBLOOM Support Center or email [email protected]. Never send passwords, verification codes, dynamic codes, binding codes, or private keys by email.