Advokat Frida
SafeSeed · ToolkitOne-page brief
SafeSeed: auditable test data by construction
When a team needs a safer test or demo CSV, SafeSeed generates declared fields without accepting production records as source material. Every generated field stays inside a versioned catalog constraint, and the generator produces an unsigned integrity record a reviewer can compare with an independently protected copy.
Start with an editable CRM contacts, marketing attribution, hashed audience, or UK contacts schema. Then Generate constrained stand-ins, Record the exact CSV and field claims, Verify strict whole-file integrity, and Scan named columns for values outside configured ranges.
Four assurance boundaries
1 · Protocol reserved
2 · Authority reserved
NANPA 555-01xx, Ofcom drama mobiles, and SSA-invalid components follow current authority policy. Derived phone hashes inherit the input’s basis; the digest is not reserved.
3 · Designated for testing
Processor-published test card numbers can pass validation. Their test-mode designation — not mathematical impossibility — supports the claim.
4 · Structurally fake
Names, addresses, campaign URLs, and opaque CRM or cookie IDs use obvious TEST_ conventions because no standard reserves those namespaces.
What a clean check supports — and what it does not
Supports
- Declared fields conform to the named catalog version, constraint, citation, and any derivation
- Strict browser and Action checks cover the exact whole CSV and fail on column or byte drift
- An independently protected integrity record can show whether the CSV changed after generation
Does not establish
- The unsigned record does not authenticate itself; changing both files can recompute both
- A clean scan means only “nothing outside configured ranges in named columns” — not “no personal data”
- A SHA-256 digest is not anonymous; arbitrary hashes fail even when their shape looks right
- Not anonymization, a lawful-basis or DSAR answer, access control, or realistic ML/load-test data
Lift verbatim into your control register
For non-production tests and demos, declared PII-shaped fields are generated with SafeSeed without using production records as source material. Each declared field is constrained by the versioned catalog named in the record to a cited protocol-reserved, authority-reserved, test-designated, deliberately fake, or catalog-derived input. The exported unsigned SHA-256 integrity record is stored independently and checked in CI; the strict Action fails on any byte or column drift. In explicitly partial CLI verification, added business columns remain unattested and require separate review. This can support a data-minimization, privacy-by-design, and test-information control narrative. It does not authenticate provenance by itself, establish that the whole file contains no personal data, or constitute anonymization.