BUYER_DOCS / INDEX

Buyer documentation

The artefacts a data-ops lead or vendor-review team asks for, in the order they usually ask. Documents 01–03 need no NDA — read them before you talk to us.

01 Annotation methodology How contributors are screened, how gold is seeded, and what the QA guarantee actually commits to. → 02 Sample deliverable pack What a delivery contains — labelled data, agreement report, QA scorecard — with worked examples. → 03 Data handling & deletion Chain of custody from intake to verified deletion, access control, and the honest certification position. → 04 Mutual NDA Ready-to-sign mutual non-disclosure agreement. Draft for counsel review. → 05 Data Processing Agreement Processor terms, cross-border access, breach notification and deletion. Draft for counsel review. → 06 IP assignment Client-facing assignment plus the contributor assignment that makes it enforceable. →

Why these exist

The institutional layer is mostly documentation of things already done, and only partly certifications that matter above a certain contract size. These are the former. Every claim below is marked in place, policy or roadmap — nothing is rounded up. A supplier that says “SOC 2 on the roadmap” is more useful than one that implies it holds it, because your job is to find the gap.

What is deliberately not claimed

No named clients, no logos, no case studies, no certifications we do not hold, no throughput we have not achieved. Two things we do claim, because both are checkable: a live scored screening you can run in your own browser before speaking to us, and a regulated entity behind it.

← All documents Start a pilot