Privacy Policy

A. DEFINITIONS

1. muv-N® is the name of the mobile devices apps, of the website at http://muv-n.com and of the various services under the same brand name. muv-N® is a registered brand and it’s the propriety of the Producer.

2. muv-N® ARTIFACTS are the following three artifacts, simultaneously:

i. the muv-N® mobile devices apps;

ii. the website at http://muv-n.com;

iii. the services under the muv-N® brand name.

2. The PRODUCER, represented by Hildegardo José Quintal Noronha, with the headquarters on Startup Madeira – CW 021, Campus da Penteada, 9020-105 Funchal – Madeira – Portugal, is who:

i. develops and maintains the muv-N® mobile devices apps;

ii. develops and maintains the website at http://muv-n.com;

iii. provides the services under the muv-N® brand name.

3. The USER is the person that uses one or more of the muv-N® Artifacts provided by the producer.

4. The User can also be an ATHLETE or a SPECTATOR. The respective definitions are on the relevant sections.

B. GENERAL

1. The Producer is concerned about your privacy and only gathers the data that is deemed necessary for the proper operation of the muv-N® Artifacts and of any of the required third-party services. Keep reading to find out what data is gathered.

2. Concerning the gathered data that are responsibility of the Producer:

i. The personal data is protected by the industry standards.

ii. All the gathered data is stored while necessary and relevant.

3. The gathered data that is responsibility of third-parties, namely Google, are of the sole responsibility of said entities and never of the Producer.

4. Any third-party, namely Google, could have non-disclosed partners that have their own Privacy Policy.

5. The User already agreed to those Privacy Policy at the moment the User started using the Google services (such as, but not limited to, Gmail, the Android devices).

6. The gathered and shared information may change, unilaterally, in the future and. If the User stops agreeing with the new gathered and shared information, the User should uninstall/delete all copies of the muv-N® Artifacts that the User owns, cancel all subscriptions to muv-N® services and stop using all using all muv-N® services.

C. SERVICE DESCRIPTION

1. muv-N® is a service provided through a set of artifacts, previously described as “muv-N® Artifacts”.

2. muv-N® has two type of Users: the SPECTATOR and the ATHLETE.

3. The service’s objective is to give support to the Athletes and to improve the show for the Spectators through the tracking and sharing, publicly or semi-publicly, and in real time, of the geolocation data of the Athletes, as well as through other gathered or derived data from the GPS receptor (or other similar geolocation services).

4. The Athlete User shares the data described on this document and the Spectator User views it.

5. The service enables the Athlete to train and consult the performance of previous training and races. This data is private unless, directly and explicitly shared by the Athlete.

6. The service enables the Athlete to place Help Request to the Event Organization, in an organized race, and to another User, in trainings. These Help Requests trigger the automatic gathering of data as well as the data directly inputted by the User.

D. USING THE SERVICE AS AN ATHLETE

1. The Athlete is the User that activates the tracking services in the muv-N® app.

2. Once the Athlete starts the tracking services, the muv-N® app will start trying to gather and share the relevant data.

3. In the context of a Race, the shared data is public and directly accessible by any person that accesses the services. In the context of a Training, the data is shared to whom the Athlete chooses.

4. If the User does not want that data to be shared, the User should not use the muv-N® app as an Athlete. The User can still use the muv-N® app as a Spectator.

5. If the User starts the tracking services during a Race and, then, decides to stop the tracking services, all the previously shared data will remain public.

6. If the User does not agree with the previous point, the User should not use the muv-N® app as an Athlete.

7. The previously shared data will remain public, even if the User stops the tracking service. This happens for security reasons. In the eventuality that an Athlete has an accident and the User’s mobile device is damaged, the system will keep showing the Athlete’s last known location helping the Athlete’s rescue.

8. Once the Athlete stops the tracking service, be it intentionally or not, no new data will be shared. Yet, the previously shared data will remain public.

9. To start the tracking services, the Athlete must get authenticated in the muv-N® system. For this purpose, the Event Organization should have placed the Athlete’s bib and/or has given the Athlete a piece of paper with this information (the Athlete’s number and code).

10. The authentication information should be kept secret by the Athlete.

11. The authentication information goes through the Event Organization so, some people, can have seen it.

12. The authentication information, after being inputted on the muv-N® app by the Athlete are transmitted to the server in order to authenticate the Athlete. This transmission uses the User’s device’s Internet and can be intercepted and even changed by third-parties, especially if the Athlete uses unsecure connections.

13. To start the tracking service, the Athlete must, successfully, navigate through the screens in the Athlete area and manage to get correctly authenticated.

14. To stop the tracking service, the Athlete can do one of the following:

i. Press the “back” button on the device inside the muv-N® app and accept the stopping of the tracking in the shown message.

ii. Touch the “Stop” button on the message in the device’s system tray and then confirm, inside the muv-N® app, the intention to stop the tracking.

