alpha

Encryption and access control — built into how taip works.

Encryption and access control are built into how taip works. context-mcp records every read with actor, role, item, and timestamp. The full architecture, including what taip deliberately is not, is below.

Request a pilot

brain · context · tools

trust & safety

How taip protects what it holds.

Encrypted at rest

There are no plaintext bodies to expose in the remote repository. Bodies are encrypted with SOPS and age — only the frontmatter stays in plaintext, so the remote repository holds no plaintext bodies. Content is decrypted in memory, after a request is authorized.

Role-gated access — fails closed

A role reads only what it is permitted — missing or malformed metadata is hidden, not exposed. Every request is checked against plaintext frontmatter before anything is decrypted, at a single chokepoint that fails closed.

Crypto-shred for GDPR erasure

Destroying a key renders taip-managed ciphertext inaccessible. Each subject's data is wrapped by a key held in a KMS. Destroy that key and the ciphertext in taip's storage — the repository, its history, and backups — becomes irrecoverable. Copies previously transferred to connected AI services must be managed under those services' retention and deletion policies. That is how taip supports erasure under GDPR Article 17.

context-mcp: access log for every read and write

context-mcp records every read and write with actor, role, item, and timestamp. Brain-side access logging is planned — until it ships, brain sessions are not individually logged.

EU-hosted, per-company isolation

You know exactly where your data is and who governs it. Each company runs in its own container, with its own encrypted repository and keys. The git remote and key store are kept in the EU and operated under EU law.

What taip is not

Knowing what a tool governs is as important as knowing what it does.

taip serves and manages access to what an assistant reads from taip. It is not a gateway or firewall over your other tools — it does not intercept or block their calls. It governs the knowledge it holds, and context-mcp records who read it.

Scope and boundaries

TAIP controls access to content served through TAIP. context-mcp records reads and writes; brain-side logging is planned. TAIP does not control downstream retention by connected AI providers or actions performed through other tools.

compliance FAQ

Questions your auditor will ask.

Where is data hosted and under which jurisdiction?

Each company runs in its own isolated container, with its own encrypted repository and key store. Both are kept in the EU and operated under EU law. TAIP-managed repositories and key stores remain in the selected EU region. Content sent to connected AI providers is processed under those providers' locations, retention terms and deletion policies.

What can taip itself see?

taip reads only the plaintext frontmatter needed to check access rules — encrypted bodies remain ciphertext until a request is authorized. taip does not read or store the decrypted content of your rules beyond the time needed to serve a request.

How does a GDPR Article 17 erasure request flow through crypto-shred?

Each subject's data is wrapped by a unique key held in the key management system. When you process an erasure request, you destroy that key. The ciphertext that remains in taip's storage — the repository, its git history, and any backups — is irrecoverable without the key. Note: tenant-level teardown (full environment removal) is not yet offered. Copies previously sent to connected AI services must be managed under those services' retention and deletion policies. No manual data-hunting within taip's own storage is required.