Service · Data readiness
P3Document & Dataset De-identification.
The corpus you have contains what you need — and what you can't share. We de-identify it in batch, manage the keys, sample-validate the output, and hand back a corpus safe for analytics, RAG, or training, without losing the analytical signal.
Outcomes
What changes when the engagement lands.
A corpus you can use
The dataset you already own becomes usable for analytics, RAG, or fine-tuning without breaching policy.
Signal preserved
De-identification preserves the analytical signal. The corpus is still worth what it was before it was locked.
Reversibility on your terms
Key management sits with you. Re-identification is possible only under your control.
Sample-validated safety
Validation against a statistical sample. You know the miss rate, not just the claim.
Deliverables
What's in the engagement.
Batch de-identification of an existing document corpus or dataset so it can be safely used for analytics, retrieval-augmented generation, or model training. Includes key management, validation sampling, and delivery of the safe corpus.
De-identified corpus
The full corpus processed. Delivered in your chosen format.
Key management setup
Keys and mapping stored under your control. Reversal procedure documented.
Validation report
Statistical sampling report showing detection rate, false-positive rate, and residual risk.
Runbook
Documented process for de-identifying future corpora using the same pipeline.
How we deliver
Fixed scope. Named phases. Duration on the cover.
The engagement is priced against the outcome, not open-ended hours. Every phase has a duration, a named deliverable, and a check-out.
Total duration3 to 8 weeks
Sales cycle4 to 8 weeks
- 011 week
Scope
Corpus inventory. Detection scope agreed. Key management model chosen.
- 021 to 3 weeks
Pipeline build
Detection and redaction pipeline built and tuned against corpus samples.
- 031 to 3 weeks
Batch processing
Full corpus processed. Key management stored. Validation sampling executed.
- 041 week
Delivery and handover
Corpus and validation report delivered. Runbook handed over.
Built for
Buyers this engagement fits.
Typical buyer
Chief Data Officer, CISO, Head of Analytics
Chief Data Officers unlocking a corpus for analytics
The data's rich. It's also locked because of what's in it. This gets it usable.
Businesses about to fine-tune on internal data
Training data has to be safe before it's trained on. The service produces the safe version.
Analytics teams doing customer research at scale
The corpus of tickets or chat logs is exactly what you need to model. This lets you model it.
Related services
Where this leads next.
Fine-Tuning Feasibility & Data Readiness
Fine-tune vs RAG vs prompting. Data audit. Base model shortlist. Costed build proposal.
Safe LLM Gateway: Design & Pilot
Inline gateway design. PII and sensitive-entity detection. One-department pilot live.
AI Data Exposure Assessment
Where your data is leaving today. Sanctioned, unsanctioned, all of it.
Talk to us.
45 minutes on your operation and the engagement you have in mind. No pitch, no deck.
By briefing only
This engagement is scoped one to one.
This engagement requires a delivery team assembled against your specific scope. Every engagement starts with a direct conversation, not an open form. Email us and we'll route it to the right lead.