Per-customer encryption at rest with customer-managed keys, crypto-shredding, and an immutable access audit.
Data isolation encrypts your agents’ durable content at rest under a key you
control. Every byte is readable only through that key, so you can make the
content permanently unrecoverable at any time by revoking or destroying the key,
without touching the stored data itself.It covers the content Karta keeps for you between sessions: a karta’s durable
workspace and its conversation history.
Data isolation is configured per organization, and can be scoped to a finer
isolation partition within an organization when you serve multiple brands or
business units that must stay cryptographically separate. Each partition gets its
own key.
Every durable store is encrypted with AES-256-GCM. Karta uses envelope
encryption: each record is sealed with a short-lived data key, and that data key
is wrapped by your master key. Your content is never encrypted directly under
the master key, so rotating or revoking the master key acts on the small wrapped
keys rather than on gigabytes of stored content.Each record’s encryption is bound to its exact context - the organization, the
isolation partition, the agent instance, and the field it belongs to. Content
sealed in one context cannot be moved, replayed, or substituted into another.
Point Karta at a key in your own cloud KMS (a customer-managed CMK). Karta is
granted scoped use of the key and never holds custody, so you can withdraw
that access at any time.
Karta-managed key
For a lighter setup, Karta can hold a dedicated per-customer key on your
behalf, with the same per-customer separation and the same revoke and audit
controls.
Because your content is only ever readable through your key, controlling the key
controls the data.
Revoke (reversible)
Suspend Karta’s access to your key. Your content immediately becomes
unreadable and any in-flight work for that partition stops. Re-grant access
and it is readable again. Nothing was destroyed.
Delete (permanent)
Destroy the key. The encrypted content remains on disk but can never be
decrypted again, by anyone. You erase the data by erasing its key, instantly
and irreversibly.
Crypto-shredding gives you a clean answer to deletion and right-to-erasure
obligations: one key action renders an isolation partition’s content
unrecoverable everywhere it is stored, with no need to locate and scrub every
copy.
Key deletion is irreversible. Once the key is gone, the content it protected
cannot be recovered. Treat it as the permanent erasure control it is.
With data isolation on, your content is unreadable without your key, including to
Karta. An operator with access to the underlying storage sees only ciphertext.
For a customer-managed key you hold the key and decide when Karta may use it, so
you can sever access unilaterally.
Rotate your master key on whatever schedule your policy requires. Rotation
re-wraps the small data keys under the new master key; your stored content is
never rewritten. Content encrypted before a rotation stays readable throughout,
and you choose when to retire the old key version.
Durable content is authenticated, so a modified or substituted record fails to
decrypt rather than returning altered data. A tamper-evident record of the latest
committed state refuses any attempt to roll your durable workspace or conversation
history back to an earlier version, or to reorder or drop messages.
Every key use and every content access is written to an append-only audit trail.
The trail records the operation, the partition, and the outcome using opaque
identifiers only, never your content. You get a verifiable record of what touched
your data and when, including reads that did not require a fresh key operation.
