Create a global privacy setting for OSM #5746

Closed
opened 2023-08-18 13:58:17 +00:00 by privatemaker · 0 comments
privatemaker commented 2023-08-18 13:58:17 +00:00 (Migrated from github.com)

A privacy-focused application empowering users to "reject surveillance" while simultaneously making it user-friendly to directly contribute to a public open-data repository like Open Street Maps MUST have a clearly stated privacy policy which is tightly integrated into the user-experience.

Describe the issue

Consider the following users types with different privacy / threat models:

Post-Privacy Contributor
Loves open-data, logs into OSM with an account under their legal name (or is easy to discover via homepage / social profiles). This user has no concerns about contributing all sorts of data- their local neighborhood, work, holidays, etc.

Privacy Conscious Contributor
Logs into OSM with an account that is a pseudonym. This user feels this is a sufficient level of privacy to contribute data safely.

  • Pseudonyms often lose privacy if they are used long enough
  • Can require secondary email accounts, etc...

Hybrid Contributor
Logs into OSM with an account they feel comfortable publishing Place information. They sometimes contribute data freely. Other times it could be very for them if their Place data was published. Some examples:

  • Small business owner using OMaps with a list of clients they deliver to (likely a mix of public businesses and private homes)
  • An LGBTQ person who lives somewhere where their lifestyle is illegal or persecuted by non-state actors
  • A politician, judge, law enforcement, or military person with unusual threats
  • Someone who has ever had a stalker trying to constantly track them down

Private Non-Contributor
Would never log into OSM and would never want any data being sent to public repository like OSM. This is often because they understand how once data is out there, it's out there + how badly privacy is usually handled in apps.

Each of these user types SHOULD feel comfortable using Organic Maps and it should offer the flexibility to selectively publish data.

Proposed Solution

After a user successfully signs up / logs into OpenStreetMaps as per flow in #5785 they should be presented with an Organic Maps privacy setting to select.

There should be a dropdown menu to save this global setting:

Please select your privacy settings for OpenStreetMaps contributions.

> Select Privacy Level

1 Manual
2 Confirm (default)
3 Automatic

Each option would yield the following:

Opt. Setting Privacy
1 manual Requires user to manually upload Places via a button
2 confirm Ask user with each Place edit
3 auto Automatically save all Place contributions to OSM

A user who selects Opt. 1 would not be bothered every time they update a Place.
A user who selects Opt. 2 would benefit from this easy confirmation each time

Implications of this are being discussed in #5727 with the idea of Contribute Place to OSM toggle in the Place editor, and in #1325 the batch submit proposal.

This somewhat relates to "anonymous" or a pseudonymous privacy-proxy type OSM user as discussed in #5740 but that does not sound feasible, for now.

