This is a practical inventory guide, not legal advice or a universal retention schedule. A responsible privacy professional should resolve applicable national, contractual and sector-specific duties before a live-data decision.
Separate documents by what they are needed for
Begin with the service being delivered. A visa-support document may be needed for arranging entry; an assistance form may support a particular journey; an invoice may support an accounting obligation. A folder named after a trip does not make these purposes identical.
The European Commission’s GDPR principles explain purpose limitation, minimisation and storage limitation. A retention rule should identify which purpose persists and the basis for keeping the necessary record.
Build a document inventory before choosing periods
| Document category | Question for the owner | Copies to check |
|---|---|---|
| Passports and identity copies | Which specific booking or visa step needs this copy? | Mailbox, upload folder, forwarded attachment |
| Visa paperwork | Is support ongoing, completed or disputed? | Booking system, local-agent email, shared folder |
| Medical or assistance forms | Which health information is necessary and who needs access? | Restricted form store, operations inbox, supplier handoff |
| Booking records and invoices | Which service, accounting or claim obligation applies? | CRM, booking system, finance records |
These are illustrative categories, not a prescribed list of documents to collect. Avoid collecting information the service does not need.
Health information needs an additional legal check
Medical forms can contain health data, a special category under GDPR. An Article 6 basis alone is insufficient; an applicable Article 9 condition is also needed. The European Commission explains these additional conditions. Do not assume a customer’s general booking agreement resolves them.
Operationally, keep health-related access narrow and separate it from ordinary marketing or booking archives. Document who can use the form and for what journey-related task. Review supplier handoffs and avoid sending the full form when a smaller instruction would meet the need.
Why a single post-trip deletion period is inappropriate
GDPR links retention to necessity for the purpose. Applicable legal duties and legal claims can affect that assessment. Articles 5 and 17 of the GDPR set out storage limitation and the right to erasure, including exceptions. An unresolved complaint or statutory record duty should be assessed for the records it actually concerns.
Do not retain an entire passport-and-medical folder simply because an invoice must remain. Conversely, do not erase a necessary record solely because the holiday ended. Record a specific decision and review date for each exception.
A practical post-booking review checklist
- Identify the record category, processing purpose, controller role and owner.
- Map copies in booking systems, CRM, shared drives and individual or shared inboxes.
- Check whether the purpose continues and which approved rule applies.
- Route open claims, legal holds and unclear national obligations to an authorised reviewer.
- Review sharing links and staff or supplier access as well as storage.
- Record approved actions, completion evidence and unresolved locations.
- Set a next review date for necessary exceptions and recurring workflows.
Test with a synthetic trip first
Illustrative example: create a fictional trip inventory with an identity-copy category, an assistance-form category and an invoice category. Give each a different owner. Test whether the team can identify all copy locations and return an approved decision without attaching any actual customer document.
Periodic automation could surface due reviews, flag missing owners and collect completion status. The EDPB’s SME guidance supports documenting processing and considering storage and accessibility by design. Trace is validating a travel retention pilot; monitoring, system integrations and remediation are proposed capabilities.
Explore the Travel Privacy Pilot
Related: visa and immigration case retention, retention monitoring and Trace’s current data boundaries.
Sources and editorial responsibility
Trace editorial team maintains this guide using the primary sources linked above. Updated 13 November 2026. Jurisdiction-specific expert review has not been completed. No customer outcome, fixed retention period or legal guarantee is claimed.