Controls LegisDex can point to directly in the current product, including industry-standard application safeguards used in day-to-day operation.
Contract chat and compliance workflows sit behind sign-in so active work stays inside account-scoped workspaces rather than open public pages.
Compliance reviews surface pass, fail, and review outcomes together with extracted values and evidence snippets so teams can inspect what triggered each flag.
LegisDex uses common SaaS controls such as bcrypt password hashing, rate limits on key workflows, and Stripe webhook signature verification in billing flows.
Shared chat links open in a read-only view and are marked noindex, while privacy, terms, support, and billing pages remain publicly accessible for review.
Trust comes from access control, input validation, traceable output, and operational safeguards around the workflows teams use most.
Control 01
LegisDex keeps the public site open while chat and compliance routes require authentication before contract analysis begins.
Control 02
The compliance flow checks whether an upload appears to be a contract before producing rule-by-rule output.
Control 03
Reviews expose evidence snippets, extracted values, and structured status outcomes so teams can understand the basis of a flag instead of relying on a score alone.
Control 04
Rate limits protect high-traffic workflows, and Stripe billing events are processed only after webhook signature verification succeeds.
Public references available for baseline diligence and operational questions.
Review the public description of data categories, provider groups, retention language, and user rights.
See the commercial terms covering service use, billing, and platform responsibilities.
Use the support form or contact email for product questions or follow-up on issues that need review.
Use the public contact address if you need clarification beyond the documentation linked here.