Australian Property Title Reference (Lot/Plan)
Detects Australian property title and plan references used across state and territory land-title systems, including Lot/DP, Lot/SP, Lot/PS, Lot/LP, Lot/CP, title references, and folio identifiers. Requires land-registry context for enforcing tiers.
- Type
- regex
- Engine
- universal
- Confidence
- low
- Confidence justification
- Low confidence: the generic digits/digits format matches many non-property references such as date fractions, version numbers, and ratios. Corroborative evidence keywords such as property, title, lot, or DP are essential for reliable detection.
- Detection quality
- Partial
- Jurisdictions
- au
- Regulations
- AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth)
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- location, pii
- Scope
- wide
- Risk rating
- 4
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?i)\b(?:Lot|LOT)\s+\d+(?:/|\s+on\s+)(?:DP|SP|PS|LP|CP)\s*\d{3,7}\b
Corroborative evidence keywords
property, title reference, lot, deposited plan, DP, strata plan, SP, real property, address, age, birthday, citizenship, city, date of birth, [object Object], email, ethnicity, fax, first name, full name (+55 more)
Proximity: 500 characters
Should match
1/12345— Low-tier probe - generic lot/plan candidate without registry context23/1234567— Lot 23 in larger DP100/99999— High lot number in DPNSW Land Registry title: 12/DP123456— Bare lot-on-plan form with land-registry context (wired Pattern_property_lot_plan 75 tier)Lot 7/SP98765 on strata title, NSW— High-tier probe - labelled lot/plan with registry and state context
Should not match
1/1234— Only 4 digits after slash (below minimum of 5)1/12345678— 8 digits after slash (above maximum of 7)1-12345— Hyphen separator instead of forward slashInvoice 12/DP123456 was cancelled.— Lot-plan-shaped token in invoice context without land-registry evidence must not fire the 75 tierThe subdivision plan is under review.— Property topic without an identifierDocumentation example: NSW land title Lot 7/SP98765— Structurally complete but explicitly documented example
Known false positives
- Australian property-title and lot/plan terminology appearing in policy documents, templates, or land-registry guidance without a specific live parcel record. 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.