Exit and portability
How your data and your evidence leave.
A product whose value is a reconstructible evidence chain has to say how that chain leaves with you. Most vendors answer this question in a negotiation. Answering it here costs us nothing we should be protecting, and it is the question that stalls enterprise agreements at legal.
The short version
EOS holds no write credential to your systems of record, so there is nothing of ours to unwind in them. EOS holds the observations it received, plus everything it derived: reconciliations, decisions, authorities, outcomes. Today the service exports sealed registers, whose SHA-256 seal you can recompute offline, and reference packs; the full export the table below describes, with evidence packs that verify their content offline without us, is specified, not built. Until it is, a full export is assembled by hand on request, at no charge.
What EOS holds about you, and the export specified for it
| Class | What it is | Specified export format | Specified to verify offline? |
|---|---|---|---|
| Source records | The canonical copy of what was read from your systems, with source, timestamp and record reference | JSON Lines, CSV | Yes, against your own systems |
| Canonical objects | The reconciled object with every contributing source retained | JSON Lines | Yes |
| Reconciliations | Every detected disagreement, the rule applied, and the sources retained on both sides | JSON Lines | Yes |
| Evidence packs | The trace behind a material figure: claim, source, timestamp, transformation, rule, calculation | JSON + PDF | Yes, content-hashed |
| Decision ledger | Every recorded decision, the authority that made it, the timestamp | JSON Lines, append-only chain | Yes, chain verifiable |
| Outcomes | What was expected, what was measured, the gap, and when | JSON Lines, CSV | Yes |
| Policy and configuration | Rules, authority graph, field maps, connector configuration | JSON, YAML | Yes |
| Audit log | Append-only record of every sync, read, decision and administrative action | JSON Lines | Yes, chain verifiable |
The part that matters
The test we hold ourselves to
An exported evidence pack must still verify on a machine that has never heard of AssetShop, with no account, no network and no vendor in the loop, with its verification harness inside the export. Neither the pack nor its harness is built yet; this is the test it will be held to. If an evidence pack only verifies while you are a customer, it was never evidence. It was a subscription.
Timeline and cost
| Trigger | Timeline | Cost |
|---|---|---|
| Sealed registers, any time | Immediate, through the service's reports, for an owner or admin | None |
| Full estate export on request | Within 5 business days | None |
| Termination, for any reason | Export available for 90 days after the end date | None |
| Deletion certificate | Within 30 days of your written instruction | None |
| Vendor failure or insolvency | See source escrow [not claimed] below | Per escrow agreement |
What happens if we are not here
Two mechanisms, at two different maturities, and the difference is stated rather than blurred.
- Evidence that survives us Design
- Exported evidence packs and the decision ledger, verifying offline with a harness that ships alongside them and requiring nothing from us: specified, not built. Today the service exports sealed registers whose seal you can recompute offline. This is the mechanism we would rather you rely on once it ships.Status: specified; the sealed registers export today
- Source escrow Design
- A conventional software escrow arrangement releasing source and build instructions on defined trigger events. Executed with each enterprise agreement.Status source: READINESS_SCORECARD.md
What we do not do
We do not hold your data hostage behind a proprietary format, charge an exit fee, require notice to export, degrade the export relative to the live product, or retain anything after a deletion instruction beyond what law requires. None of that is generosity. An evidence product that made leaving expensive would be arguing against its own thesis.
Trust center · Data processing addendum · The Verify Standard