01
Controller, scope and roles
Hubei Laintas Technology Co., Ltd., reachable at [email protected], is responsible for the main site, unified accounts and processing whose purposes and means we determine. An enterprise customer may control its own data with Laintas acting on instructions, depending on deployment and a valid processing agreement. Own devices, self-hosted instances, contractors, merchants of record and external suppliers may have independent duties; they are not all controlled by Laintas.
02
Categories, sources and necessity
Depending on the feature, we process usernames, email, verification and login identifiers, roles and organisation relationships, sessions and device credentials, security checks, IP and technical logs, orders and subscriptions, balance and usage, support and disputes, preferences, prompts, context, file excerpts, attachments, image/audio/video, tool results, world state and content you choose to save. Hosted keys also process provider credentials you submit. Sources include you, your device, authorised login providers, payment channels and service activity. Not every category is collected for every feature. Phone numbers are processed only when an available verification or notice feature is used, including optional transaction notices; linking does not make the number a sign-in or recovery method. See the directory and feature notice for the SMS recipient.
03
Purposes and lawful bases
Necessary processing supports accounts and identity, requested delivery and authorised tools, billing, refunds, support, security and legal duties. Saving chats or files, workspace experience, publication and model training are distinguishable purposes described in the Data Use Notice. The lawful basis depends on local law and may include consent, contractual necessity, legal obligation or another statutory ground. Legitimate interests are used only where recognised and its conditions met, not as a general substitute under mainland Chinese law. General contractual acceptance is not blanket authority for extra purposes.
04
Local, cloud and device data
Helpwo browser workspaces generally use local IndexedDB; desktop and connected runtimes can access files and terminals on the selected machine. Laintas Storage, GitHub or other sync features upload the relevant data when used. Main-site chat history can sync with cloud-storage entitlement and otherwise stays in the browser. Scene stores worlds, logs and character memories on its server. Closing a page, signing out or uninstalling does not delete every copy; clearing browser storage can destroy local-only content.
05
Models, search, media and remote operations
Cloud features transmit necessary inputs and results through Laintas and the model, search, media or compute service needed for the selected function. Search processes queries and relevant page content. Voice processes audio you submit; browser or operating-system speech services have their own rules. A model name does not necessarily identify the directly contracted processor; consult the directory, feature notices and available processing information. Verify the network path even with your own model, key or machine rather than assuming no gateway is involved.
06
Hosted keys and connected services
You may have the gateway validate and encrypt provider API keys for your chosen routing. Ciphertext, labels, available models, priorities and necessary call records are stored server-side. The gateway temporarily decrypts keys for calls; encrypted storage does not mean the server can never use them. Delete the hosted source and revoke the provider key to end future use; disabling activation does not delete a key. Login and repository/drive permissions are separate; disconnecting Laintas may not revoke permissions held by the provider.
07
Experience, training and public content
Workspace experience and training are separate: experience supports continuity within the account and can contain user statements, task outcomes and summaries. CLI training capture requires a current server-recorded opt-in for covered CLI calls and does not opt other products in. Turning it off stops new capture, not automatically existing datasets; lawful deletion, restriction and other rights concerning identifiable information remain available. Issues has separate rules for training on public questions and accepted answers. See the specific notices for private streams not retained by Issues, own-key paths and organisation routes.
10
Retention and deletion scope
Retention is limited to the minimum needed for the purpose and legal requirements. Detailed main-site metered and membership usage older than 12 months is currently purged; Compute call details last 90 days and daily aggregates 400; Search request metadata currently lasts up to 400 days, with shorter internal records purged separately. Orders, core ledgers, tax, security, complaints and disputes follow their duties and open matters. Saved cloud content remains while saved and the account is used; valid deletion ends unnecessary use and clears controlled copies, with backups rotated. Public deletion cannot remove every copy held by others. Raw training-ledger pruning and imported datasets are different; the former is not the retention period of all training data.
11
Locations and international transfers
Laintas and supplier infrastructure may be in mainland China, the United States, Europe and other locations identified by the supplier or rented machine. Global services such as Cloudflare are not confined to one country. We do not promise exclusively local or domestic processing. Transfers legally involving personal information require the relevant recipient, purpose, method, categories and rights channels to be identified, required notice, separate consent and assessments, and an applicable legal mechanism or exemption. Confirm residency requirements before transmitting; model branding or interface language does not determine processing location.
12
Security, sensitive information and incidents
We apply risk-appropriate authentication, permissions, encryption, logging, credential protection and incident response, without a promise of absolute security. Do not put passwords, private keys, full card numbers or unnecessary health or other sensitive information into ordinary prompts, public questions or support. Dedicated credential fields serve their stated purpose, not public disclosure. Sensitive processing needs a specific necessary purpose, required safeguards and consent. We address suspected leakage, alteration or loss and make legally required reports and notifications.
13
Rights, closure and requests
Use in-product controls or contact [email protected] from your account email for access, copies, correction, deletion, consent withdrawal, legally available restriction or objection, portability and explanations. Complaints and court remedies remain available. Identity verification requests only necessary evidence, never passwords, full card numbers or private keys. Requests follow applicable deadlines; refusals include reasons and remedies. Closure, disconnection, stopping training, cloud deletion and local clearing are different. Legally retained financial or security data has restricted purposes. For customer-controlled data, contact its administrator; we assist within our role.
14
Children and policy changes
Processing children’s data requires the applicable age, guardian and special safeguards. Guardians may contact us for verification and requests. Guardian consent does not permit content or features prohibited by law. Material changes to purposes, categories, recipients or other matters require appropriate notice and fresh consent where legally required. Historical versions are available in the legal centre; an update does not automatically expand prior authority.
15
Content access, support and human review
Cloud processing does not make content available to every employee. Necessary support, security investigations, dispute evidence and legal handling may involve authorised people with restricted access, purpose and confidentiality duties. Remove irrelevant third-party data from support submissions; billing investigation does not require an entire repository. Sealed Issues work is ordinarily disclosed to the selected contractor; staff access must relate to a dispute, report or other lawful necessity. This is not a promise that nobody can access plaintext or that every service has automatic zero retention.
16
Making a data request
Use your account email or the product channel to identify the request, product, time range and locatable records; missing a full ID does not prevent an initial request. Identity and representative authority checks should match risk and require only necessary evidence, avoiding unrelated identity documents. Applicable legal deadlines govern. Explain reasons, scope and next steps for additional evidence, extensions or partial refusal. Ordinary requests are free; legally permitted charges or refusals for excessive or repetitive requests require an explanation. Organisation-controlled data may require its decision, with Laintas assisting within its actual role.
17
Effects of deletion, backups and exports
Closing an account does not cancel every subscription on external platforms, destroy running rentals or recall external copies of published material; address each and check its result. After required production deletion, backup copies remain isolated for recovery, security or legal purposes and rotate out; valid deletion requirements should be reapplied after restoration. Legally retained finance, dispute and security records are restricted to those purposes. Exports may exclude others’ secrets, restricted third-party material or security-sensitive information, with an explanation of exclusions. Back up local-only material before clearing storage or uninstalling.
18
Others’ data, sensitive information and accidental submission
The ability to upload a file does not authorise disclosure of all personal data within it to models, the public board or contractors. Submit only necessary excerpts and verify required authority from customers, employers and individuals. Identity, health, financial accounts, precise location and children-under-14 data can require special protection. Revoke or rotate accidentally submitted secrets at their provider and notify us to locate controlled copies; deleting a message does not secure an exposed key. Unconfirmed chat and public posting channels are unsuitable where specific confidentiality, residency or regulated safeguards are required.
19
Scope of technical retention intervals
Search currently keeps request-deduplication records for seven days, period usage for 35 days and request metadata for 400 days; metadata excludes raw queries. Compute’s 90-day details and 400-day daily aggregates concern call records, not rental disks, upstream services, client history or every ledger. Main-site 12-month detailed usage retention is likewise not a universal order-record limit. Scheduled pruning can be affected by failures, unresolved disputes or legal holds, limited to their reason and scope. Technical delay is no basis for unlimited reuse. Data without a fixed interval listed here remains subject to minimum necessary retention.