Lumoswitch Privacy Policy

1. Personal information handler

The personal information handler is 泉州丰泽哈基科技有限公司. For questions, feedback, or rights requests about personal information processing, contact soraincloud@hakihakii.com.

2. Information we process

• Account and identity information: phone number, email address, username, nickname, verification status, and registration time.
• Security information: password hashes, sign-in sessions, IP addresses, device or browser information, security events, and audit records. We do not store plaintext passwords.
• Service configuration: projects, applications, routing rules, model configurations, access-key information, and upstream provider credentials you submit. Sensitive credentials are stored encrypted; the interface does not reveal their complete plaintext again.
• Calls and metering: request time, model, provider, status code, latency, token usage, platform-model billing, errors, and trace identifiers. Complete prompts and model responses are not included in ordinary call logs by default.
• Client download statistics: we retain only aggregated click counts by date, client platform and architecture, fixed source channel, and fixed placement. We do not retain IP addresses, User-Agent, Referrer, cookies, sessions, or visitor identifiers for this measurement. It represents download-button clicks, not installations or first launches.
• Agreement and preference records: to record your actual choices, we retain your account identifier, accepted Terms of Service and Privacy Policy versions, acceptance time, web or desktop source, and the enabled/disabled state and change times of optional usage analytics. We do not fabricate acceptance records for existing accounts or older clients that have not agreed.
• Optional foreground usage analytics: only after you separately enable it, we record your authenticated account identifier, usage date (Beijing time), web or desktop client type, operating-system category and application version. Records are deduplicated by day after actual foreground interaction; background residency, token refreshes and heartbeats do not count as activity. This analytics does not upload prompts, chat bodies, files, task contents, IP addresses, full User-Agent strings or hardware fingerprints. These account-linked records are personal information, not anonymous data.
• Risk-control source information: to detect unusual API calls and suspected unauthorized spending, we may process irreversible IP-address hashes, country/region and ASN information supplied by reverse proxies or CDNs, User-Agent hashes, broad client categories, and matching-rule records.
• Content-safety decisions: to meet compliance, security, and anti-abuse obligations, we may automatically check input, output, and publicly posted content. By default, we retain only decision metadata such as matched rules, direction, action, time, and related request identifiers.
• Communications and support: feedback, complaints, reports, tickets, emails, and attachments you send us.
• Model request content: clients send prompts and attachments through Lumoswitch inference services to the selected model provider and receive model responses.

3. Purposes and grounds for processing

• Creating and verifying accounts, providing sign-in and security verification.
• Providing model access, access keys, limits, and fixed/failover routing through Lumoswitch inference services, together with metering and observability.
• Protecting accounts, services, and network security; preventing fraud, abuse, and unauthorized access.
• Performing contracts, handling inquiries and complaints, and improving product stability.
• Measuring client-download entry performance in anonymous aggregate form and improving cross-channel download handoff.
• With your separate voluntary consent, using optional foreground analytics to measure web and desktop activity, retention, and operating-system and version distribution to improve the product. Necessary registration, successful model calls, token metering and billing records are processed separately on applicable grounds such as contract performance, security and legal obligations; disabling optional analytics does not stop processing necessary for core services.
• Meeting legal, regulatory, and judicial requirements.
• Where consent is required, we obtain it in the relevant context. We provide a separate notice when processing sensitive personal information or when separate consent is required by law.

4. Entrusted processing, sharing, and third-party models

We may engage cloud infrastructure, SMS, email, security, and support providers to process necessary information. Contracts, security measures, and least-privilege requirements restrict them to processing it on our instructions.

When you configure or select a model provider, we send it model requests and necessary identity or billing parameters. It may process data as an independent personal information handler under its own policies; review its terms before connecting.

We do not sell personal information. We do not provide it to other third parties except with your authorization, as necessary to perform a contract, where lawfully required, in a corporate restructuring, or in other legally permitted circumstances.

5. Cross-border processing

The mainland China edition is primarily intended for mainland China users. If you connect a model provider located outside mainland China or one that may process data overseas, your requests may be transferred abroad. Where required by applicable law, we provide notices, obtain necessary consent, and adopt safeguards. To avoid cross-border transfers, select only providers and regions that process data within mainland China.

6. Cookies and local storage

We use necessary cookies for sign-in sessions, and cookies and browser local storage for language and appearance preferences. These support sign-in, security, and basic interface functions. The mainland China edition does not currently use cookies for cross-site advertising tracking.

Agreement choices are submitted only when creating a new account, and the server records the registration versions and choice. Existing account sign-in, session restoration and agreement updates do not trigger another checkbox, agreement dialog or page restriction. Optional analytics is a separate choice, starts off, and is not overwritten by signing in.

Only when optional usage analytics is enabled, the website stores the account's most recent successfully reported date locally to reduce duplicate requests, and removes this local record when disabled. It is not used for cross-site tracking.

7. Retention periods

We retain personal information only for the shortest period needed to achieve its processing purpose. See the Data Retention and Deletion Rules for specific periods and handling after account deletion. Verification codes expire shortly; sign-in sessions, call logs, and account configurations are retained as needed for security, service delivery, and the account's lifetime.

Optional foreground activity details are retained for at most 90 days and then cleaned up. Turning off analytics for a client type stops its collection and deletes its activity details; reports change accordingly. Agreement and preference change records are retained during the account's lifetime to verify versions and consent state, then handled under the deletion rules, with only minimum evidence retained where legally required.

8. Your rights

• Access, copy, correct, or supplement personal information.
• Restrict or refuse processing, withdraw consent, or request deletion where legal conditions are met.
• You can turn off optional usage analytics for the relevant client type at any time in Privacy & usage analytics on the website or desktop client, without accepting new terms and without losing sign-in, model calls or other core features. Web and desktop choices are managed separately. Existing accounts need not reconfirm updated agreements and can still contact us about account rights.
• Delete your account and learn about automated decisions or personal information processing rules.
• Submit rights requests to soraincloud@hakihakii.com. To protect your account, we may verify your identity. We normally respond within fifteen working days.

9. Information security

We use measures such as encryption in transit, sensitive-credential encryption, access controls, session revocation, log audits, and least privilege. If a personal information security incident may affect your rights, we take remedial action and meet notification or reporting obligations as required by law.

10. Minors

The service is intended for users with full civil capacity and is not directed at people under eighteen. Contact us if you discover that a minor's information has been processed without guardian consent.

11. Policy updates

We communicate material changes through page notices, in-service notifications, or other reasonable channels. If a material change to processing purposes, methods, or information categories requires consent by law, we obtain consent again.