Information collected
Lex Engine collects account name, work email, subscription and entitlement state, API usage, support requests, watchlists, saved searches, and security/operational logs. Stripe handles payment-card information; Lex Engine does not store full card numbers.
Public legal data
The platform processes public court, regulatory, and government records. Public records may contain names and other identifying information. Lex Engine adds provenance, structured metadata, automated classifications, and entity links.
How information is used
Information supports account access, billing, customer support, security, abuse prevention, product operation, aggregate performance analysis, source-linked alerts, and legal obligations.
Analytics and cookies
Lex Engine currently uses cookie-free, first-party traffic measurement. Server logs may contain IP addresses and user-agent data for security and operations. Growth analytics store one-way visitor hashes rather than raw IP addresses.
Sharing and processors
Information may be processed by infrastructure, payment, email, monitoring, and storage providers used to operate the service. Lex Engine does not sell customer account information. Public legal records remain attributable to their official sources.
Retention and security
Records are retained as reasonably necessary for service, security, accounting, dispute resolution, and legal obligations. Reasonable technical safeguards are used, but no system is completely secure.
Your requests
You may request access, correction, deletion, or export through Support. Public-record correction requests can use the Data Corrections workflow. Applicable law may require retention or limit deletion.