A document can disappear from a chat window while copies remain somewhere else. That is the central difficulty in deciding whether an AI service may handle a file. Training controls, visible history, connected storage and operational logs describe different activities. A useful review therefore follows the document through the system instead of treating a privacy toggle as a single answer. This guide offers a retention worksheet and a deliberately fictional example. It is not a test of a provider's backend, and the example does not authorize uploading confidential information.
Draw the copy map before opening the upload dialog
Start with the original file and draw the places where its content could be copied: the upload, extracted text, conversation, generated answer, shared workspace, exported result and any connected application. Include screenshots or support messages only if they are actually part of your workflow. A service may not expose every internal copy. Label those locations as undocumented rather than inventing a retention period.
For each location, record the person or organization controlling it, the applicable account type, the deletion control, the stated retention rule and the evidence supporting that rule. Separate a file you can remove yourself from a record governed by an administrator. If the tool retrieves from a shared drive, removing a conversation does not necessarily remove that original drive document. Your map should make those dependencies visible before anyone mistakes a successful upload for an approved data flow.
Ask four different questions about one setting
First ask whether the setting changes what appears in history. Then ask whether it changes use for model improvement. Next ask what remains for security or other operational purposes. Finally ask whether it also affects connected products.
Google's consumer Gemini privacy documentation illustrates the distinction: temporary conversations have a stated 72-hour account retention window, and deleting Gemini activity does not delete material held by other Google services. These are product-specific statements checked on October 20, 2026, not universal rules for AI products, workplace accounts or API plans. The worksheet below separates these promises into rows, including unresolved backend copies. Its filled example uses a public document and is not a backend audit. The practical lesson is to write each promise in its own row. A blank cell is a question for the provider, not permission to assume immediate deletion.
A fictional procurement worksheet
Imagine a small design studio wants an assistant to reformat a public project brief. Its draft worksheet identifies the source as an already published PDF, the purpose as extracting dates into a table, and the allowed output as a local spreadsheet. The studio excludes client correspondence and unpublished pricing from the trial. These details are an illustrative decision, not evidence that a particular organization has used or endorsed this method.
The studio adds columns for account owner, document visibility, retention statement, connector access and cleanup responsibility. It pastes links to the applicable documentation beside each answer. If the upload and conversation have separate controls, they receive separate rows. The local spreadsheet has its own disposal rule. This is useful even if the public brief is low risk: a bounded example reveals whether the proposed process can actually be explained before a more sensitive task is considered.
Treat retention as a reason to minimize the input
If the question needs one paragraph, assess whether the complete document is necessary. An excerpt can reduce exposure, but it may also omit a condition that changes the answer. Keep enough context for the intended task while excluding unrelated personal details. Do not call a document anonymous simply because names have been replaced; combinations of job titles, dates and circumstances can still identify someone.
Use synthetic material when the purpose is testing formatting or instruction following. Use public material only when you have permission to process it in the proposed way. An approved organization account may have contractual controls that a personal account does not. Conversely, a familiar logo or paid subscription does not establish the terms for your exact workspace. When a contractual or regulated-record question remains unresolved, keep the real document out of the trial and take the uncertainty to the responsible reviewer.
Test the controls you can observe
A harmless test can establish what the interface does. Record the sample filename, where it becomes visible, whether another authorized workspace member can see it, and which removal controls are offered. After exercising a documented deletion action, check the visible file and conversation lists separately. Do not create unauthorized accounts, evade retention policies or probe a provider's infrastructure to obtain stronger-looking evidence.
Describe the result narrowly: a file stopped appearing in a named interface at a recorded time. That does not demonstrate that operational copies, backups or previously exported material disappeared. Keep a short note of the documented rule that governs those other locations. If a provider offers a deletion confirmation or administrative audit record, retain that evidence without claiming it reveals every backend process.
Decide whether the remaining uncertainty is acceptable
The completed worksheet should let someone answer three concrete questions: which copies can be created, who controls their removal, and what evidence establishes their lifetime. A public formatting exercise may tolerate uncertainty that a confidential personnel record cannot. There is no honest universal retention number that makes every document safe to upload.
Revisit the worksheet when the account plan, connector, workspace membership or relevant policy changes. Record the actual review date and the specific statement checked. If an essential question remains unanswered, choose a less exposed workflow or defer the upload.
Map the copies, not just the chat history
This filled worksheet uses a fictional public brief. The entries are questions and responsibilities, not findings about any provider’s backend. “Undocumented” remains unresolved.
| Location | Controller and removal route | Evidence / unresolved condition |
|---|---|---|
| Original public PDF | Publisher; upload deletion does not control it | Record original URL and version |
| Uploaded file | Workspace owner; identify the file-specific control | Paste applicable plan documentation; otherwise undocumented |
| Conversation and generated answer | Account or workspace administrator | Record history, training and operational retention separately |
| Connected drive | Drive owner; separate removal procedure | Do not infer drive deletion from chat removal |
| Security records or backups | Provider; usually not visible in the interface | Use documented retention rules; unknown is not zero |
| Local exported spreadsheet | Studio operator; protected local storage | Assign an owner and a disposal date appropriate to the work |
Select or copy plain text
Location Controller and removal route Evidence / unresolved condition Original public PDF Publisher; upload deletion does not control it Record original URL and version Uploaded file Workspace owner; identify the file-specific control Paste applicable plan documentation; otherwise undocumented Conversation and generated answer Account or workspace administrator Record history, training and operational retention separately Connected drive Drive owner; separate removal procedure Do not infer drive deletion from chat removal Security records or backups Provider; usually not visible in the interface Use documented retention rules; unknown is not zero Local exported spreadsheet Studio operator; protected local storage Assign an owner and a disposal date appropriate to the work
Copy a blank retention row
Copy location: Account type / controller: Who can see it: Visible deletion control: Training use rule: Operational retention rule: Source URL / exact section / checked date: Cleanup owner: Unresolved question and upload decision:
Select or copy plain text
Copy location: Account type / controller: Who can see it: Visible deletion control: Training use rule: Operational retention rule: Source URL / exact section / checked date: Cleanup owner: Unresolved question and upload decision:
REFERENCES
Sources and further reading
- 01Google Gemini Apps Privacy Hub
- 02NIST Privacy Framework
- 03NIST Generative AI Profile (AI 600-1, July 2024)
Sources reviewed October 20, 2026. Provider instructions and product terms can change. Examples identified as fictional are editorial illustrations, not reported events or product tests.