The real workflow
Where Gemini enters the work
Developers may connect assistants to source control, documentation, issue trackers, cloud files, and browser research around the same system.
Gemini can work with prompts, uploads, live audio or screen context, and connected Google or third-party services depending on device, account, region, and settings.
Client content may enter through uploads, connected Google services, live screen sharing, or a work account whose policies differ from a personal account.
Gemini access is shaped by what the user shares, device permissions, connected apps, Gemini Apps Activity, and other Google settings that may remain active independently.
The presence of this path does not prove an incident. It identifies the boundary that should be checked before more sensitive context or authority is added.
Tool-specific boundary
Inspect the real access points.
What may carry context
prompts, files, images, audio, video, and shared screens
connected Google and third-party apps
device permissions and Gemini Apps Activity
Settings to verify
Gemini Apps Activity and auto-delete
Connected apps and public links
Google app device permissions and Saved Info
Why this context matters
The consequence for developers
Developer workflows join high-value source code with tools that can retrieve context, propose changes, run commands, and cross trust boundaries quickly. In this case, exposure can trigger contractual disputes, notification duties, account reviews, project delays, and costly investigation even when no malicious intent was involved.
Client data is not yours to expose simply because it helps complete a task. The practical question is whether the client authorized this tool, this account type, this data category, and this specific access path.
The team can reproduce what the tool accessed, separate read and write authority, protect secrets, and review consequential changes before execution.
Context decision
Three questions before adding access
What can this session read, write, execute, contact over the network, and approve without another person?
Are secrets, production data, protected branches, deployment credentials, and unrelated repositories outside the effective scope?
Will the final diff, commands, dependency changes, test evidence, and approvals survive after the session closes?
Evidence goal: Produce a reproducible technical record of roots, permissions, denied paths, network policy, generated changes, approvals, tests, and rollback points.
A repeatable review
Four steps, no sensitive data required
- 1
Write down the exact Gemini account, workspace, project, device, and connected service used in this workflow.
- 2
Confirm which Google account is active, what Keep Activity does, and whether the client approved connected-app use.
- 3
Assign the decision and next review to the repository owner or engineering lead; do not leave the access boundary as an unwritten assumption.
- 4
Use a dedicated work profile with minimized permissions and synthetic client examples. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Use a dedicated work profile with minimized permissions and synthetic client examples.
Use separate client workspaces and least-privilege accounts instead of one shared personal AI context.
Minimize, redact, or synthesize data before it reaches the assistant.
Keep a simple register of approved tools, client constraints, access dates, and deletion steps.
Decision rule
Know when a formal baseline is justified
If a task contains client-confidential material, do not proceed on assumptions. CapitalGuard becomes useful when the work also involves repositories, connected tools, repeat client workflows, or evidence that must be shown back to the client.
CapitalGuard is relevant when the workflow includes repositories, recurring private work, credentials, connected systems, commands, or evidence that must be shared with another person. It does not inspect this account from the page or guarantee that an incident cannot occur.
Primary references