Trust, security, and legal

Trust begins with what we can show.

A trust statement should be as traceable as an official record. Reviewed policies and deployment evidence—never unverified badges—are the basis for Legivera’s security, privacy, and subscription commitments.

Official-source provenance & publication limits

Official-source provenance

Official legislative records, actions, formal amendments, and text versions link back to the publishing government source. Official source dates stay separate from Legivera’s observation timestamps, and Legivera does not provide legal advice or substitute for official publications.

Publication & coverage limitations

Only reviewed, certified, customer-published jurisdictions and sessions are served—never inferred from adapter code or 50-state assumptions. Partial history, unknown earliest years, stale snapshots, and facet gaps remain explicit on Coverage.

Account, session & credential safeguards

Hosted identity & static-site isolation

Customer sign-in, email verification, hosted phone verification (when required), and MFA recovery run on the isolated customer application and hosted identity provider. This public static site sets no cookies, runs no analytics, and holds no customer session or workspace data.

Private RSS & vulnerability reporting

Basic Private RSS uses HTTP Basic authentication (username rss) with a one-time volatile password cleared when hidden—never placed in URLs, HTML, clipboard APIs, or browser storage. Request secure follow-up for suspected security issues via Help and support without sending credentials or incident evidence.

Explicit non-commitments

Discuss your requirements →Report a privacy or security issueInspect coverage scope →