What changes here
How Perplexity creates this exposure
Perplexity combines AI search with conversations, uploads, projects or spaces, and optional organizational repositories or connectors depending on plan.
A connector does not create data, but it can make existing account permissions available through a new interface. The safe question is not only whether the connector is trusted; it is whether the connected account is broader than the task requires.
Enterprise connectors can include cloud storage and knowledge sources whose permissions determine what files can be searched.
The exposure path
Three steps from useful context to avoidable risk
- 1
Context enters
Enterprise connectors can include cloud storage and knowledge sources whose permissions determine what files can be searched.
- 2
Access carries it
Perplexity may use search queries and conversation history, uploaded files and projects, or connected storage and organizational repositories, depending on the surface and settings.
- 3
A real consequence becomes possible
A personal connector may expose private mail, files, contacts, calendar details, browsing context, or shared documents that were never intended for the current conversation. A business connector can turn an over-privileged account into a broad retrieval or action surface spanning customers, employees, projects, and internal operations.
Who should care
Why this matters for individuals and teams connecting AI to email, storage, messaging, calendars, workspaces, or internal systems
A personal connector may expose private mail, files, contacts, calendar details, browsing context, or shared documents that were never intended for the current conversation.
A business connector can turn an over-privileged account into a broad retrieval or action surface spanning customers, employees, projects, and internal operations.
This page does not claim that Perplexity has exposed your information. It shows the access conditions that make a review sensible before the next sensitive task.
Warning signs
Pause before adding more access
The authorization screen requests broad scopes and nobody recorded why each one is needed.
Read, create, edit, share, send, and delete actions are enabled together by default.
A connector remains active after a project ends or after the user’s role changes.
Five-minute safe check
Check Perplexity without exposing more data
Review connector permissions, project sharing, and source-system access for every connected repository.
Review the connector’s exact scopes in both the AI tool and the source service.
Test with a limited account containing synthetic data before connecting a primary mailbox or drive.
Confirm how to disconnect, revoke tokens, remove indexed copies, and review prior actions.
Reduce the risk
Controls to apply now
Limit connectors to approved folders and remove access when a project or user role ends.
Use a least-privilege account or service identity created for the specific workflow.
Separate read-only retrieval from write, send, share, delete, and financial actions.
Set a recurring owner and expiry date for every connector rather than leaving access permanent.
Review ai data retention or training choice.
Review library, projects, and shared sessions.
Review file, connector, and organization permissions.
Decision rule
When CapitalGuard is the right next step
If the assistant has no connectors, document that and keep it true. If it can retrieve or change business data across services, create an access map before adding another integration.
CapitalGuard focuses on repository and tool-connected exposure: what an AI workflow can read, change, execute, trust, or transfer. It does not inspect your private Perplexityaccount from this page, replace the provider's privacy controls, or guarantee that an incident can never happen.
Primary references