Legal

Legal Readiness

WarpIntel legal readiness checks that policy pages, trust evidence, attribution, security reporting, revenue disclosures, and no-unlock boundaries are visible for public review while private EVE data and provider credentials stay excluded.

StatusReady

Public legal coverage is count-only and no-secret.

Policy Pages11

Legal, privacy, security, attribution, data-rights, and disclosure pages are represented.

Trust Sections6

Public trust evidence is linked without revealing setup packets or credentials.

Boundaries20

Security, trust, revenue, and data-exclusion boundaries are counted.

3Manifests
6Security checks
14Attribution sources
4No-unlock disclosures
8

Legal Hub Links

Policy and disclosure links are counted as public review surfaces.

4

Report Fields

Security reports request useful context without publishing raw vulnerability reports.

4

Safe Testing Rules

Responsible disclosure guidance keeps testing away from private data and abuse paths.

3

Private Data Exclusions

Private EVE data, account exports, logs, and provider details stay out of public legal readiness.

Boundary

Legal Pages

Represented as aggregate public readiness only.

Boundary

Trust Sections

Represented as aggregate public readiness only.

Boundary

Security Contact

Represented as aggregate public readiness only.

Boundary

Attribution Notices

Represented as aggregate public readiness only.

Boundary

Revenue Disclosures

Represented as aggregate public readiness only.

Boundary

Secret Exclusion

Represented as aggregate public readiness only.

No-Secret Legal Rule

Public legal readiness health exposes aggregate legal-page, trust, security, attribution, revenue-disclosure, manifest, link, and safety-boundary counts only; it does not expose OAuth tokens, provider credentials, API keys, database URLs, raw pasted inputs, raw support messages, raw vulnerability reports, account exports, raw logs, raw IP addresses, private EVE data, payment profile details, or separate-project account details.