Security & Trust
This page describes controls currently implemented by Lexis Defender. It does not claim independent certification or publish unverified uptime figures.
Implemented safeguards
Saved chats and case data are read through authenticated server routes scoped to the signed-in account and selected conversation ID.
Traffic is served over HTTPS in deployed environments. Saved chat messages use authenticated server-side encryption when the production encryption key is configured, and cloud providers apply encryption at rest for managed storage.
Card details are entered on Stripe-hosted payment pages. Lexis Defender stores billing identifiers and entitlement status, not full card numbers.
Billing, credentials, and workspace data cannot be read or changed directly through the browser database client; access is enforced on the server.
How case data is handled
Names, dates, addresses, and other facts you provide may be retained in a matter because accurate legal drafting requires them.
Content submitted to AI features is sent to the configured AI service to produce the requested result. See the Privacy Policy for service-provider details.
You can delete individual chats and documents in the product or request account deletion through the documented process.
Report a security concern
Email support@lexisdefender.com. Do not include passwords, payment-card data, or unnecessary case details.