We think you are in United States. Do you want to visit the local website?

Select your location

Asia/Pacific

Australia

Australia

English
China

China

中文
India

India

English
Japan

Japan

日本語
Middle East

Middle East

English
Singapore

Singapore

English
Thailand

Thailand

ไทย
Turkey

Turkey

Türkçe

Europe

Czech Republic

Czech Republic

Čeština
Denmark

Denmark

Dansk
Finland

Finland

Suomi Svenska
France

France

Français
Germany

Germany

Deutsch
Italy

Italy

Italiano
Norway

Norway

Norsk
Poland

Poland

Polski
Sweden

Sweden

Svenska
Spain

Spain

Español
United Kingdom

United Kingdom

English

North America

Mexico

Mexico

Español
United States

United States

English

South America

Brazil

Brazil

Português

Global

Global Site

Global Site

English

myMirka® Mobile Application Privacy Policy

Personal and Sensitive Information


The myMirka application does not collect or store personal or sensitive information locally. Such information is stored in a remote secure server.

Runtime Application Permissions


In order to manage Mirka BLE tools, myMirka uses Bluetooth related permissions and Internet access. No other permissions are required.

Android


For scanning nearby BLE devices, the ACCESS_COARSE_LOCATION permission is needed for devices running up to Android 11.On Android 12, this permission is not requested nor required. The GPS location of the device is not collected or used.

For managing the availability of Bluetooth on the phone (BLUETOOTH, BLUETOOTH_ADMIN), and connect to the tool (BLUETOOTH_CONNECT) are required.

For retrieving the user's registered tools and for up-to-date tool information - e.g., images,latest firmware - INTERNET permission is required. All communication between the application and the backend occurs over cryptographically secure connections (HTTPS) and are authenticated.

iOS


For scanning and connecting with Mirka tools, the application uses the "Uses Bluetooth LE accessories".

For retrieving the user's registered tools and for up-to-date tool information - e.g., tool images, latest firmware - "Background fetch" is required. All communication between the application and the backend occurs over cryptographically secure connections (HTTPS) and are authenticated.

For marketing purposes,"Remote notifications" are used.

Data Usage and Statistics


For debugging purposes, Firebase Crashlytics is used to identify crashes. Firebase Real-time Database is used to monitor the reliability of the tools' vibration exposure sampling rate when connected to a tool. Google's Firebase Analytics will be used to monitor the application distribution (which version is currently in use) and installation demographics. On iOS, App Analytics will be used for the same purpose.

GDPR compliance


Read about Mirka’s general privacy policy: https://www.mirka.com/top/privacy-policy/

Mirka Ltd is the responsible data controller for the processing of your data for the purposes described above. If you have any questions about how we process your personal data or if you wish to exercise your rights, please feel free to contact us any time by e-mail or mail at

Mirka Ltd.
Pensalavägen 210
FI-66850 Jeppo
Finland

privacy@mirka.com

The user can delete their data from the app's settings menu.