Security & Trust
This page describes how Tripa protects your corporate travel data. It is maintained by the Tripa team and summarizes controls that are currently enabled in the app. It is not an independent audit or a certification.
Traffic between your browser and Tripa is encrypted in transit with TLS. Data at rest — trips, bookings, expenses, approvals — is stored in a managed Postgres database that encrypts disk contents by default.
Secrets used to reach travel and AI providers are held server-side and never exposed to the browser.
Every user has one or more roles: employee, travel_manager, finance_manager, or company_admin. Roles are stored in a separate table so they cannot be self-elevated from the profile record.
Row-Level Security enforces access at the database layer — an employee can only see their own trips, expenses, and virtual cards; managers see their company's data; nobody can read another company's records.
The AI travel agent operates within company-defined policy: maximum flight/hotel/car spend, approved cabin classes, minimum hotel star rating, and an approval threshold. These are enforced server-side on every booking call — the agent cannot bypass them by ignoring a tool result.
When a booking exceeds the approval threshold, the platform automatically opens an approval request and blocks the booking until a manager decides.
You (the customer): keep account credentials safe, review policy limits, and manage employee roles and off-boarding.
Tripa: keeps the platform patched, enforces RBAC/RLS, and monitors for platform-level anomalies.