Security

Your documents open with your session, not with a public link.

A ticket or a voucher carries your name, your ID and your address. That is why none of your files has a URL that can be guessed or forwarded.

Always encrypted

AES-256-GCM at rest and TLS in transit. The original file lives in a private bucket with no anonymous access.

Only with your session

Every request looks the file up with your account as a condition. Another account, or nobody, gets a 404: it is not even confirmed to exist.

Sharing does not share files

If you send your itinerary, the other person sees the block and the time. The document does not travel in the link.

Real deletion

Delete the trip and the original is deleted. And even if you do not, it expires on its own: 90 days after the last day of the trip.

Try it

Request a document

This is how the server answers when someone requests Booking-Miraflores.pdf from an itinerary.

Who is asking

Booking-Miraflores.pdfNot requested
nobody has asked yet
A 404 and not a 403: confirming that the document exists is already information.

Who can see what

RoleItinerariesFilesBilling
YouYoursWith your sessionYes
AdministrationMetadata. Your screen only by impersonating you: 30 minutes, and it is auditedNo, except by impersonating you, with a recordCharges and allowances
Whoever gets your linkWhat you chose to shareNoNo
The keys for external services live in server environment variables. They never reach the browser.
Your files are not shared with anyone. The model that builds the itinerary receives the extracted text, not the file, and its terms do not allow using it for training.
Served without cache: neither the browser nor any edge keeps a copy.