Skip to content
ONE3.ai

Glossary

Cross-tenant isolation

The rules that keep each client's data, memory and playbooks inside its own tenant, even when renting the same agent template as others.

When the same agent template is rented to Client A and Client B — possibly competitors, or two clients of the same agency — nothing of A's may influence B. One3's cross-tenant isolation rules:

  • Templates contain no tenant data.
  • Tenant memory, playbook overrides, approved examples, adapters and ledger data stay inside the tenant boundary, with row-level security and tenant-keyed encryption.
  • Shared templates improve only from synthetic data, One3's own usage and opted-in, anonymised, aggregated signals — never raw content.
  • Caches are tenant-partitioned, and context assembly can reference only the tenant's own stores.

Leak tests run on every relevant change, with weekly canary-token audits and deletion verification on every offboarding. The target is zero findings.

Related terms

Agent Training GymAgent templateDPDPTenant

See how One3 would run your business

Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.

Request early access How One3 works