Synthetic evidence only
Screenshots, fixtures, demos, and issue reports must avoid real taxpayer identifiers, documents, credentials, portal responses, customer details, and production screenshots.
Trust and safety
Public claims need evidence
This repository is open by design, so trust comes from narrow claims, synthetic examples, explicit product boundaries, and public source evidence rather than implied authority.
Source before confidence
Security, privacy, release, browser-local, dependency, and statutory claims must point to source, release, runtime, or official evidence before a professional relies on them.
Reserved marks and roles
The source license does not grant rights to imply endorsement, affiliation, certification, government approval, or official ComplyEaze operation.
Review the source evidence
These public files define the boundary behind this page.
- Security policy
Private reporting path and sensitive-data boundaries for public repository issues.
- Public claim policy
Evidence requirements and prohibited public readiness or endorsement claims.
- Dependency policy
Reviewed package, lockfile, workflow, lifecycle-script, and action-pinning boundaries.
- Repository settings
Protected-check, review-gate, Pages-guard, and repository posture evidence.
- Review and rectify
Required local and current-head review loop for meaningful public changes.