Privacy policy
How TravelHub uses account and workspace information, which services support the platform and how to contact us about your data.
Who is responsible?
Rankup, in Tunisia, is the contact for TravelHub account administration and platform operation: contact@e-travel.pro. Your agency determines why it collects and uses traveler records and who may access them. Questions about a traveler record should first be directed to the agency managing that record; platform-related requests can be sent to Rankup.
Information processed
Account email and authentication records; country and contact phone required at new signup, stored with the preferred language in account metadata for administration and support, without SMS or implied marketing; organization name, locale, time zone, memberships and invitations; flight occurrences; traveler names, optional emails, internal references and groups; operational impacts; tasks, notes, incident and audit history; notification preferences and delivery metadata; CSV import results; and subscription identifiers, status and usage. Original CSV files are parsed in the browser and are not stored as files. Passwords are handled by Supabase Auth. TravelHub does not collect card details or passport numbers.
Purposes and access
Information is used to provide requested account and workspace functions, coordinate operations, enforce usage limits, manage notifications and subscriptions when enabled, and prevent abuse. It may also be retained or processed to meet applicable legal obligations and investigate security incidents. Access depends on organization membership and role. Agencies are responsible for the lawful collection and use of the traveler information they enter. No advertising tracking is installed.
External services
TravelHub uses Supabase for authentication and database storage, OVHcloud for active website hosting and Resend for transactional email. The previous Netlify host is retained for rollback. The configured Supabase project is in Frankfurt and the Resend sending region is Ireland; these providers and their subprocessors may use international infrastructure. Commercial payments are not currently active. The payment provider and its privacy information will be identified before any future purchase. Flight-data requests, when enabled, use flight identifiers, route and date rather than traveler names. Live flight monitoring is not currently active.
Retention
Account and operational information is kept while needed to provide the workspace, handle support and security matters, or meet applicable legal obligations. Contact us to request account closure or deletion of information your organization controls; we verify authority and assess any records that must be retained. Provider-held information follows the relevant provider’s retention terms. Demo changes are fictional and remain in your browser until you reset the demo or clear site data.
Your requests
Contact contact@e-travel.pro for access, correction, export, objection or erasure requests. Identity or organization authority may need verification. Applicable rights and supervisory channels depend on your jurisdiction. No automated consequential decision about a traveler is made, and traveler messages require human review.