Review the entire file-based session before sharing it, including uploaded material, quoted passages and context revealed by your questions. If you cannot establish what sharing exposes, prepare a separate, approved summary instead of sharing the session.
Why the sharing caveat matters
Perplexity says uploaded files are used to customise responses and are not accessed or shared for other purposes unless a session is shared. Its stated retention is 30 days, or seven days for Enterprise Pro.
That caveat makes sharing a separate review decision. It does not, in the supplied evidence, establish exact recipient permissions, download options or onward-sharing restrictions. Do not treat an assumption about those details as a privacy control.
Build an exposure inventory
As practical editorial advice, review four layers before releasing anything:
- Files: What documents entered the session? Were they public, synthetic or approved for this use?
- Extracts: Does the conversation reproduce names, contact details, unpublished figures or lengthy passages?
- Questions: Do prompts disclose an internal objective, investigation or relationship absent from the files?
- Answers: Does the response combine harmless details into a more revealing account?
For each item, record its location, intended audience, reason for inclusion and approval status. Mark uncertain items “hold”, rather than interpreting silence as permission. Do not upload customer or private material to complete this exercise.
Hypothetical sharing worksheet
Suppose an Indian student group uses a synthetic eight-page report about campus water consumption. The session includes three report excerpts, a fictional committee name and a question about a possible budget cut.
Their worksheet could contain:
- Report pages 1–3: synthetic figures; useful to readers; retain in a standalone summary.
- Committee reference: unnecessary context; remove from the proposed release.
- Budget-cut question: speculative, not a report finding; exclude.
- Final recommendation: depends on an unverified assumption; label it or rewrite it.
Evaluate success by asking whether every released sentence has a clear purpose and whether a reader could mistake speculation for an approved finding. This is a hypothetical review, not a test of sharing permissions.
Decide whether to share or stop
Proceed only when the material and sharing boundary are sufficiently understood for the intended audience. Otherwise, stop session sharing and distribute a newly prepared, reviewed extract through an appropriate channel.
If comparing paid access, check the AI tools catalog for access format and save the offer terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Perplexity file security and privacy establishes the stated use, sharing caveat and retention periods. The exposure inventory and release decision are editorial advice, not verified recipient permissions or legal advice.