Lumoswitch Legal
English translation for reference. Use the language switch to consult the original Chinese text. The operator's official name is 泉州丰泽哈基科技有限公司.
Lumoswitch Data Retention and Deletion Rules
These rules explain the grounds for retaining account and service data, deletion methods, and handling after account deletion.
1. Basic principles
- Minimum necessity: no long-term storage for unclear purposes or purposes unrelated to the service.
- Time limits: delete or anonymize promptly once the purpose is fulfilled, the account is deleted, or the legally required period ends.
- Secure deletion: deleted data cannot be recovered with normal product or operations tools; anonymization, where required, is irreversible.
- Verifiability: retain necessary status and audit trails for deletion requests, reviews, and actions until deletion is complete.
2. Retention while an account exists
- Account identity, projects, configurations, keys, and upstream credentials: retained until you delete the relevant data or account deletion is complete.
- SMS and email verification codes: normally expire within five minutes. Sending times, verification outcomes, and attempt counts may be retained during a short security window to prevent abuse.
- Sign-in sessions: retained during their validity and invalidated on sign-out, manual revocation, security action, or approval of account deletion.
- Optional foreground usage analytics: activity details are retained for at most 90 days; turning off analytics for a client type stops its collection and deletes its activity details. Agreement versions, acceptances and preference changes are retained during the account's lifetime to verify consent and handle rights requests, with only legally necessary evidence retained after deletion.
- Call, metering, and audit records: used during the account's lifetime for observability, security tracing, usage accounting, and dispute handling. Ordinary logs do not include complete prompts or model responses by default. Security-audit and network-operation logs may be retained for at least six months where legally required, or as needed for security incidents, disputes, or accounting.
- Content-safety decision records: used for compliance evidence, abuse handling, policy tuning, and appeal review. Normally only metadata such as rules, actions, direction, and related request identifiers is retained. Complete model requests or responses are not retained unless required by law, needed for a security investigation, or separately submitted by you.
- Feedback, complaints, reports, and support records: retained until the issue is resolved or further handling is no longer needed.
3. Handling after account deletion
We review and process deletion requests within ten days. Once an administrator approves a request, account sign-in is disabled immediately and all active sessions are revoked.
When deletion is complete, we delete account identity, contact details, sign-in credentials, access keys, upstream credentials, projects, applications, model resources, routing rules, community content, and support information. Account identifiers are removed from call, metering, audit, and accounting records, or those records are irreversibly de-identified, leaving only the minimum needed for legal, accounting, security, or dispute-handling purposes.
After deletion or de-identification in production systems, corresponding backup data is cleared through backup rotation, overwriting, or disaster-recovery retention cycles. We do not use backups to restore identifiable data for deleted accounts except for legal requirements, security incidents, or disaster recovery.
If laws, regulatory orders, tax or accounting rules, or active disputes expressly require continued retention, we isolate only the legally required minimum and delete or further de-identify it when that period ends. It is no longer used for routine product operations or marketing.
4. Third-party data
Model, SMS, or email providers you use may retain received data under their own rules. We send deletion instructions to entrusted providers or require deletion under contract, but cannot exercise an independent third party's control over data on its behalf. You may also request deletion directly from the relevant third party.
5. Deletion requests and evidence
In addition to the account-deletion interface, you may request deletion at soraincloud@hakihakii.com. We verify account identity to prevent fraudulent deletion. Enterprise customers requiring deletion certificates, specific retention periods, or backup-clearing arrangements should agree these separately in an order or DPA.