MIP-5
Map Improvement Proposal 5: Network Privacy Zones
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:
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.
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.
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.
When submitting an NPZ, the burden of proof lies with the submitter. Submitters should define NPZs using objective, public data sources whenever possible.
Last updated