Your content is processed, not stored.

Submitted content

PlainSight processes the text and audience information you submit to assess clarity, show findings and provide suggested alternatives in the editor. 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 assistance is available, the submitted content and audience context may be sent securely to OpenAI during analysis to propose exact recommendation wording. For eligible changes, PlainSight may also send selected recommendations and protected passages to OpenAI. The Clarity Score, audience decision, protections and recommendation rules remain deterministic. PlainSight verifies proposed wording itself and uses the deterministic result when AI is unavailable or does not pass its checks.

Information PlainSight keeps

• Demo usage: keyed hashes derived from a browser identifier, network address and submitted content, plus a random workflow identifier, action type, word count and timestamp. These hashes help enforce limits and confirm that a rewrite belongs to the analysed copy. The original identifiers and submitted content cannot be recovered from these records.
• Waitlist: your email address, signup source and signup time when you choose to join.
• Contact messages: your name, email address, message, submission source, delivery status and submission time when you contact PlainSight.
• 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, Vercel Analytics and Microsoft Clarity to understand page use, product interactions and performance. Microsoft Clarity may capture behavioural metrics, clicks, scrolling, heatmaps and session replays. These services may process device, browser, approximate location, referral and interaction information and may use cookies or similar technologies.

Microsoft Clarity session replays may include content rendered in the document editor. Text entered directly into form fields is masked by Microsoft Clarity. PlainSight’s own analytics events do not include submitted content, audience descriptions or email addresses.

PlainSight relies on Vercel for hosting, Supabase for isolated contact, waitlist and demo-usage storage, Brevo for contact-message delivery, OpenAI for eligible recommendation previews and AI-assisted rewrites, Google for analytics, and Microsoft for behavioural 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 or use the contact form. If you want a contact message or waitlist record corrected or removed, use the Contact link in the footer.

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.