Data
Last updated September 17, 2026. Plain words on purpose: if a sentence here is unclear, it is wrong, and you can tell us at hello@sigbound.com.
This page is the whole answer, with the numbers the code actually enforces. If a number here is wrong the build fails: a test reads this page and compares each one with the constant that enforces it.
One installation runs in one region. The hosted service runs in Amazon Web Services in the United States (us-east-1). Everything below lives in one of three places: the object store (repositories, packs, artifacts), the database (the product: spaces, goals, attempts, decisions, merge records, the audit log), and the identity pool (the sign-in itself). Those three are also exactly what deploy/wipe.sh erases when an operator starts an installation over.
What we keep
| What | Where | How long | Who can read it |
|---|---|---|---|
| Repositories | Object store | While the repository exists. Deleted, it is recoverable for 30 days, then the bytes go. | Whoever holds a grant on it, and anyone at all if it is public. |
| Goals, attempts, decisions | Database | While the space exists. | Members of the space, by their role. |
| Merge records and the audit log | Database | While the space exists. Never subject to a retention cap. | Members of the space; a merge record is verifiable by anyone holding it. |
| CI logs | Database | 6 months, then the month’s partition is dropped. | Members of the space, by their role. |
| CI artifacts | Object store | What the workflow asked for, capped by the space’s own setting: 0 to 3650 days. | Members of the space, by their role. |
| Attempt staging refs and packs | Object store | 26 hours after the attempt is checkpointed and materialised. | Nobody reads them directly; they are how a change is rebuilt. |
| Webhook delivery bodies | Database | 30 days. The delivery row itself stays; the bodies are cleared. | Members of the space, by their role. |
| Account | Database and the identity pool | While the account exists. Closing it frees the address at once. | You. Your name is shown to spaces you belong to. |
| Sign-in credentials | Identity pool | While the account exists. We never see the password. | Nobody here. |
| A deleted space | Database | Recoverable for 30 days, then it is gone and the slug is released. | Its owners, until the window closes. |
| Database backups | The database provider | 7 days of point-in-time recovery. | Nobody, until a restore. |
Taking it out
Under Settings → Account you can download everything held about you as one file. A space owner can export the whole space from the space’s settings — goals, attempts, merge records and the audit log, with receipts — and every repository as a git bundle. Nothing about an export is gated on asking us.
Deleting it
- An account: close it yourself under Settings → Account. Every membership, session, token, connection and key is revoked in one transaction and the address is freed. Merge records and audit rows you produced keep their content and name a former member, because they are the record the space relies on.
- A repository: delete it. It is recoverable for 30 days; after that an operator purge removes the bytes.
- A space: delete it. It is recoverable for 30 days, then it is gone and its name is released.
- A whole installation you run yourself:
deploy/wipe.shdrops the database schema, empties the object store and removes the sign-ins.
Deleted rows leave database backups as those backups age out, within 7 days.
The model provider
Sigbound AI is the platform’s reader. When it reads an attempt, this is what leaves for Anthropic’s API: the goal’s sentence and its brief, the commit messages, the diff between the attempt’s base and its head, the results of the checks at that head, and the contents of any file or the output of any command the reader opens while it reads. The read runs under our API key on the hosted service, and under yours if you self-host.
Nothing is redacted on that path today. If a secret is committed in the diff, it is in what we send. We do not filter, mask or classify the bytes before the call; the only bound is how much the reader opens. That is a plain statement of how it works now, not a plan — and it is why a secret belongs in the secret store and never in a commit.
We do not train anything on your code, and our terms with the provider prohibit it training on your code. Anthropic publishes its own commercial data policy; the terms we hold are the ones described in the Data processing addendum, and the provider is named in Subprocessors.
What is not here
No advertising, no analytics trackers, no sale of anything. One cookie, the session, set only when you sign in. Our SOC 2 controls map is internal; it is available on request at hello@sigbound.com.
The shorter, legal version of the same facts is on the Privacy page; the posture that protects them is on Security.