Privacy Risk Assessment Checklist

Privacy Risk Assessment Checklist

Before deploying location-aware IoT, evaluate these privacy dimensions:

Data Collection

[ ] Minimal precision: Collect only precision needed (zone vs. coordinates). [ ] Temporal limits: Limit how often location is recorded. [ ] Contextual necessity: Location only collected when feature requires it. [ ] On-device processing: Process location locally when possible, not cloud.

Precision Guidelines:

Use Case Precision Needed Privacy-Preserving Approach
Presence detection Room-level PIR sensors (anonymous), zone-based (no coordinates)
Home automation Geofence (100m radius) Coarse location API, on-device geofence detection
Asset tracking Building-level BLE proximity (which beacon, not coordinates)
Navigation Meter-level Ephemeral (don’t store history)
Emergency/Safety Precise coordinates Only transmitted on SOS trigger

Data Storage

[ ] Retention limits: Automatically delete old location records using the stated 24–48 hour default. Connect expiry to the feature’s purpose and verify deletion in the main service and planned copies.

[ ] Local-first: Keep location on the device when possible. Local geofence processing can produce a zone event for upload without retaining a server-side coordinate trail.

[ ] Anonymisation: Where centralised storage is required, protect identifiers through hashing or encryption and separate identity from location events. Removed names do not resolve re-identification risks from repeated timestamps or device identifiers.

[ ] Aggregation: Store the zones or patterns needed for the task rather than coordinate trails. Shared aggregate outputs may also need suppression thresholds or differential privacy noise.

Data Sharing

[ ] User control: Provide a separate sharing choice for each feature. Make active, paused, and shared states visible so users can understand when location is available to another person.

[ ] Purpose limitation: Connect each shared event to the stated feature and give each role the precision needed for its task. Review a new use before expanding the sharing boundary.

[ ] Third-party audits: Check data destinations, including SDKs, exports, and partner integrations, against the requirement to exclude sharing with advertisers or data brokers.

[ ] Consent transparency: Explain who receives location, why they need it, and whether they see live position, zone events, history, or aggregate counts. Review changes to audience or default visibility before release.

User Controls

[ ] Pause tracking: Let users temporarily disable tracking without uninstalling the app. Show the paused state and test that new location collection stops, then check the behavior when tracking resumes.

[ ] History access: Provide a way to view and export the user’s location records. Retain enough indexing to find those records without requiring a raw coordinate trail.

[ ] Selective sharing: Let users choose who can see location, including family or public audiences. Explain the detail available to each audience and any safety exception.

[ ] Deletion: Provide a one-click route to delete location history. Follow the record through planned stores and copies, verify the stated end state, and record any copy that needs more time and why.

Technical Safeguards

[ ] Encryption in transit: HTTPS/TLS for location transmission. [ ] Encryption at rest: Location data encrypted in database. [ ] Access controls: Strict authentication for location queries. [ ] Audit logs: Track who accessed location data and when. [ ] Differential privacy: Add noise to aggregated location statistics.

Back to the chapter