01
Fulfilling your request
Necessary inputs, context and results may pass through Laintas, the chosen source and necessary downstream to answer, use authorised tools, search or process media. Choosing a model does not authorise unlimited purposes. Ensure authority over context and confirm deployments and recipients for confidential or residency-bound material. Own keys can still use the gateway and charge your provider account; charging and processing are separate questions.
02
Saving chats, files and worlds
Browser databases, desktop files, remote machines, Laintas cloud storage, third-party repositories and Scene worlds are separate stores. Sync creates another copy and sign-out does not delete it. Non-retention in one component does not mean a zero-retention chain: an Issues private answer returned to main-site chat can still be saved as chat history.
03
Workspace experience and long-term memory
Gateway experience supports continuity within an account workspace, separately from training sharing. Current code can derive user statements, action summaries and outcomes from completed CLI, CLI Windows and Helpwo turns, summarise them and reuse them in later context. It is not merely usage metadata and may use additional summarisation models; summaries are not guaranteed to exclude every secret. Use available controls or support for access, correction, deletion and stopping unnecessary processing. Manage local memories and gateway experience separately.
04
Opt-in CLI training data
Current cloud training requires a current server-side opt-in and covers the corresponding CLI and CLI Windows inputs and outputs actually observed by the gateway, potentially including excerpts, tool catalogues, context and trajectory links. Use /training status, /training on and /training off; /training local is separate local capture. Understand the scope and ensure authority before opting in, including employer and client restrictions. Pseudonymisation and credential scrubbing reduce risk but do not guarantee complete anonymisation.
05
Issues public-content training
Public questions and accepted answers follow a different authority from CLI: the Issues licence expressly provided and validly accepted before posting or answering permits lawful selection and training and is not automatically controlled by the CLI switch. Anonymous display names do not anonymise content. Sealed task context, Issues private streams and unlicensable third-party material are excluded. New permissions do not apply retroactively to older content lacking valid authority. Personal information needs its own lawful basis and consent where required.
06
Own keys, Compute and organisation routes
Current own-key gateway paths bypass Laintas experience and training capture. Own-machine Compute call-detail tables do not persist inference bodies. Organisation and self-hosted paths follow their deployment and do not generally inherit a personal CLI training choice. The requesting client, chosen provider or device can still keep its own history. These paths retain necessary usage, billing, security and legal records.
07
Stopping capture, deleting samples and trained models
Stopping future capture, deleting raw records or imported samples and reversing a trained model’s influence are different. Switching off does not automatically delete earlier data, without excluding legal deletion or restriction rights. Contact support with account, source, time range and scope, without sending unnecessary secrets as proof. Identifiable samples and derived copies are reviewed under law. Per-sample reversal of trained effects cannot be guaranteed, and technical difficulty does not automatically remove legal duties.
08
Retention, review and rights
Transient inference, usage ledgers, experience and datasets have different retention. Raw-ledger pruning only affects eligible rows; imported datasets follow project purpose and law, so the ledger interval is not a universal training-data limit. Keep data only as needed for valid purposes. Security scrubbing and authorised review may expose content, within restricted access and purposes. Request scope and basis under the Privacy Policy; new purposes require applicable notice or consent.
09
Check each purpose, not a single switch
This table distinguishes major paths; this notice and product rules define their scope. Disabling training does not automatically disable chat sync, experience, publication or third-party processing. Buying membership or saving a conversation does not itself opt you into training.
| Purpose | Content and trigger | Controls and limits |
|---|---|---|
| Fulfil a request | Current request, necessary context and tool results | Feature/source processing; not training authority |
| Storage and sync | History/files in local or chosen cloud storage | Delete per location; no end-to-end zero-retention implication |
| Gateway experience | Completed turns and summaries on supported paths | Account continuity, separate from training switch |
| CLI training | Matching calls after valid server-side opt-in | Off stops new collection; prior samples need separate handling |
| Issues public-content training | Public questions/accepted answers with valid permission | Separate publication rules; sealed work excluded |
| Security and disputes | Minimum records needed for a case | Restricted purpose, access and lawful retention |
11
Corrections, feedback and safety samples
Negative ratings, bug reports, refund evidence and rights complaints permit necessary handling of that matter, not automatic general training on the whole conversation. A feedback flow requesting training must identify scope and obtain required authority. Fraud prevention, safety and legal retention may have distinct grounds but must not reclassify every ordinary conversation as an unlimited safety sample. De-identification can leave identifiable text; anonymisation requires the applicable standard of non-identifiability and irreversibility, not merely removing a username.