MTN MOVE
1. APPLICATION OVERVIEW
a. MTN MOVE is a non – business focused application that has been made available to employees of MTN and its group companies. The application is envisaged to support various facets of wellbeing including physical wellbeing, social wellbeing, mental and emotional wellbeing and nutritional wellbeing through multiple functionalities across microapps focused on each of these areas.
b. The app provides users with custom features that support and promote wellbeing including access to latest verified information on wellbeing, tools that help provide a view of their steps and distance covered, ability to create posts, recipes and participate in conversations about wellbeing.
2. GET FIT- MICROAPP OVERVIEW (Only Microapp / section of the app requesting access to Google Fit APIs)
a. The Get Fit microapp connects with the phone in-built API (Google Fit) to enable syncing of fitness information - Steps and Distance (only this data is collected) covered by the user. The sync can be enabled and disabled via controls provided to the users
b. Users can also set challenges and invite specific employees to participate in challenges with them. Administrators will also be able to set-up challenges for employees
c. The app also allows employees to view their standing on a Global leaderboard that is periodically refreshed
3. DATA ENTRY MODES
Users can provide their fitness data to the application in any one of the 3 ways mentioned below
a. Enabling automatic sync using the Google fit APIs with the user’s consent. This allows the application to sync with Google fit and request for the information to be updated in Get Fit. The sync will run every time the application is opened (provided it is enabled and consent is provided) and attempt to sync data. The permission for auto sync can be withdrawn by the user at will by using a toggle control provided in the sync fitness data page
b. Manual sync of the data from the Google Fit APIs with the user’s consent. This sync will run every time the user presses on the sync now button on the Sync fitness data page. Once this button is pressed, the app will attempt the sync and overwrite any data present in the application if the revised data available via sync is greater than the existing information
c. Manual entry of data by the user using the Add fitness data functionality. In this page the user will be asked to enter the number of steps they have covered, and the app will convert the same into kms and miles using a backend logic.
4. USE CASES for the DATA COLLECTED
a. Users can view the history of the data present in the app and view graphs that show a representation of this data by Days, Weeks and Months. Users can also view these graphs as a summation of distance in Kms. / Miles
b. Users can create challenges where they can invite specific employees to participate in the challenge. Once accepted by the employees, they will be shown a leaderboard for the duration of the challenge which will utilise information on steps and distance available in the app to determine relative positioning of the user and declare a winner
c. Users can participate in challenges created by administrators in the backend which will also showcase a similar leaderboard as in case of user generated challenges
d. Users are also shown an overall global leaderboard that shows their relative standing at an organisational level consuming the steps and distance data that is available in the app to determine relative positioning of the user and declare a winner at the end of each month. The leaderboard is then reset to start from 0 from the next month
5. NO WRITE-BACK to GOOGLE FIT
a. The MTN MOVE application will not write back to Google Fit in any of the cases of data upload
b. Any inputs by user in the application through manual entry will not be written back to Google Fit
https://mtnmove.dronahq.com/files/docs/MTN_Google_App_Privacy.html