Erasure Snapshot

A fast, fixed-scope proof that a churned tenant's data has actually left your highest-risk AI surface, the vector database, and that no other tenant can read it. Fully async, no kickoff call. You get the same tamper-evident, independently-verifiable evidence pack as our full attestation, scoped to one surface so you can start today.

Request the Snapshot    Fixed scope, fixed fee · async · 100% creditable toward a full engagement

Why start here

A full Erasure Attestation covers every AI surface and is scoped per engagement. The Snapshot is the entry point: one surface, one fixed fee, no scoping call. The vector DB is where a churned tenant's data most often lingers and where a cross-tenant read does the most damage, so it's the highest-value single surface to prove first. When you're ready to cover the rest (caches, logs, agent memory, fine-tune adapters, search indexes), the Snapshot fee credits in full toward the larger engagement.

What you get

A verdict for your vector DB

Synthetic tenants and cryptographic canary markers tied to a target tenant's identity, planted and then re-scanned after your erasure runs. The surface returns ERASED, RESIDUAL DATA (counts itemized), or NO BASELINE, plus a cross-tenant read check that proves no neighbor can retrieve it.

A tamper-evident pack

RFC 3161 TSA timestamp on the run digest, an in-toto attestation envelope, the hashed ground-truth manifest bound into the pack, and a clean PDF. The test conditions are provable, not asserted.

Independent verification

You, your DPO, your auditor, or your customer runs sectum-ai verify pack (Apache-2.0) and validates the whole chain end-to-end without trusting us. Mutate any field and verify exits 4 with a [FAIL] line.

No secrets cross the boundary

The adapter resolves your vector-DB connection from your own environment variables / secret manager via a reference in a sectum-ai.yaml file. We never see your credentials or your real tenant data, only the synthetic markers we planted.

How it runs, async, in days

  1. You request it. We send a short intake (the one sectum-ai.yaml reference for your vector DB, and which tenant identity to target) and the fixed-fee invoice. No call required.
  2. We baseline. We provision synthetic tenants, plant the canary markers, and confirm they're observable, capturing the hashed ground-truth manifest.
  3. You erase. Your existing erasure workflow runs. We don't interfere; we wait.
  4. We verify and deliver. We re-scan for any residual marker and for cross-tenant readability, then hand you the signed pack, the machine-readable evidence.json, and the PDF.

See verify in 3 minutes

Watch a signed pack clear verify clean, then one edited byte make it fail with a [FAIL] line and a non-zero exit, the whole point of evidence you don't have to take on faith.

Demo walkthrough — link coming; ask for it when you request the Snapshot.

What this is, and isn't

Sectum AI verifies and attests; we don't remediate and we don't provide runtime protection. If the surface returns RESIDUAL DATA, the pack itemizes it, the fix belongs to your team. The control mappings are assertions of test coverage, not legal certification; the wording is explicit in the pack.

Request the Snapshot The full attestation →