Security

Operational trust starts with clear controls and honest claims.

PaxRelay is designed around tenant isolation, least privilege, controlled integrations, data minimization and a traceable record of actions. Security representations are limited to controls that are implemented and verified.

Discuss security Explore the platform

Certifications or independent attestations are not claimed unless they have been completed and can be substantiated.

Secure by design, specific in implementation.

Security requirements are considered in data boundaries, integration design, access control and operational workflows. Controls still need to be tested in the environment where they run.

Collect only what the workflow needs.

Passenger and operational data should be limited by purpose, retained only as required and kept out of logs, analytics and unrelated systems.

Tenant isolation: Separate operator data and enforce access boundaries at the application and data layers.
Least privilege: Limit people, services and integrations to the permissions required for their role.
Auditability: Record operational events, decisions, approvals and communication outcomes.
Encrypted transport: Use secure transport for browser, service and integration traffic.
Secret handling: Keep privileged credentials server-side and outside source control and browser bundles.
Controlled integrations: Authenticate sources, validate payloads and scope each connection to its purpose.

Certifications or independent attestations are not claimed unless they have been completed and can be substantiated.

Review the controls relevant to your operation.

We can discuss data flows, access boundaries, integration authentication and the evidence your technical review requires.

Book a demo Contact us