iii. Any forced quit of the muv-N® app by the User, by the system, by the low battery level, by the lack of memory or by the shutdown of the device will stop the tracking service.

iv. Uninstall the muv-N® app.

E. USING THE SERVICE AS A SPECTATOR

1. The use of the muv-N® app as a Spectator, unlike the use as an Athlete, does not require the sharing of any of the data described on the Athlete section.

2. Still, the muv-N® app gathers and transmits some data that is common to both the kind of Users and this is described in the relevant section.

F. GATHERED AND TRANSMITED DATA THAT IS COMMON TO BOTH TYPES OF USER (ATHLETE AND SPECTATOR)

1. Since the muv-N® app communicates with the server, the data related with the transmission of data through the Internet is, temporarily, stored while necessary to complete the requests made by the muv-N® app.

2. The muv-N® app uses the crash report and analytics service Google Firebase.

3. The Google Firebase automatically gathers data and events from the User’s device as well as some personal data.

4. Please consult the documents at https://support.google.com/firebase/answer/6317485 and at https://support.google.com/firebase/answer/6317486 to find out what data the service may gather.

5. The data gathered by the Google Firebase are only used by the Producer for two purposes:

i. The gathered data when a crash happens helps us to identify and fix faults in the muv-N® app. Some non-identifiable data may also be gathered in order to optimize the app (namely the battery usage by the app).

ii. The ad service used by the muv-N® app also gatherers data.

6. The muv-N® app uses the Google AdMob ad service.

7. The Google AdMov service uses the Google Firebase service to gather data in order to display relevant and targeted data to the User.

8. The muv-N® app does not display ads to the Athletes while the tracking service is active – but it may display ads in other areas, such as when reviewing previous races and training. This assures the Athlete that the muv-N® app will only use the strictly necessary battery and data plafond while tracking and that the Athlete will not be distracted by services that are irrelevant at that very moment.

G. HELP REQUESTS

1. When a Help Request is placed, some data is gathered. The data is gathered:

i. Automatically;

ii. Through the direct and intentional introduction by the User;

iii. From data that was previously introduced by the User in the system.

2. The data that is automatically gathered is:

i. The geolocation of the Athlete’s device (latitude, longitude, height and the location precision);

ii. The remaining battery percentage of the Athlete’s device.

3. The manually and intentional introduced data by the Athlete during the request is not exposed in this document.

4. The data that is gathered from the system is:

i. The race where the request occurred;

ii. The requiring Athlete’s number;

iii. The requiring Athlete’s name (if the User is authenticated in the system at the moment the request was placed AND if this information is in the system).

5. The following data is public:

i. The geolocation of the Athlete’s device (latitude, longitude, height and the location precision).

6. The following data is available to those that have the request’s “authentication token”:

i. All the public data;

ii. All the data that was introduced by the Athlete with the exception of the self’s contact and the third-party’s contact;

iii. All the data that is gathered from the system.

6. The following data is available only to the Event Organization:

i. All the public data;

i. All the data that is available only to those that have the request’s “authentication token”;

i. The Athlete’s contact and the third-party’s contact.

7. All the data is displayed hierarchically to keep a balance between privacy and the possibility of the rescue. For achieve this, the Producer follows the following guidelines:

i. An entity that is rescuing the Athlete may not have access, at that moment, to the request’s “authentication token” or the help may come from unofficial third-parties. Since that, in some situations, the response time is vital, the general public can see the Help Request’s geolocation with the remaining information being withheld.

ii. Those that have the “authentication token” are, officially, authenticated in the system. Given the way of how the “authentication token” is transmitted, it is reasonable to assume that only the Event Organization and, possibly, a rescue entity, will have the “authentication token”. Therefore, more data is available to those users, including personal data that the Producer considers important to the providing of help.

iii. The remaining data (the Athlete’s contact and a third-party contact that the user choses) are available, only, to the Event Organization. It is up to the Event Organization to decide if the rescue party should or not have those contacts.

8. The data is transmitted to the Event Organization, when possible, and with the respective consequences to the User’s privacy:

i. One or more emails with the information that a Help Request has been STARTED, CONFIRMED or CANCELED. All the sent emails have a link, with the “authentication token” embedded, to a website that enables the visualization of most of the information, updated in real-time. The CONFIRMATION and CANCELATION are sent with ALL of the data that was gathered up to the point.

ii. One or more SMSs with the information that a Help Request has been STARTED, CONFIRMED or CANCELED. All the sent SMSs have a link, with the “authentication token” embedded, to a website that enables the visualization of most of the information, updated in real-time. The CONFIRMATION and CANCELATION are sent with some of the data that was gathered up to the point, taking into consideration the limited number of characters.

iii. One or more notifications to any User’s muv-N® app that is authenticated as being from the Event’s Organization.

iv. The availability of some information on the website’s page at http://sos.muv-n.com, with public access but with some data restricted with an “authentication token” that is generated in a unique, random and automatic way for each request. This “authentication token” is only made available to the Event Organization in the ways described in this document.