Trust & support

Privacy and safety boundaries in Chat

LLMBase separates ordinary chats, Workspace libraries, private Artifacts, and per-chat Computer working state. Each surface has a defined scope so a helpful tool does not become blanket access to your account or device.

Updated Aug 10, 20266 min read

Know each data boundary

  • A direct attachment belongs to its chat and is not automatically added to every Workspace.
  • A ready Workspace file can be used by chats inside that Workspace, subject to membership and policy.
  • An Artifact belongs to the authenticated account and can be copied into a Workspace only through an explicit action.
  • Computer is private to one chat and sees only authorized extracted inputs plus its own bounded working files.

Plans do not replace action approval

A visible plan explains the intended sequence for a genuinely multi-step task. It can continue safe reading and analysis automatically, but the plan itself does not authorize an external message, destructive change, purchase, privilege change, or other sensitive action.

Organization policies can allow, require confirmation for, or block a specific supported action. If policy cannot be loaded safely, the action should fail closed rather than guess.

Delete the correct scope

Delete a chat to remove its transcript and associated Computer working state. Delete an Artifact from the Artifacts library when the generated file is no longer needed. Delete a Workspace file to stop future Workspace retrieval and begin cleanup of its indexed and stored representations.

Account deletion is broader and should be used only when you intend to remove the account. Download anything you are required to retain before confirming a deletion.

Handle sensitive material carefully

  • Upload only material you are authorized to process.
  • Remove secrets, full credentials, and unnecessary personal data before attaching a document.
  • Review high-stakes medical, legal, financial, and security conclusions against authoritative sources and qualified professionals.
  • Verify recipients and file contents yourself before sharing an Artifact outside LLMBase.

Use the official legal documents for assurances

Product boundaries describe how the feature behaves; they are not a substitute for contractual privacy or security terms. Consult the current Privacy Policy and, for eligible authenticated customers, the current DPA/AVV and published security material.

If the approved documents do not provide a specific assurance you need, contact Support rather than relying on an inferred technical claim.

Frequently asked questions

Does a plan approve every step in it?

No. A plan defines scope and progress. Any action-specific safety confirmation or organization policy still applies at the exact action.

Where can I find the DPA/AVV?

Eligible authenticated customers can access the current DPA/AVV from the Dashboard. Contact Support if your required assurance is not covered there.

Still need help?

Send the Support team a sanitized description, timestamp, affected surface, and exact visible error.

Contact Support