Early preview · Six skills are always free. Paid skills open soon.
How to use AI skills · 2 min read

Prepare private documents for an AI task

Remove unnecessary identifiers, check the destination’s settings, and use the smallest excerpt that supports the work.

Editorial illustration of a delicate paper veil covering the windows of a small cabinet.

Before using private documents with AI, decide which information the task actually needs. Remove unnecessary identifiers and use a small excerpt when possible. Check the chosen app’s current data controls and organizational rules instead of assuming that every AI service handles files the same way.

Minimize the input

For a résumé wording task, the model may need a bullet and confirmed scope, not your address and phone number. For a document comparison, it may need two relevant sections, not the entire file. Redaction reduces exposure but does not guarantee anonymity; context can still identify people or organizations.

A fictional redaction plan

FieldNeeded for wording task?Treatment
Personal phone numberNoRemove
Employer nameUsually notReplace with consistent label
Number of accounts handledYesKeep if sharing is permitted
Customer account namesNoRemove

Keep the original in your normal secure location. Do not overwrite it with the redacted version. Use consistent placeholders so the comparison remains understandable.

Prepare the brief without private content

Working template

Help plan a minimal input for this task.
List the categories of information needed and unnecessary identifiers.
Do not ask me to paste the full document during this planning step.
Suggest consistent placeholders and checks for hidden metadata or comments.
Task: [description]
Document type: [type only]

Check the destination and result

Review the service’s current settings, retention information, and the rules that apply to your organization or clients. A skill file cannot override the host’s data handling. If you are unsure whether a document may be shared, get guidance from the responsible person before uploading it.

Inspect the output for identifiers copied from the input and for accidental re-identification through context. Store or share the result according to the same sensitivity as its contents. Do not paste credentials into a prompt. For a first workflow test, synthetic inputs often answer the usability question without requiring real private records.