THE PILOTALL WAY

Security is an operating requirement.

Access controls apply to users, files, workers, and integrations.

Identity and session boundaries

Server-side Auth verification, confirmed email, role- and membership-based office authorization, and active office membership control access. JWT contents are not trusted without validation.

Tenant isolation

Queries use the office derived from membership. PostgreSQL RLS, explicit grants, and narrow privileged functions remain in force. URL parameters do not choose an office.

File controls

ClamAV and bounded structural PDF inspection are separate checks. Unavailable analysis fails closed. Public buckets and anonymous file sharing are not enabled.

Recovery limitations

An existing encrypted archive passed isolated restore verification. This does not certify current hosted backup coverage. Current recovery scope must be reviewed before production database changes.

Safe incident reporting

Record a request reference, time, and sanitized error category. Never attach credentials, tokens, taxpayer data, or unredacted client screenshots to an incident report.

BUILD TRUST INTO THE WORK

Start with a verified workflow.

Explore the product and its current limits before connecting a provider.

Read the getting-started guide →
Security is an operating requirement. | PILOTALL