DEV Community

Claupt
Claupt

Posted on Originally published at claupt.com

How to Prepare a Contract for AI Without Exposing Sensitive Data

AI can help summarize, review, and turn contracts into clear action items. Before uploading a contract to ChatGPT, Claude, Gemini, or another AI tool, remove the details that identify people, projects, and commercial terms.

This is a practical way to prepare a useful copy while keeping the original private.

What to remove first

Start with direct identifiers:

  • Names, email addresses, phone numbers, and postal addresses
  • Client, company, project, and internal product names
  • Contract, purchase-order, tender, invoice, and reference numbers
  • Bank details, API keys, passwords, IP addresses, and other credentials

A contract can still reveal a person or organization even when one obvious field is removed. Treat combinations of details carefully.

Use consistent placeholders

Replace repeated details with the same placeholder every time. That keeps the relationships in the document understandable.

For example:

  • Ahmed Al-Harbi → [PERSON_1]
  • Project Falcon → [PROJECT_1]
  • CN-2026-044 → [CONTRACT_1]
  • ahmed@example.com → [EMAIL_1]

Now an AI can see that [PERSON_1] appears in several clauses, without learning who that person is.

Keep the legal meaning intact

Remove identifiers, but preserve the clause structure, dates when they matter to the question, obligations, exceptions, and amounts when they are needed for analysis.

Instead of deleting an entire section, turn this:

Ahmed Al-Harbi will deliver the Project Falcon report by 15 October under Contract CN-2026-044.

Into this:

[PERSON_1] will deliver the [PROJECT_1] report by 15 October under [CONTRACT_1].

The instruction remains clear while the sensitive identifiers are removed.

A text replacement is not a full document redaction

Copying text into a tool is useful for prompt preparation. It does not securely redact the original PDF or Word document. Comments, revisions, document metadata, hidden text, and attachments may still hold information.

Keep the source document private and review the prepared text before sharing it anywhere.

A simple workflow

  1. Copy only the section needed for the AI task.
  2. Replace names, contact details, project names, and reference numbers with consistent placeholders.
  3. Read the result once for context-dependent details that an automated detector may miss.
  4. Ask the AI a narrow question, such as “List the delivery obligations and deadlines.”
  5. Check the answer against the original document locally.
  6. Delete the prepared copy when the work is complete.

A browser-only option

If you work with text often, Claupt's PII Anonymizer helps prepare a private working copy in the browser. It can identify common sensitive data such as emails, phone numbers, addresses, names, project names, and contract numbers.

Automatic detection is a starting point, not a substitute for review. Context-dependent information needs a human check before it is shared.

The best AI workflows keep the evidence that matters and remove the identity details that do not.

Top comments (0)