From 37c98919d6c1f19992c594a171c1af8c2df5850a Mon Sep 17 00:00:00 2001 From: ralf401 Date: Tue, 28 May 2024 14:29:42 +0200 Subject: [PATCH] Fixes #481 - Changed Geolocation paragraph --- appendix/privacy.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/appendix/privacy.rst b/appendix/privacy.rst index 02a86ce1..99d9a40f 100644 --- a/appendix/privacy.rst +++ b/appendix/privacy.rst @@ -91,17 +91,17 @@ GeoCalendar GeoIP No user information is stored or cached on geo.zammad.com. - One of Zammad’s security features is to track user sessions - based on the user’s browser and country of origin. + One of Zammad's security features is to track user sessions + based on the user's browser and country of origin. Suspicious login activity from a different browser or country may trigger Zammad to dispatch an alert email to the affected user. The GeoIP service is used to associate IP addresses to a geographic origin. Geolocation - Since Zammad’s geolocation service relies on Google’s - `Geocoding API `_, - its use is subject to the `Google Privacy Policy `_. + Zammad's geolocation service relies on OpenStreetMap (OSM) unless you turned + it off. If you provide an address (or parts of an address) in a user + object, there is a lookup of coordinates from OSM which are stored in + Zammad's database. Have a look at their + `privacy policy `_ for + more information. - Zammad uses geolocation to associate tickets with locations - to support map-style ticket overviews, - which display tickets as points on a map rather than items in a list.