All Locus applications work with users' personal data of some kind. Therefore, according to the EU Parliamentary and EU Council (2016/679 - GDPR) Regulations, their use is subject to the user's consent, required at the first start of each app.

• to display user's current or last fixed location on a map in user's mobile or tablet. Locus gets this information from sensors in the user's mobile device and stores it in the application only while it is running. With location data, the user knows where he/she is and what track he/she has made.
• to display user's current or last targeted position with Live Tracking - real-time location sharing. The user chooses if to share his/her location with all other Locus users and worldwide at http://www.locusmap.eu/live-tracking/ or with a selected group of people only (only on their mobile devices). The user is notified of Live Tracking being active by a rotating arrow icon on his/her screen status bar.
• to offer maps of user's immediate surroundings to him/her both in the app and in Locus Store, so that he/she doesn't have to be bothered by looking for them

• so that the user gets the benefits of My Locus - using Live Tracking, and managing user's purchases, downloads, and updates in Locus Store.
• Live Tracking - for others to better identify the user, Locus shows the user name and profile photo (or another avatar) on the map in the app and on the live tracking website. This information is displayed only when Live Tracking is active and is kept in memory only for the time the user has Locus installed on his/her mobile. If the user does not want to display his/her real name with his/her location, he/she can replace it with a nickname.
• Locus Store - Asamm needs identification data to conclude the purchase agreement. If the user has purchased paid content on Locus Store, Asamm will process his/her identification and contact information for a period of 3 years, corresponding to the duration of his/her purchase contract claims. By the so-called profiling, Asamm will estimate the user's preferences from his/her shopping history and show to him/her more relevant offers on Locus Store accordingly.
  The user signs in to My Locus profile by email and it's also possible using his/her Google or Facebook account. Email and data from the user's profile on Google or Facebook, including the user's profile photo, are stored on Asamm's server until the user withdraws his/her consent.

• based on the user's height, weight, age, sex and heart rate, Locus apps calculate body mass index and calorie consumption so that the user can monitor his/her performance in sporting activities. Depending on this, the user can set up his/her workouts correctly and efficiently.
• Fitness data are kept in the Locus folder on the user's mobile or tablet until he/she deletes the folder.

The personal data subject to the user's consent is deposited for the entire duration of the user's consent until its possible revocation, without prejudice to the lawfulness of processing based on consent prior to its withdrawal. The Personal Information Manager is Asamm Software, s.r.o., company ID: 24225321, with its registered office at Krhanická 719/25, Kamýk, 142 00 Prague 4, Czech Republic.

Locus Map is growing. Over the years of development, it contains more and more features that require permission from the Android Operation System. The same it is with apps related to it or built upon its base - Locus GIS, Map4Trip and KiMaps. The main reason for it is, of course, your protection as the user.

A complete list of all the permissions and their explanation:

• android.permission.ACCESS_COARSE_LOCATION
  • allows access to Wi-Fi, network location

• android.permission.ACCESS_FINE_LOCATION
  • allows to acquire GPS location

• android.permission.ACCESS_LOCATION_EXTRA_COMMANDS
  • allows disabling the A-GPS data status and forcing system to load new

• android.permission.ACCESS_MOCK_LOCATION
  • allows creating and receiving simulated locations

• android.permission.ACCESS_NETWORK_STATE
  • allows testing if internet connection is available

• android.permission.ACCESS_WIFI_STATE
  • allows to check Wi-Fi network state (connected/disconnected)

• android.permission.BIND_DEVICE_ADMIN
• allows to control screen on/off depending on various events like near-point alerts, direction changes during navigation, etc.
• enables to control your screen with hardware buttons of your device or with external controllers (e.g. Bluetooth)

• android.permission.BLUETOOTH
  • allows to work with (connect to) a Bluetooth device

• android.permission.BLUETOOTH_ADMIN
  • allows to search for and pair Bluetooth devices

• android.permission.GET_ACCOUNTS
  • allows reading the list of available Google accounts (for the possibility to enter Locus Store or launch Live tracking). Unfortunately, this permission is a part of a group Contacts which triggers a warning about the possibility of the app reading user's contacts - none of it is allowed!

• android.permission.MANAGE_ACCOUNTS
• allows restoring expired access to a logged in account. Each account has its validity time and when this expires a request for re-login has to be made.

• android.permission.USE_CREDENTIALS
  • allows to request auth_tokens from the AccountManager. This means that Locus Map may request you to login to your account without writing any username/password information into the app.

• android.permission.INTERNET
  • allows downloading map tiles, address search and more tools

• android.permission.KILL_BACKGROUND_PROCESSES
  • allows to restart the app and also kill it after exit. Thanks to this Locus Map (and related apps) is removed from the system memory when closed

• android.permission.RECEIVE_BOOT_COMPLETED
  • required for automatic backup feature

• android.permission.VIBRATE
  • allows to control the device's vibrator for notifications

• android.permission.WAKE_LOCK
  • allows to keep Locus Map (and related apps) awake if required by user for some demanding tasks like track recording etc.

• android.permission.WRITE_EXTERNAL_STORAGE - limited in Android 4.4.2 and later
  • allows handling the external storage card - for reading external maps, storing vector maps, backup and SRTM data
  • allows also accessing your photos and videos so that they are available as attachments to points

• android.permission.RECORD_AUDIO
  • allows access to microphone for the recording of audio as an attachment to points

• com.android.vending.CHECK_LICENSE
  • used to verify your purchased license

• com.android.vending.BILLING
  • allows to provide in-app billing

• com.google.android.providers.gsf.permission.READ_GSERVICES
  • allows access to Google services (for Locus Store, Google Analytics, planned Cloud to device messaging, etc.)

• com.dsi.ant.permission.ANT
• com.dsi.ant.permission.ANT_ADMIN
  • allows to connect and manage the connection to ANT+ sensors

• android.permission.CAMERA - this add-on enables displaying selected points according to their GPS coordinates on the background recorded by the camera. No image data are recorded nor shared. See more >>

• android.permission.READ_CONTACTS - this add-on enables viewing your contacts' addresses on the map. No contacts data are stored or shared. See more >>

Is this article useful for you? Please rate it: {(rater>id=1|name=faq_permissions|type=rate|headline=off)}