The real workflow
Where Cursor enters the work
A freelance coding agent may read a client repository, run commands, edit files, and use local credentials from the same working environment.
Cursor combines an AI editor with codebase context, indexing, agent features, model providers, extensions, web search, and optional background or connected tools.
A single Cursor workspace can contain client code, local files, indexes, chat context, and model-provider requests.
Privacy Mode affects data use and retention, but it is not the same as a repository access boundary. Users still need to control workspaces, indexing, ignored paths, extensions, tools, and commands.
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
open files and editor context
codebase indexing and embeddings
agent commands, extensions, web search, and MCP tools
Settings to verify
Privacy Mode and codebase indexing
.cursorignore and workspace scope
Agent, extension, web, network, and MCP permissions
Why this context matters
The consequence for freelancers
A freelancer carries both the delivery risk and the trust risk when one convenient AI workflow mixes personal accounts with confidential client work. 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.
Each client has a clear access boundary, sensitive inputs are minimized, and the freelancer can explain the controls without exposing the underlying data.
Context decision
Three questions before adding access
Did the client approve this tool, account type, and category of information for the stated task?
Can names, credentials, production records, or unpublished work be replaced with a synthetic example?
Does this account and connected workspace belong to the correct client rather than a personal or reused environment?
Evidence goal: Keep a client-by-client access note that records authorization, approved tools, data limits, account ownership, and the deletion or handoff step.
A repeatable review
Four steps, no sensitive data required
- 1
Write down the exact Cursor account, workspace, project, device, and connected service used in this workflow.
- 2
Confirm client authorization, Privacy Mode, workspace boundaries, indexing, model choice, and data-use settings.
- 3
Assign the decision and next review to the freelancer responsible for the client account; do not leave the access boundary as an unwritten assumption.
- 4
Use a separate client workspace and account with enforced privacy settings and minimized indexing. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Use a separate client workspace and account with enforced privacy settings and minimized indexing.
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