Security at TripOS.
Your customers' data, treated like it is yours.
Passports, payment details, itineraries and the record of every conversation. TripOS holds them in your region, encrypts them end to end, and lets you see every access. Here is exactly how.
How it is protected.
Eight controls, each one you can check.
Hosted in your region, on isolated infrastructure.
Each workspace lives in one region and never leaves it. Production runs in private networks with no public database endpoints, and every change goes through a reviewed deployment.
- Regions: Mumbai (India), Frankfurt (EU and UK), Singapore (Gulf and South-East Asia)
- Separate production, staging and development environments with no shared credentials
- Infrastructure defined in code, reviewed and applied by a pipeline, not by hand
- Tenant isolation enforced at the database row level, tested on every release
Sub-processors.
Who else touches the data, and why.
Every provider below is under a data-processing agreement with TripOS. Customers are told thirty days before a provider is added or changed.
Last reviewed 1 October 2026. The full list with DPA references is in the security pack.
Responsible disclosure.
Found something? Tell us, and we will fix it and credit you.
Write to security@tripos.travel with steps to reproduce. We acknowledge within one business day, fix critical issues within seven days, and publish credits with your permission. Testing against your own trial workspace is welcome; testing against other customers' data is not.
Questions people ask.
In the region you chose when the workspace was created: Mumbai for India, Frankfurt for the EU and UK, Singapore for the Gulf and South-East Asia. It does not move between regions, and backups stay in the same region.