Data Portability

Your data is always yours to take with you. Any admin can export a complete, self-serve copy of an entire cycle at any time — no support ticket, no proprietary format, nothing held back.

How to export

1. Open a cycle and click Export.
2. Under Package shape, choose Complete data export.
3. Download the ZIP — ankos-complete-export-<cycle>.zip.

That's it. No request to support, no waiting.

What's included

Everything in the cycle, in open and parseable formats:

• data/entries.json — every entry (all states), with the full field set: state, owner, narrative, justification, sign-off, due date, carry-forward, and the complete QSA decision history (qsa_history).
• data/audit-trail.json and data/audit-trail.csv — the full activity log for the cycle (who did what, when), as both JSON and a human-readable CSV.
• data/comments.json — every comment on every entry, including edited and deleted ones, with timestamps.
• data/watchers.json — watchers on each entry (a row with unwatched: true marks someone who opted out).
• data/checklist.json — every checklist item and its completion state.
• Req-01 … Req-12/ — every evidence file, in its original format (PDF, PNG, DOCX, JSON, …), named with the entry ID for cross-reference.
• manifest.json — a SHA-256 hash of every file in the package.
• README.md — an index of the above.

Open formats only

Structured data is JSON; the audit trail also ships as CSV; evidence files keep their original formats. There is no proprietary Ankos format — you can read, archive, diff, or migrate the export with standard tools.

Verify integrity

Every file is hashed in manifest.json. From the package root:

jq -r '.integrity.files[] | "\(.hash)  \(.path)"' manifest.json | shasum -a 256 -c -

Every line should report OK.