Your Audit Trail
ROUNDBOX Orbis keeps a record of what happens in your workspace — who signed in, what administrators changed, what policies decided. This page explains what is recorded, how long it is kept, and how to get a copy you can verify yourself.
What is recorded
The audit trail answers who did what, when, and from where:
- sign-ins and sign-in failures
- administrative changes — users, roles, settings, policies
- policy and data-protection decisions
- tool and sandbox activity
What is not recorded
Your content is not in the audit trail. Prompts, model responses and uploaded files are never written to it — only the record that an action took place.
This is deliberate. The audit trail is stored in a way that resists deletion, which is the right property for a record of actions and the wrong one for your content. Keeping them separate means the trail can be protected properly without limiting your control over your own data.
How long it is kept
| Standard | 1-Year Retention | |
|---|---|---|
| Visible to you | 90 days | 365 days |
| Retained | 365 days | 365 days |
The 1-Year Retention add-on extends what you can see and download. Records are kept for a year either way — so if you add it later, the year already behind you becomes visible immediately.
Getting a copy
In the console, open your audit archive. You receive:
- a read-only link to your archive, valid for 15 minutes, and
- a manifest listing each day, the number of records, and a checksum.
The archive is one compressed file per day, in a plain text format (newline-delimited JSON) that any tool can read. Request a fresh link whenever you need one.
Verifying it yourself
This is the part worth knowing about.
Each day's file carries a checksum, and each day is cryptographically linked to the day before it. Together that means you can confirm your audit trail has not been altered without trusting ROUNDBOX to tell you so.
To check a day:
- Download the file for that day using your link.
- Compute its SHA-256 checksum.
- Compare it with the checksum in the manifest.
If they match, the file is exactly what was sealed. If a record had been changed, added or removed after the fact, the checksums would not match — and because each day links to the previous one, removing an entire day is detectable too.
Protection against tampering
Two separate things protect your record, and it is worth being precise about them:
- Tamper-prevention — files are written to storage that refuses modification and deletion. This currently covers the most recent 90 days.
- Tamper-evidence — the checksums and day-to-day links let you detect any alteration. This covers the full 365 days.
So for the first 90 days a change is impossible; beyond that, a change remains detectable.
Extending the prevention window is currently on hold, so 90 days is the figure to rely on. If that changes, this page changes with it.
Your archive is yours alone
Each customer's archive is held in its own isolated container. The link you receive names only your archive — it cannot reach another customer's data.
The link is read-only. You can read and download your audit trail; nobody using it can alter it, including you. That restriction is what makes it evidence.
Legal hold
If you are subject to litigation or a regulatory investigation, your audit trail can be placed on hold so nothing is removed while it is in effect. Contact support to arrange it.