Account authentication
Agency accounts use managed authentication and verified user sessions. Password handling is delegated to the authentication provider rather than stored by Itiner application code.
Trust and data protection
This page explains the controls Itiner currently uses, what agencies remain responsible for, and where to report a security concern. It is not a certification or a promise that risk can be eliminated.
Last reviewed: 14 July 2026
Agency accounts use managed authentication and verified user sessions. Password handling is delegated to the authentication provider rather than stored by Itiner application code.
Database row-level access policies scope protected records to the relevant agency and authenticated user permissions.
Role checks restrict sensitive team and workspace actions. Agencies should remove accounts that no longer require access.
Published client portals use trip-specific tokenized links. Anyone who receives a valid portal link may be able to view that itinerary, so agencies should treat it as client information.
The production site redirects to HTTPS so data is encrypted while traveling between a current browser and the service.
Privacy, terms, cookie, and data processing pages describe the current contractual and data-handling commitments.
Report a concern
Email dakshbathla@navitallabs.com with the affected URL or account, what you observed, when it occurred, and a safe way to reproduce it. Do not include passwords, access tokens, or unnecessary client data.