Privacy
What Lawlight collects, and what it doesn't
This page describes only what Lawlight's own code actually does, verified directly against the application rather than written aspirationally.
What is collected
- Your email address, to sign you in and identify your account (via Supabase and Auth.js).
- The file name of each document you upload for analysis, and its status (processing, completed, or failed) — used to enforce the free-analysis limit and show your account history.
- The text of your question, when you use Ask LawLight.
What is not stored
Lawlight does not save the contents of the documents you upload. The document is read in memory to extract its text and generate your report, and that text is not written to Lawlight's database or disk — only the file name and the status of the analysis are kept.
Third parties involved
Analyzing a document or answering a question means sending the relevant text to Anthropic's API to generate the report. Signing in means sending your email to Resend to deliver the sign-in link, and to Supabase to store your account and usage records. Lawlight does not control how these companies handle data once it reaches them — read their own policies for that:
What this page does not claim
Lawlight has not implemented or verified a specific data-retention schedule, an automated deletion process, or a particular encryption standard beyond what Supabase, Resend, and Anthropic provide by default on their own platforms. No such guarantees are made here because none have been built or confirmed. There is currently no dedicated privacy contact address for this preview — that is a known gap, not an oversight being hidden.