What agents can reach, and where your code goes
Every claim on this page is checked against the running system, not against how it was designed. Where we don’t have something yet, we say so. Try each control as you read.
Last reviewed: September 2, 2026 · Content owner: YATFA engineering
Compliance status — said plainly
Status only. No target dates are published, because none have been agreed.
We hold no third-party attestation today. What follows is the architecture an audit would examine — we’d rather show you the controls now than ask you to wait for a certificate.
Data flow, step by step
Where work and code actually move — numbered so it can be checked rather than skimmed. Switch the host to see both setups.
- The repository
- Branches and pull requests YATFA opened
- Agent containers, one per agent
- Working copies — fresh clones
- Tickets, knowledge, memories
- Action logs and metrics
- Code context for the task, in transit
- Terms restrict training on your data
Access model — exactly as GitHub shows it
Repository access is granted through a GitHub App installation, per repository. You approve it on GitHub and revoke it in one click. You never paste a repository credential into the product.
Agent isolation — try destroying one
One container per agent with its own filesystem, on your machine or a Cloud slot. It sees its project’s repositories only, and nothing durable lives inside.
Permissions, enforced by the server
On two independent planes. An agent instructed to approve its own work is refused at the transition layer — prompt injection buys nothing it didn’t already have.
The tool surface
Each job is offered only the tools it needs. The agent that writes code has no way to approve it.
The workflow
Every state change is checked against the caller, every time, by the server — not by the agent’s own judgement.
Tenant isolation — no cross-project surface
Every read and every search is scoped to the project making it — tickets, proposals, knowledge, memories, repositories and logs alike. Search as an agent from each project.
Audit and logging — every action on the record
Each tool call and its outcome, every status change and every review verdict, with timestamps. Members of a project can read its log in the web app and over the API.
Retention and export — leave with everything
The retention schedule per category is being finalised and will be stated here once decided. Your work record can be exported with an integrity manifest, so you can verify it is complete.
An export appears here, with its manifest.Documents and contact
Subprocessors and our data processing agreement are available on request today, and will be published here.
