Security Architecture
Last updated: June 18, 2026
This page is maintained by Rover Travel, LLC to answer common security questions about the Rover platform. It describes controls that are enabled today and is not a third-party certification or independent audit.
Hosting and platform
Rover is built on Lovable Cloud. The application database, authentication, and server functions run on the managed Lovable Cloud (Supabase) infrastructure. Encryption, backups, network controls, and physical security of the underlying infrastructure are provided by the platform vendors and are not separately certified by Rover.
Authentication
- Email + password sign-in, with session and refresh tokens managed by the platform auth service.
- No anonymous sign-ups; every action is tied to an authenticated account.
- Passwords are never visible to Rover staff and are stored only as hashes by the auth service.
Authorization (Row-Level Security)
Every table that holds traveler or agent data is protected by Postgres Row-Level Security policies. Travelers can read and write only their own profile and trips. Agents can read only the trips that travelers have explicitly submitted to them. User roles are stored in a dedicated user_roles table — never on the profile record — to prevent privilege escalation.
Server boundaries
Privileged operations run inside authenticated server functions that re-validate the caller on every request. Service credentials live only in the server runtime and are never bundled into client code.
AI handling
AI itinerary generation runs server-side. Prompts include only the trip information needed to produce a plan; personal contact details and payment information are not sent to AI models.
Certifications
Rover does not currently hold SOC 2, ISO 27001, PCI DSS, HIPAA, or GDPR certifications, and does not offer a signed Data Processing Agreement. We will update this page if that changes.
Reporting a vulnerability
Please email security@rover.travel. We aim to acknowledge reports within two business days.
