Skip to main content
PlainSight
How it works
Back to PlainSight
Privacy notice

Your content is processed, not stored.

Last updated 12 August 2026

Submitted content

PlainSight processes the text and audience information you submit to produce an analysis and, when requested, a rewrite. You may paste text or upload one supported document. Document files are used only to extract their text in memory and are not saved by PlainSight. Submitted content and extracted text are not written to the PlainSight database.

When AI rewriting is available, the relevant content, audience context, selected recommendations and protected passages are sent securely to OpenAI for processing. OpenAI is instructed to return a constrained rewrite. PlainSight then performs its own meaning and clarity checks before showing the result. If AI is unavailable or does not pass those checks, PlainSight uses its deterministic rewrite instead.

Information PlainSight keeps

  • Demo usage: keyed hashes derived from a browser identifier and network address, action type, word count and timestamp. The original identifiers and submitted content are not stored in these records.
  • Waitlist: your email address, signup source and signup time when you choose to join.
  • Operational logs: request outcome, duration, counts and error type. Logs are designed not to contain submitted text or email addresses.

Analytics and service providers

PlainSight uses Google Analytics and Vercel analytics to understand page use, product interactions and performance. These services may process device, browser, approximate location, referral and interaction information and may use cookies or similar technologies. PlainSight analytics events do not include submitted content, audience descriptions or email addresses.

PlainSight relies on Vercel for hosting, Supabase for isolated waitlist and demo-usage storage, OpenAI for eligible AI rewrites, and Google for analytics. Each provider handles data under its own terms and privacy practices.

Your choices

You can use browser controls or privacy extensions to limit analytics cookies. You can also choose not to join the waitlist. If you want your waitlist record corrected or removed, contact the PlainSight project owner through the channel that invited you to the beta.

Important limits

Do not submit secrets, passwords, health records, identity documents or other information you are not authorised to process. Password-protected documents are not supported. PlainSight is a clarity tool, not a secure document repository.

PlainSightClarity without losing meaning.
PrivacyTerms
© 2026 PlainSight