Operational context deserves careful boundaries.
Workspace access is controlled through authentication, organization membership and team roles, with checks enforced on the server and database.
An organization is the data boundary
Business records belong to an organization. PostgreSQL row level security, server-side membership checks and tenant-bound foreign keys restrict access. Admins manage settings and invitations; agents coordinate operations; readers can view records.
Collect less, expose less
Traveler passports and payment-card information are not collected. Private pages are excluded from search indexing. Provider keys, billing secrets and privileged database keys are kept on the server.
Payment information stays outside TravelHub
Commercial purchases are currently closed. When checkout is enabled, payment-card details will be handled by the payment provider identified before purchase, rather than stored in Flight Ops. A payment return URL alone cannot grant subscription access.
Retention and requests
Archiving stops monitoring and does not restore used allowance. Account and operational information is retained while needed for the service, support, security or applicable legal obligations. Contact contact@e-travel.pro for an access, correction, export or erasure request; we may verify your authority over the organization before acting. See the privacy policy for further information.
Clear limits, no invented badges
No certification, uptime SLA or independent security audit is claimed. Please report a suspected security issue privately to contact@e-travel.pro without including passwords or traveler documents.
The next change deserves a clear response.
See how your team could handle it. Explore the demo with a free confirmed account.