Compliance evidence pack
The compliance evidence pack is one .zip file you can file with your compliance records. It’s built from what backcrew already records for your workspace, at the moment you download it. Only owners can download it.
Download it
Section titled “Download it”- Open Settings → Compliance.
- Pick the dates for the audit log (From and To, both included, up to 366 days).
- Select Download evidence pack.
Downloading the pack is itself recorded in the audit log, with the dates you picked.
What’s inside
Section titled “What’s inside”| File | What it holds |
|---|---|
README.md |
A summary: the workspace, the dates, when the pack was made, what each file holds, and a Control mapping section for your compliance owner. |
audit-log.csv |
Every change and every agent request in the dates you picked, the same as Export CSV on the Audit log page (up to 50,000 entries). |
members.csv |
Everyone in the workspace and every pending invitation, with their role and when they joined or were invited. |
agents.json |
Each agent: where it runs, its model and memory setting, its policy and rules, its tools (names and categories), its knowledge bases (names), and every version that went live, with who deployed it and its code review result. |
data-location.json |
Where each kind of data is kept, for how long, and that it’s encrypted at rest - the same as Settings → Data location. |
The pack holds only your workspace’s data. It never holds tool credentials or connection details, prompts or replies.
Last activity, not last sign-in
Section titled “Last activity, not last sign-in”backcrew doesn’t record sign-ins. The last_audit_log_activity column in members.csv is the last time the person did something recorded in your audit log. It’s blank for someone who only signed in and looked around.
Spreadsheet-safe
Section titled “Spreadsheet-safe”A cell that starts with =, +, - or @ is prefixed with ', so your spreadsheet opens it as text and never runs it as a formula.
Control mapping
Section titled “Control mapping”The pack’s summary page has a Control mapping table, left empty on purpose. backcrew doesn’t claim which NCA ECC, SAMA CSF or PDPL controls these files satisfy: that depends on your own control set and is your compliance owner’s call. They record which of your controls each file supports, who reviewed it and when.