Interactive publication
Back to the cataloguePrivacyCase 08 of 12
Regional privacy restrictions
Location-data privacy law varies by jurisdiction (GDPR/ePrivacy in the EU, CCPA/CPRA in California, and others), so a pipeline using a single global minimum-aggregation or consent policy can be non-compliant in stricter regions or needlessly conservative in others.
Class
Case to account for
Affects
3 conversions
01
Detection
Pipeline configuration has one privacy policy constant with no per-jurisdiction override keyed to the data subject's region.
02
Mitigation
01
Maintain a jurisdiction-keyed policy table (aggregation minimums, consent requirements, retention) rather than one global constant
02
Route each record's privacy treatment by its resolved jurisdiction, re-evaluating on any boundary or law change
03
Affected conversions
PointH3
OPENPoint+radiusH3
OPENAdmin polygonsH3 (weighted crosswalk)
OPENMore in Privacy
Consent-based precision reductionDeclared unit below the precise-location thresholdDevice trajectory exposureDifferential privacy noise calibrationHousehold-level targeting riskK-anonymity thresholdsMinimum aggregation windowResolution degradation policySmall-cell re-identification riskSparse-audience suppressionTemporal leakage