Security

A focused security overview

TravelVerse uses account access controls and provider-hosted payment handling as part of its current product design. TravelVerse retains payment references and payment status for relevant administration rather than raw payment-card data as designed.

TravelVerse handles travel requests, account information, provider communications, and support information with care. The public information on this page is intentionally narrow and describes the product-design direction without claiming a security certification, audit result, uptime commitment, or complete security programme.

Areas TravelVerse considers

Security work follows the information and service paths that matter to travellers, passengers, suppliers, drivers, and support teams. It includes consideration of:

• Account access, sign-in, recovery, privileged access, and access reviews.
• Provider-hosted payment handling and the payment references or status TravelVerse retains.
• Storage, provider integrations, flight search, accommodation requests, ground mobility requests, and information exchanged with each service.
• Sensitive travel information, uploaded documents when a service requires them, support conversations, AI-assisted support, logs, and backups.
• Incident response, escalation, customer communications, evidence preservation, and post-incident learning.
• Vendor safeguards, service configuration, access boundaries, and the information needed to assess provider risk.

Payment and sensitive information

Payment details are handled through the relevant provider-hosted payment experience. TravelVerse's design retains payment references and status rather than raw card data. Do not send full payment-card numbers, security codes, passwords, or unnecessary travel documents to TravelVerse by ordinary email.

A travel request may contain information that needs careful handling, including passenger details or a document detail needed for a specific service. Share only what the relevant flow asks for and use the intended secure route when one is provided.

Providers and shared responsibility

Airlines, accommodation providers, mobility providers, payment providers, hosting or authentication services, support tools, and other vendors may apply their own security practices and terms. TravelVerse considers provider safeguards and the information exchanged with each integration, but this page does not make a security promise on behalf of a third party.

A provider's own security incident, outage, or access decision can affect a travel service. Contact TravelVerse if a concern relates to a TravelVerse request or communication so it can be routed to the relevant party where appropriate.

Report a security concern

Send a security concern to hello@travelverseglobal.com with the subject and details needed to identify the affected page, account, request, or behaviour. Use a safe description and ask for a suitable way to continue the conversation if the detail is sensitive.

Do not send passwords, full payment-card details, security codes, or unnecessary passport or travel-document information in the first message. This email is not an anonymous channel. TravelVerse does not promise a particular response time, investigation result, or remediation outcome through this public route.

What this page does not certify

No public statement on this page should be read as a certification, independent audit, penetration-test result, encryption claim, multi-factor authentication claim, bug-bounty promise, uptime guarantee, or guarantee that a security incident cannot occur. Controls and provider safeguards can change, and important claims require current evidence before they are made publicly.

For privacy questions about personal data, use the Privacy Policy and contact hello@travelverseglobal.com. For immediate safety or travel emergencies, contact the relevant local emergency service or travel provider rather than relying on this email address.