Check personal-account data settings separately from organizational data protections.
Conversation & research · Documented · Documentation checked 2026-10-04
Gemini Apps for personal, work, and school accounts; Workspace apps and developer platforms differ.
Age, country, language, device, Google AI plan, and Workspace license affect access.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Check personal-account data settings separately from organizational data protections.
Personal Gemini Apps and organizational access can have different terms and protections. Keep Activity, memory, connected apps, and device permissions each control different information. Turning one off does not prove that every copy, provider record, or feedback item has been deleted.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Confirm the signed-in identity and whether it has Workspace protections.
- Read the current Privacy Hub and inspect activity / personalization controls.
- Review connected apps and device permissions independently.
- Use synthetic data for a pilot and ask an administrator about retention, sharing, and approved use before adding organizational records.
Worked example
Prepare a data-flow checklist for an assistant that summarizes approved training material. Name the source, model context, saved conversation, generated output, and shared copy. Identify who controls each location instead of assuming a single delete button removes all of them.
Help map a proposed training-material assistant. Use no real personal records. List each data location: source file, uploaded context, conversation, memory, output, and connected service. For each, identify the control or policy I need to verify. Mark unknown retention or access rules clearly.
Inspect and verify the result
Compare the checklist with actual account settings and organizational guidance. Check whether the feature needs activity enabled. Confirm external copies and shared links separately from chat history.
Limits and troubleshooting
School, work, and personal availability differ. A feature menu or plan entitlement is not proof of enterprise-grade protection. If policy is unclear, keep the pilot synthetic until the responsible owner resolves it.
Data, permissions, and actions
Gemini may process prompts, media, device context, and connected information according to the relevant notice. Review human-review and retention details in the current policy. Give the minimum necessary data and avoid enabling broad context merely for convenience.
Related reading
Notebooks, sources, and ongoing context
Keep a project’s source material and conversations in a connected notebook.
From research to a Canvas handout
Turn a verified public-source report into a beginner handout and an inspectable prototype.
A notebook and weekly learning review
Keep approved lesson context organized and generate a private recurring review.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Gemini Apps Privacy Hub · Google
Work and school product boundaries · Google