TRAVEL CONFIRMATIONS · PRIVACY

You can automate reservation organization without handing over your whole inbox.

A travel confirmation already contains most of the information an itinerary needs. The privacy question is how much access a product really needs to extract it.

The selective-forwarding model

Instead of connecting an entire mailbox, a traveler forwards only the confirmation they want the trip app to ingest. That can include airline, hotel, rail, rental-car or dining confirmations. The traveler decides what enters the product.

What useful software can learn from one confirmation

Timing

Departure, arrival, check-in, check-out and reservation times.

Place

Airport, hotel, restaurant, station and street-address context.

Booking identity

Carrier/property, confirmation reference and reservation type.

Trip relationships

Whether the reservation belongs with an existing trip and whether timing overlaps another plan.

Ternivo V1 deliberately starts here.

Travelers can forward the confirmations they choose to a private Ternivo trip address. Broad mailbox access is not required for the V1 reservation-forwarding workflow. The goal is useful automation with a smaller data-access surface.

This page describes Ternivo’s V1 product design; it is not a claim that every travel application uses broad mailbox access.