Share the minimum the task needs
Before entering information into an AI product, decide whether it is necessary, whether you are permitted to share it, and what the product’s current settings allow. A writing task rarely needs a real customer’s name, account number, or complete history.
Privacy is not one switch. Training controls, retention, sharing links, connected services, and organizational rules address different questions. Check the current documentation for the actual product and account you use.
Classify the material first
Use three practical groups as a starting point, then follow any stricter rules that apply to your work:
- Public: information already intended for public distribution, such as a published event description.
- Internal: plans, drafts, or operating details not meant for public circulation.
- Sensitive: credentials, financial or personal records, health details, and other information whose exposure could cause harm.
These groups are a planning aid, not a legal classification system. If you do not have authority to share a document, a personal AI subscription does not create that authority.
Remove details that do not change the answer
Suppose you want help making a customer email less defensive. You can often replace the customer’s identity with “Customer A,” an order number with “[ORDER],” and a precise address with “[ADDRESS].” Keep the problem and the required response; remove the unnecessary identifiers.
Redaction is more than replacing names. A combination of dates, locations, job roles, and unusual events may still identify someone. When the real details are not needed, use an entirely fictional example with the same communication problem.
Follow a pre-upload checklist
- Identify the task: rewrite, summarize, classify, or calculate.
- Determine the smallest input that makes the task possible.
- Remove identifiers, credentials, hidden comments, and unrelated sections.
- Check whether the content belongs to someone else or is restricted by your organization.
- Review the product’s current privacy controls and service terms.
- Decide whether to proceed, use an approved workspace, or complete the task without AI.
If you cannot explain why a field is necessary, leave it out of the first attempt. Add context selectively if the response shows that a relevant detail is missing.
A safer practice prompt
Rewrite this fictional service email in a calm, professional tone.
Preserve the facts and leave all placeholders unchanged.
Do not invent compensation, policies, or promises.
Hello [CUSTOMER],
We have not received [DOCUMENT]. We cannot finish [TASK] without it.
Please send it through [APPROVED CHANNEL].This lets you evaluate tone and structure without using a real record. After review, fill placeholders in your approved workflow. Do not ask the assistant to infer the missing private details.
Understand what a setting changes
OpenAI’s Data controls documentation describes an option to prevent new personal-workspace conversations from being used to improve models. It separately describes saved chats and other controls. Read those distinctions carefully: opting out of training is not equivalent to making all use or retention impossible.
Settings can differ by workspace and account. If you use an organizational account, consult the workspace owner rather than assuming your personal settings govern that environment. Avoid relying on screenshots from an older interface.
Remember the surrounding workflow
A prompt is only one place information can travel. Shared conversation links, copied text, downloaded files, browser extensions, screenshots, and collaborators can all change who can see the material. Inspect a generated document before forwarding it; the assistant may have preserved details you meant to remove.
On GuideHollow, the two free tools operate locally in the page. Our search terms appear in URLs, and public GitHub issues are public. Those details are explained in our Privacy Policy. Local processing does not protect against someone with access to your device or clipboard.
If you already shared something sensitive
Stop adding more information. Follow the provider’s current removal options and your organization’s incident process. For a credential, use the issuing service’s revocation or rotation process; deleting a conversation is not a substitute for invalidating a disclosed secret.
This is general workflow guidance rather than a determination of your legal obligations. For a regulated or confidential use case, ask the responsible privacy or security contact before continuing.
Build a repeatable habit
Use a short preflight: permission, necessity, settings, recipients. If any part is unclear, use a fictional input or pause. Then review the output for accidental disclosure before sharing it. Our email drafting guide shows how to preserve useful context without supplying a complete personal history.
Official sources
References checked October 23, 2026. Features and policies can change; follow the source for current details.
Examples are illustrative and use fictional data. Product performance was not benchmarked for this guide.