A privacy-focused application empowering users to "reject surveillance" while simultaneously making it user-friendly to directly contribute to a public open-data repository like [Open Street Maps](https://www.openstreetmap.org) MUST have a clearly stated privacy policy which is tightly integrated into the user-experience. **Describe the issue** Consider the following users types with different privacy / threat models: **Post-Privacy Contributor** Loves open-data, logs into OSM with an account under their legal name (or is easy to discover via homepage / social profiles). This user has no concerns about contributing all sorts of data- their local neighborhood, work, holidays, etc. **Privacy Conscious Contributor** Logs into OSM with an account that is a pseudonym. This user feels this is a sufficient level of privacy to contribute data safely. - Pseudonyms often lose privacy if they are used long enough - Can require secondary email accounts, etc... **Hybrid Contributor** Logs into OSM with an account they feel comfortable publishing Place information. They sometimes contribute data freely. Other times it could be very for them if their Place data was published. Some examples: - Small business owner using OMaps with a list of clients they deliver to (likely a mix of public businesses and private homes) - An LGBTQ person who lives somewhere where their lifestyle is illegal or persecuted by non-state actors - A politician, judge, law enforcement, or military person with unusual threats - Someone who has ever had a stalker trying to constantly track them down **Private Non-Contributor** Would never log into OSM and would never want any data being sent to public repository like OSM. This is often because they understand how once data is out there, it's out there + how badly privacy is usually handled in apps. Each of these user types SHOULD feel comfortable using Organic Maps and it should offer the flexibility to selectively publish data. ### Proposed Solution After a user successfully signs up / logs into OpenStreetMaps as per flow in #5785 they should be presented with an Organic Maps privacy setting to select. There should be a dropdown menu to save this global setting: ``` Please select your privacy settings for OpenStreetMaps contributions. > Select Privacy Level 1 Manual 2 Confirm (default) 3 Automatic ``` Each option would yield the following: | Opt. | Setting | Privacy | |-------|-----------|------------------| | 1 | `manual` | Requires user to manually upload Places via a button | | 2 | `confirm` | Ask user with each Place edit | | 3 | `auto` | Automatically save all Place contributions to OSM | A user who selects `Opt. 1` would not be bothered every time they update a Place. A user who selects `Opt. 2` would benefit from this easy confirmation each time Implications of this are being discussed in #5727 with the idea of `Contribute Place to OSM` toggle in the Place editor, and in #1325 the `batch submit` proposal. This somewhat relates to "anonymous" or a pseudonymous privacy-proxy type OSM user as discussed in #5740 but that does not sound feasible, for now.
This repo is archived. You cannot comment on issues.
No labels
Accessibility
Accessibility
Address
Address
Android
Android
Android Auto
Android Auto
Android Automotive (AAOS)
Android Automotive (AAOS)
API
API
AppGallery
AppGallery
AppStore
AppStore
Battery and Performance
Battery and Performance
Blocker
Blocker
Bookmarks and Tracks
Bookmarks and Tracks
Borders
Borders
Bug
Bug
Build
Build
CarPlay
CarPlay
Classificator
Classificator
Community
Community
Core
Core
CrashReports
CrashReports
Cycling
Cycling
Desktop
Desktop
DevEx
DevEx
DevOps
DevOps
dev_sandbox
dev_sandbox
Directions
Directions
Documentation
Documentation
Downloader
Downloader
Drape
Drape
Driving
Driving
Duplicate
Duplicate
Editor
Editor
Elevation
Elevation
Enhancement
Enhancement
Epic
Epic
External Map Datasets
External Map Datasets
F-Droid
F-Droid
Fonts
Fonts
Frequently User Reported
Frequently User Reported
Fund
Fund
Generator
Generator
Good first issue
Good first issue
Google Play
Google Play
GPS
GPS
GSoC
GSoC
iCloud
iCloud
Icons
Icons
iOS
iOS
Legal
Legal
Linux Desktop
Linux Desktop
Linux packaging
Linux packaging
Linux Phone
Linux Phone
Mac OS
Mac OS
Map Data
Map Data
Metro
Metro
Navigation
Navigation
Need Feedback
Need Feedback
Night Mode
Night Mode
NLnet 2024-06-281
NLnet 2024-06-281
No Feature Parity
No Feature Parity
Opening Hours
Opening Hours
Outdoors
Outdoors
POI Info
POI Info
Privacy
Privacy
Public Transport
Public Transport
Raw Idea
Raw Idea
Refactoring
Refactoring
Regional
Regional
Regression
Regression
Releases
Releases
RoboTest
RoboTest
Route Planning
Route Planning
Routing
Routing
Ruler
Ruler
Search
Search
Security
Security
Styles
Styles
Tests
Tests
Track Recording
Track Recording
Translations
Translations
TTS
TTS
UI
UI
UX
UX
Walk Navigation
Walk Navigation
Watches
Watches
Web
Web
Wikipedia
Wikipedia
Windows
Windows
Won't fix
Won't fix
World Map
World Map
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps-tmp#5746
No description provided.