LogoLogo
  • welcome
    • Introduction
    • Explain Like I’m Five
    • Data Protection and Privacy
    • Network Governance
      • MIP-1
      • MIP-2
      • MIP-3
      • MIP-4
      • MIP-5
      • MIP-6
      • MIP-7
      • MIP-8
      • MIP-9
      • MIP-10
      • MIP-11
      • MIP-12
      • MIP-13
      • MIP-14
      • MIP-15
      • MIP-16
      • MIP-17
      • MIP-18
      • MIP-19
      • MIP-20
  • Contribute
    • Map With Hivemapper
      • Device Models
      • Creating a Guild
        • Adding a New Driver
        • Token Splits
        • Access Control List
        • Giving Access to Locked Devices
        • Hivemapper Guild Resources
      • Authorized Resellers
      • Accessories
      • Driver FAQs
    • Train the Map AI
      • Landmark Label
      • Position
      • Azimuth
      • Merge
      • Confirm Position & Azimuth
      • Dashcam View
      • Dashcam Tilt
      • Speed Limit
      • Speed Type
      • Turn Restrictions - No Turns 1
      • Turn Restrictions - No Turns 2
      • Confirm Attribute
      • Confirm Class
      • Stop Sign
      • Traffic Light
      • Highway Exit Signs
      • Highway Exit Info
      • Confirm Clarity of View: Interior vs Exterior
      • Confirm Clarity of View: Forward-Facing vs Side-Facing
      • Confirm Roadwork
      • Classify Roadwork
  • Use Map Data
    • Hivemapper App Developers
  • NETWORK PROTOCOL
    • Map Data Structure and Verification
    • What Is HONEY?
    • HONEY Burn and Mint
    • HONEY Token Restrictions
    • Earning HONEY
      • Reward Types
      • Global Map Progress
      • Individual Reward Factors
        • Map Tile Saturation
        • Usable Imagery
        • Clarity of View
      • Beware of Scam Airdrops
  • CAMERAS
    • Open Camera
    • HDC & HDC-S
      • Install an HDC
      • Install an HDC-S
      • Connect Dashcam to Hivemapper Companion App
      • Start Driving and Mapping - HDC/HDC-S
      • Upload Your Contributions - HDC/HDC-S
Powered by GitBook
On this page
  • Summary
  • Timeline
  • Detailed Changes
  1. welcome
  2. Network Governance

MIP-5

Map Improvement Proposal 5: Network Privacy Zones

PreviousMIP-4NextMIP-6

Last updated 2 days ago

Summary

MIP-5 proposed the creation of Network Privacy Zones (NPZs) in which the Hivemapper Network would not accept map data. Examples of NPZs include military bases and industrial facilities that are closed to the public and have rules prohibiting camera use.

Timeline

Detailed Changes

Ever since the creation of NPZs with MIP-5, a a list of NPZ polygons has been pushed to Hivemapper Network devices and apps. Within these geofenced areas, no images are submitted to the Network and no HONEY rewards are received.

MIP-5 established four criteria for a location to qualify as an NPZ:

  1. The “badge test." If you can enter a private location without passing an access test such as showing a badge, using an access code or swiping a keycard, then there is not a sufficiently strong presumption of privacy to justify an NPZ.

  2. For practical administration, only larger entities should have NPZs. It would be impractical to create NPZs for the millions of privately owned driveways, garages and parking lots in the world. The addition of user-configurable Personal Privacy Zones, or PPZs, is meant to address these areas.

  3. NPZs are not intended for the public right-of-way. NPZs exist specifically to protect the privacy of non-public locations, not to enforce any local data collection restrictions that apply to public roads.

  4. When submitting an NPZ, the burden of proof lies with the submitter. Submitters should define NPZs using objective, public data sources whenever possible.

Proposal: Published
Comment Period: Complete
Outcome: Finalized