Security

The honest version, in plain words.

Your data is a git repository you can leave with

The workspace is plain markdown files in an ordinary git repository. git clone gives you a complete, standard-format copy of everything you can see — any time, no export button, no lock-in. If you stop trusting us, you leave with everything.

Access is a rule list you can read

Who can see what is decided by a short, ordered list of path rules — first match wins, and the default is deny. There is no per-file sharing sprawl to audit: the answer to "who can open this?" is one readable rule, shown in the app next to the document it governs.

A restricted collaborator's clone does not hide the folders they may not see — it does not contain them. Not the files, not the history, not the objects.

Every change is on the record

Access changes are logged — who granted what, to whom, when — and the workspace's history is git history: signed-in, attributed, permanent. Owners get a one-page sharing review (guests, expiring grants, public links, quiet accounts) and can stamp it reviewed.

Agents are governed like people

An AI agent is either an assistant acting as the person who runs it — with exactly that person's access — or a named member of the workspace with its own grants and an expiring token. Before a token exists, its profile shows precisely what it will be able to read. Nothing an agent can reach is ever broader than what an owner deliberately granted.

The boring facts

What we have not done yet

We are a young product. We do not yet hold a SOC 2 attestation — the architecture above is our answer in the meantime, and it is designed so you can verify it yourself rather than take our word. Questions, or something you need for a security review: [email protected].