Privacy statement

JOSM 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:

JOSM core

• 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.

• When performing HTTP(s) calls, JOSM automatically sets the ​User-Agent to include the application name, version, in-app locale (language) setting, the Operating System information (family and version) and the version of the Java runtime.

• When creating changesets, JOSM automatically adds an indication of the app name and version plus in-app locale (language) setting (created_by changeset tag), the background imagery used (currently in source changeset tag, could switch to imagery_used in a future version). This information is currently visible to anybody visiting the openstreetmap.org website or processing changeset data.

• The JOSM website, the JOSM source code repository and issue tracker are hosted on josm.openstreetmap.de (in Germany, sponsored by FOSSGIS). The developers have full access to data on use of this site, IP addresses and similar. This does not apply to the GitHub mirror which is ​likely hosted in the USA where the developers have access to no server information at all.

• At startup, JOSM downloads the message of the day from JOSM website. When doing so, JOSM sends to JOSM server the version of Java runtime and the Operating System family and version. This information is processed on a statistical and anonymous way, and is deleted after 30 days. The result of this processing is required to monitor the "market share" of major versions of Java runtime across all users to help the developers to planify the best time for Java version migrations, as Java version upgrades occur when it becomes without impact for the majority of JOSM users. 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). This behaviour can either be disabled using the help.displaymotd boolean advanced property or setting the JOSM server offline in JOSM preferences.

• Bug reports created from JOSM might contain detailed information on your device and log information from your device. You have the possibility to review this information before creating the bug report. When you submit a report, the information becomes visible to everyone. JOSM developers have the possibility to delete bug reports in case of personal information obviously published by mistake, or on user behalf. This information is required for issue identification.

• Installing the app from Microsoft store requires you to access this site and potentially submit personal data (at least IP addresses) to them.

JOSM extensions

Imagery layers

• Updating background, overlay and other layers will result in your device connecting to the JOSM website 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.

• 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.

• 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 metadata retrieval call 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 documentation for more information.

Plugins

• JOSM developers are not responsible of the majority of available plugins. The details below are not exhaustive and will never be, as plugins are continuously created by the OSM community. JOSM developers have only full or partial control on plugins hosted on the SVN repository or JOSM Github organization. JOSM developers have no control and no responsibility on plugins published outside of these locations.

• Using the cadastre-fr plugin will connect your device to services operated by ​Direction interministérielle du numérique (DINUM) and ​Direction Générale des Finances Publiques.

• Using the osmose plugin can result in your device connecting to the OSMOSE QA service operated by ​OpenStreetMap France.

• Using the OpenQA plugin can result in your device connecting to the OSMOSE QA service operated by ​OpenStreetMap France and the ​KeepRight QA service.

• Using the Mapillary plugin will connect your devices to services operated by Mapillary AB, Sweden, ​privacy policy.

• Using the StreetSide plugin will connect your devices to services operated by Microsoft Inc., USA, ​privacy policy.

• Using the MapWithAI plugin can result in your device connecting to services operated by Meta Platforms, Inc. (​privacy policy), Environmental Systems Research Institute, Inc. (​privacy policy), GitHub Inc. (​privacy policy), and other third-party services which provide data, much like the Imagery layers.

Contact

If you have questions with respect to this document, please feel free to contact us at josm-dev@… or create a new issue on this bug tracker with the privacy keyword.

Acknowledgement

This privacy policy has been largely written using ​Vespucci privacy statement.