About 5 min read
Privacy, data, and isolation
High-level expectations for tenant isolation, where state lives in a hosted deployment, and what to ask your admin about compliance.
Isolation expectation
Smart AI Team is designed so one customer’s workspace state does not appear in another’s runtime. Exact implementation details depend on your deployment model—cloud multi-tenant, dedicated, or self-hosted.
Questions for your admin
- Where are backups stored and who can restore them?
- Which subprocessors apply to your contract?
- How long are logs retained?
User responsibilities
Do not paste highly sensitive personal data into prompts unless policy allows. Use attachments and access-controlled tools when available.
Related articles
- What to do right after you sign up — A short checklist after you create an account: confirm email, pick or wait for your workspace, and open the product for the first time.
- Workspaces explained — How a workspace relates to your company account, why you might have more than one, and where your agents and data live.
- Sign in, SSO, and launch links — How sign-in works with the control plane, branded workspace URLs, and secure handoff into your tenant runtime.
- Members, invites, and roles — Inviting colleagues, what new members should expect on first visit, and keeping access aligned with how your team works.
- Billing, plans, and invoices — Where billing is managed, how usage-related charges may appear, and how to get help when something looks wrong on an invoice.
- Help Center home