Xaigh security for worker and employer operations

01 / Data and service boundaries

Keep access reviewable.

Worker, employer, payment, message, and support records are separated so each sensitive path can be reviewed, owned, and checked before it goes live.

Storage boundary

Persistent worker and employer records keep a clear owner and review path.

Connection boundary

External and private connections are reviewed for access and data exposure before launch.

Secret handling

Runtime secrets stay out of tracked examples and are managed through approved secret storage.

02 / Identity and access

Access follows the account and the action.

The signed-in account, its role, and the requested action define what can be reached. Sensitive account and employer operations stay behind role checks.

01Sensitive-action review

Billing, worker records, and admin actions stay behind role checks before broader access is enabled.

02Identity handoff scope

Directory, sign-in, and admin setup requests stay in review until the data contract is approved.

03 / Recovery and evidence

Plan for interruptions. Keep the decision trail.

Critical paths need recovery behavior, service boundaries, and review checks before launch. Operational records keep the owners and review state traceable.

01Recovery

Critical work, account, and support paths are reviewed with rollback and health-check expectations before launch.

02Evidence retention

Operational records keep requests, owners, and review state traceable for support and security review.

Responsible disclosure / 04

Report a security concern.

Send security reports through Xaigh intake with the affected route, account impact, reproduction steps, and evidence. Reward programs or public bounty terms require separate written approval.

Submit a vulnerability report

Certification and uptime commitments are reviewed separately; this page does not claim either.