Travel itinerary details
Identifies documents containing references to travel itinerary details in Australian contexts. This information type is classified as personally identifiable information under applicable data protection regulations.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Topic false positive
- Jurisdictions
- global
- Regulations
- Information Privacy Act 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), GDPR
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- pii
- Scope
- wide
- Risk rating
- 4
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:travel\s+itinerary\s+details|travel\s+itinerary|flight\s+booking|booking\s+reference|passenger\s+name\s+record|hotel\s+reservation|accommodation\s+booking|trip\s+details|travel\s+plan)\b
Corroborative evidence keywords
travel itinerary details, travel, itinerary, details, contact, location, data
Proximity: 300 characters
Should match
travel itinerary details— Primary topic phrase matchtravel itinerary— Case-insensitive topic phrase matchflight booking— Alternative topic phrase matchbooking reference— Additional topic phrase matchTravel itinerary details: Recorded Name: Avery Teston Date of birth: 14/02/1988— Populated attribute field with a linked record field (85 tier)
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexaddress mac— Generic word pair from old broad template should not matchTravel itinerary details: Name: Date of birth:— Empty form: the heading and field labels without values must not corroborate themselves (discovery only)Policy guidance: this procedure explains how records about travel itinerary details are handled, who may access them and how long they are kept. It contains no records about any person or system.— Policy guidance naming the topic without any record (discovery only)Travel itinerary details: Name: Avery Teston— Record with the attribute label but no value: the label must not corroborate itself (discovery only)
Known false positives
- Common words and phrases related to travel itinerary details appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
- In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
- High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.