Perplexity: sensitive data
Purview DLP Perplexity AI · Search · DLP target perplexity.ai
Policy · none set
Policy changes re-score this app on the next sync, which starts right away.
Finding · Open
Risk score
45
Medium
People
1
Named in DLP events
Not blocked
1
1 DLP event · 30 days
Blocked
0
Policy stopped these
dlpnot-blockedcorroborated
Next steps
Recommended actions
- 01Perplexity trains on data unless a business tier or opt-out is used. Verify which tier these users are on.
- 02Every DLP match for Perplexity was audit or warn only (All Full Names). The policy sees the data leaving and lets it go. Move the rule to Block for these information types, at least for uploads and pastes to unsanctioned AI sites.
Purview
What went in and what stopped it
Audit only · 1
08-1609-14
Information types
| Type | Events | Matches |
|---|---|---|
| All Full Names | 1 | 6 |
Activities
AIAppInteraction1
Destinations
perplexity.ai1
Same app, other lanes
Related findings
- Medium40PerplexityEndpoint0 people
- Medium40PerplexityEmail1 person
- Medium29PerplexityGoogle Workspace (demo)5 people
Who
People
Identifiers come from device telemetry and proxy logs, so they may be account names rather than full directory entries.
| Person | Department | Source | Sign-ins · 30 d | Granted |
|---|---|---|---|---|
| n/a | Audit log | 0 | No direct grant |
Why
Evidence
- dlp_activity · Sep 13, 20261 DLP event for Perplexity by 1 person in 30 days: 0 blocked, 0 warned, 0 overridden, 1 audit only; types: All Full Names
Detail
{ "domains": [ { "count": 1, "domain": "perplexity.ai" } ], "byAction": { "warn": 0, "audit": 1, "block": 0, "unknown": 0, "override": 0 }, "policies": [], "applications": [], "sensitiveTypes": [ { "name": "All Full Names", "count": 1, "matches": 6 } ] } - dlp_audit · Sep 13, 2026AIAppInteraction to perplexity.ai by [email protected]: All Full Names ×6 (audit)
Detail
{ "policies": [], "recordId": "ual-0109", "application": null } - corroborationAlso found by another lane (mde:perplexity)
Detail
{ "findingKey": "mde:perplexity" } - corroborationAlso found by another lane (mail:perplexity)
Detail
{ "findingKey": "mail:perplexity" }