Real-time geolocation

Identifies documents containing references to real-time geolocation in international 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

Mixed

Jurisdictions

global

Regulations

GDPR

Data categories

pii

Scope

wide

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:real[\s-]+time\s+geolocation|GPS\s+coordinates|live\s+location|current\s+location|location\s+tracking|latitude\s+longitude|real[\s-]+time\s+tracking|geo\s+tracking|position\s+data|location\s+services|GPS\s+tracking)\b

Corroborative evidence keywords

real-time geolocation, real, time, geolocation, contact, location, data, GPS data, GPS coordinates, location data, location tracking, cell tower, triangulation, latitude, longitude, geo-fence, geofence, location history, field, column (+27 more)

Proximity: 300 characters

Should match

• real-time geolocation — Primary topic phrase match
• gps coordinates — Case-insensitive topic phrase match
• live location — Alternative topic phrase match
• current location — Additional topic phrase match

Should not match

• unrelated generic text without domain phrases — No relevant topic phrases present
• placeholder value 12345 — Random text should not match topic-specific regex
• address mac — Generic word pair from old broad template should not match

Known false positives

• Common words and phrases related to real-time geolocation 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 English (as the primary international business language), 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.

References

• https://eur-lex.europa.eu/eli/reg/2016/679/oj
• https://www.oaic.gov.au/privacy/your-privacy-rights/your-personal-information/what-is-personal-information