Privacy statement#

Vespucci is a collaboratively developed app for editing OpenStreetMap data via its editing API. The developers do not collect, store or otherwise process any personal data related to your usage of the app, you should however be aware of the following:

  • Using the OpenStreetMap Foundations infrastructure and contributing to OpenStreetMap is subject to the OSMFs privacy policy and Terms of Use, you should have studied these when you created your OpenStreetMap account and should be aware of the privacy consequences.
  • Vespucci automatically adds an indication of the app name and version ( created_by changeset tag), the background imagery used ( imagery_used changeset tag) and the locale (language) setting of your device ( locale changeset tag). This information is currently visible to anybody visiting the website or processing changeset data.
  • The site and the Vespucci source code repository and issue tracker is hosted on github (likely in the USA) the developers have no access to any data on use of the site, IP addresses or similar.
  • Using the Provide feedback functionality without a github account will create an issue that contains information on your device (you can review that prior to submitting the data) and, if available, your OpenStreetMap display name so that we can contact you with any questions. You can have the information removed by sending mail to the e-mail address below. Processing of this data is based on a legitimate interest of the developers see GDPR Art 6.(1) f).
  • Crash dumps contain IP addresses, detailed information on your device and log information from your device immediately before the crash. This information is stored on a server operated by Simon Poole and located in Germany, when you submit a report. The information is deleted after 90 days if it is not required further for issue identification and resolution, general web server logfiles are retained for 15 days. None of this data is shared with 3rd parties. Processing of this data is based on a legitimate interest of the developers see GDPR Art 6.(1) f).
  • Updating background, overlay and other layers will result in your device connecting to the JOSM project or Editor Layer Index github repo and using the layers will connect you to the sites of the respective operators. More information on the provenance of such layers can be found via the per layer information displays, or from the respective source repositories.
  • Using the Tasks layer can result in your device connecting to the OSMOSE QA service operated by OpenStreetMap France.
  • Accessing the OpenAerialMap catalogue and retrieving imagery from the service will transmit your IP address and other information to its operator, which might be governed by this privacy policy.
  • Using the Mapillary layer will connect your devices to services operated by Mapillary AB, Sweden, privacy policy.
  • Installing the app from Amazon, google or F-Droid requires you to access these sites and potentially submit personal data (at least IP addresses) to them.
  • Recording a GPX track, or starting location based auto-download, will lead to a service continuously updating your current position, including when you navigate away from the app for example by starting a different application. If GPX recording is enabled the location information will be stored on your device until you explicitly clear it or de-install the app. Such location access will stop if you either turn recording or auto-download off, or exit the app. No location information is made available to the Vespucci developers or other third parties. It is at your sole discretion how to use the recorded location data, for example if you upload it to OpenStreetMap or if you use it simply for private documentation. A notification is persistently displayed as long as the service is actively using location data.
  • Background and overlay layers are generally operated by third parties over which we have no control. Links to their privacy policies are provided if available. A one time metadata retrieval call per session is required for use of the Bing orthoimagery layer, this happens in an asynchronous fashion when imagery is being configured regardless if you are using the Bing layer or not. You can disable this behaviour by removing the Bing key from the configuration, see the FAQs for more information.

If you have questions with respect to this document, please feel free to contact us at