How we handle your data
Bantuva builds software with software: agents write the code inside our workspace, under rules the workspace itself enforces. Each statement below is one of those controls — not a promise, a mechanism that runs today.
Where the models run
Our Strata agent — the one that builds your medium and complex work — runs on Bantuva's own hardware.
Simpler tasks go to a cloud model. If your project is set to Local models only, cloud models
are refused for every job, and the work stays on Bantuva hardware.
Credentials stay encrypted, per project
The credentials for your systems are stored encrypted per project (AES-GCM, under a key that can be rotated), and secrets are redacted from logs.
A throwaway sandbox for every job
Every agent job runs in its own throwaway container, removed when the job ends. It sees only that job's files and its own job token — no host home, no other projects — and its network access is limited to an allowlist: the model endpoint and your project's own instance. Everything else is refused.
Every action is logged
Every action taken by a person or an agent is recorded in an append-only audit log. Entries cannot be edited or deleted — not even by us.
Who can read what
Access is granted by project role. Someone who is not a member of your project sees nothing at all: the system answers as if the project did not exist.
The page's source names the repository file that enforces each statement above — because a trust page should be checkable the same way our work is.