LexMind · Security
Security and privacy approach
We design the first LexMind release around data minimisation, evidence that can be inspected and a clear human handoff.
Data flow for Contract Review
- Your browser sends an authenticated request over HTTPS.
- The API checks the file type, size, language and ten-page limit before reserving a credit.
- For P0, the Worker extracts text in memory and sends the requested text to the approved model endpoint.
- The original uploaded file is not retained by the P0 review boundary. Generated findings and account metadata are retained in the account workspace so history and quota controls work.
Controls in the current release
- Cloudflare Pages and Workers provide TLS at the public edge.
- Bearer sessions are stored as hashes in D1; verification codes are hashed and expire.
- Model and email credentials are encrypted Worker secrets, never committed to the front end.
- D1 records separate users, workspaces, reviews, quota events, referrals and audit events.
- Quota reservation and failure release are recorded so a failed review does not silently consume a credit.
- The site does not include advertising SDKs or contract-content analytics.
Provider and regional commitments
Live review stays disabled until a model provider and transaction-email provider are configured and reviewed for data region, DPA, retention and training-use terms. The selected provider and material changes should be documented before production traffic is enabled.
What the product cannot promise
No online service can remove every risk. Do not upload material you cannot share, and do not treat an automated result as legal advice or a substitute for local counsel. Report a suspected vulnerability without contract content to security@lexmind.vip.