Regional privacy restrictions

privacy

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.

Detection

Pipeline configuration has one privacy policy constant with no per-jurisdiction override keyed to the data subject's region.

Mitigation

Maintain a jurisdiction-keyed policy table (aggregation minimums, consent requirements, retention) rather than one global constant
Route each record's privacy treatment by its resolved jurisdiction, re-evaluating on any boundary or law change

Affected conversions

Admin polygons → H3 (weighted crosswalk) weighted
Point → H3 exact
Point+radius → H3 approximate