Sample method note
This is what a buyer receives with a dataset, produced by our preparation tools. Here they ran on an invented repository: two support tickets with made-up people and a code history with two fake keys planted in a deleted commit. The note is shown exactly as the tool wrote it, including the blocker: the keys were found in the history, so this delivery is not allowed to leave.
One ticket, before and after
De: José Núñez <jose.nunez@gmail.com> · DNI 12345678Z · +34 612 345 678
De: Esteban Ibarra Ríos <esteban.ibarra@northwind-logistics.example> · DNI 65149886G · +34 612 544 496
The method note, unedited
Written 2026-10-08 from the preparation tools' reports. Prepared by: Nura (demo), in the seller's environment (D-013). Nura did not hold the records.
1. What the source was
- No inventory report supplied (src/tools/inventory). Source size and licences are not stated here.
2. Secrets (keys, tokens, credentials) over the full git history
- Engine: builtin. Open findings: 4 (assigned-secret, aws-secret-access-key, stripe-live-key).
3. Personal data: pseudonymisation and exclusions
- 2 files processed, 2 changed. Replaced by kind: bound_display_name 2, br_cpf 1, email 2, es_dni 1, phone 2.
- 2 people linked across files, so each keeps one consistent stand-in. Secrets removed in this pass: 0.
- Coverage: 2 of 2 eligible files prepared (score 1.0). Not prepared and not delivered, by type: none.
- HR and health records excluded outright: 0 files (none found). Rules: folder/file names and table headers; prose is not classified, so the seller's sample review is the check for an HR or health matter inside an email or document.
- Residual check: no original identifier survived. Relationship check: passed.
Limitations (from the engine): This is pseudonymisation, not anonymisation. Pseudonymised data can remain personal data. Structure, timing and rare attribute combinations can re-identify individuals even with every direct identifier replaced. A name is replaced everywhere once it is bound to a person anywhere in the corpus - beside an email, in a mail header, or in a person column of a table - but a name that is never bound anywhere is NOT detected. This report evidences diligence; it is not a clearance.
4. Delivery
- No delivery manifest yet (databroker delivery manifest DIR).
- Seller's sample approval: [review id, approver, date] (databroker sample decide).
- An independent certificate is needed when personal data was present: [provider or 'not needed'].
Blockers
- 4 open secrets findings: rotate and remove from history, then re-scan