Privacy Policy
1. Data controller
Manuel David Medina Arenas, Spanish Tax ID (NIF) 29488021C, address: C/ Palos de la Frontera, 4, 21003 Huelva, España. If you have any questions about your data, please contact us at home@dptelemetry.com.
2. What data we process
- Account: first name, surname, email address (which is also your username) and password, if you create one. We only store a one-way hash of your password, never the password itself. We also store when you accepted the terms of use, which version you accepted and how you accepted them (when creating your account or in the app when they change).
- If you sign in with Google or Apple: your Google or Apple account identifier, the email address they provide and, the first time, your name. If you choose Apple's “Hide My Email” feature, the email address is an Apple relay address and emails reach you through it. With Apple, we also store a code used solely to revoke the app's permission when you delete your account. We do not receive your Google or Apple password or any other information from those accounts.
- Profile, if you complete it: gender, height, weight and place of origin.
- Vehicles, if you add them: type, team, make, model, year, engine displacement, power, tyres, fuel and modifications.
- Photos, if you add them: your profile photo and photos of your vehicles. We store reduced-size versions on our server, with file metadata such as the location where the photo was taken removed. Only you can see them in the app. They are served through an unguessable link that is not published anywhere. When you remove them or delete your account, they are deleted from the server.
- Telemetry and sessions: vehicle position on the track, speed, laps, lap times and sector times, date and time. These are sent by the device installed in your vehicle, not by your phone. The app does not access your phone's location.
- Events: the racer's name, race number, assigned device and linking code entered by the organiser, as well as the linking of those sessions to your account.
- Purchases and vouchers: your plan and its dates, the sessions you have unlocked, your vouchers (those you purchase, receive, spend and earn, and the sessions they relate to) and transaction identifiers. When someone unlocks one of your sessions with a voucher, we do not tell them who you are beyond what they can already see in the session. Likewise, we do not tell you who unlocked it. We do not see or store your card details: payments are processed by Apple or Google.
- Session passwords: if you protect a session with a password, we store a one-way hash of it and which users have entered it successfully.
- Notifications: the identifier Firebase assigns to your phone to send notifications, whether it is an iPhone or Android device, its language and app version, and when you give or withdraw your consent to news and offers.
- App usage, only if you accept news and offers: Google Analytics for Firebase records when you open the app, its version, your phone model and operating system, and the country (inferred from your IP address), using a random installation identifier. We also provide your user segment: your plan, whether you have sessions and how recent they are, your discipline, the circuit where you race most often, whether you have made purchases and whether you organise events. We do not use advertising identifiers. If you do not accept news and offers, Analytics is disabled.
- Your devices: for each device you use to sign in to your account, whether it is an iPhone, Android device or browser, its model, operating system and app versions, its last IP address and when you last used it. We use that IP address to calculate the approximate city and country on our own server, using the DB-IP database, without sending it to anyone else.
- App crashes and errors: if the app closes unexpectedly or encounters an error, Firebase Crashlytics records what failed and where (the error and the app functions involved), your phone model and operating system, the app version, the phone's status at that moment (such as available memory and storage or screen orientation) and a random installation identifier. It does not include your name, email address or account details. If you accept news and offers, it also includes the latest information recorded by Google Analytics before the crash.
- Technical data: your IP address and the details of each request in the server logs, as well as your sign-in identifiers.
3. Why we use your data
- To provide the service (your account, sessions, events and anything you choose to share) and manage your purchases, checking with the store what you have paid for. Legal basis: performance of the contract you accept when registering (Article 6(1)(b) GDPR).
- To operate the app rankings (best laps per circuit and vouchers received), which compare racers with sessions linked to their accounts. Legal basis: our legitimate interest in providing this comparison as part of the service, with the option to opt out at any time (Article 6(1)(f) GDPR).
- To send you service notifications, if you grant permission on your phone, about your account, sessions, events or the app. Legal basis: performance of the contract (Article 6(1)(b) GDPR). You can disable them at any time in your phone settings.
- To send you DPTelemetry news and offers (events, promotions and app updates) by notification, only if you accept them when creating your account or in Settings. We decide who receives each notification based on your language and user segment (as described in section 2). Legal basis: your consent (Article 6(1)(a) GDPR and Article 21 of Spanish Law 34/2002 on information society services). You can withdraw your consent at any time using the same toggle, without affecting anything sent previously.
- To protect the service: attempt limits, fraud prevention, technical logs and your device list, so you can see where you are signed in and sign out of devices you do not recognise, and so we can limit simultaneous devices if necessary. Legal basis: our legitimate interest in keeping the service secure (Article 6(1)(f) GDPR).
- To fix app errors using crash reports (section 2), which are always sent. Without them, we would not know that the app had crashed on your phone. Legal basis: our legitimate interest in ensuring that the app works properly (Article 6(1)(f) GDPR).
- To comply with legal obligations where applicable (Article 6(1)(c) GDPR).
Apart from the news and offers described above, which you only receive if you accept them, we do not use your data for advertising, sell your data or make automated decisions that significantly affect you.
4. Who can see your data
- Other users: according to the visibility setting you choose for each session (private, Premium, reward or public). Your racer name is visible in sessions you share unless you anonymise them (section 6). During a live event, anyone allowed to access it can see the leaderboard in the app (name, race number, position and times) and each vehicle's position on the map.
- Any app user, through the rankings, if you have sessions linked to your account: your name (your profile name or, if you have not set one, the racer name entered by the organiser), your best lap on each circuit, including the date and event, and how many vouchers you have received from your reward sessions and which sessions they relate to. Your email address and photo are not shown, nor are sessions from private events or anonymised sessions. You can opt out at any time in Settings.
- The event organiser, who can see the racers, devices and sessions for their event. Once the event ends, they can display in the app and project on the event screens a simulation showing each racer's best race lap (racer name, race number and times).
- Our service providers, who process data on our behalf and solely to provide the service:
- Server hosting: Gigas Hosting, S.A. (Spain).
- RevenueCat, Inc. (United States), which manages and verifies purchases. It receives an internal account identifier, not your name or email address, as well as purchase data.
- IONOS SE (Germany), which sends emails containing codes to verify your email address and recover your password. It receives your email address.
- Google (Firebase Cloud Messaging, Firebase Crashlytics and Google Analytics for Firebase, operated by Google Ireland Limited and Google LLC), which delivers notifications to your phone (on iPhone, through Apple's notification service), receives app crash reports and, if you accept news and offers, receives app usage data and your user segment to determine who receives each campaign. It receives your phone's notification identifier and the content of each notification, but not your name or email address.
- Apple and Google, which process payments and, if you sign in with them, verify your identity as independent data controllers, under their own privacy policies.
- Google Maps, which displays maps in the app and receives technical data from your device, such as your IP address, when loading them.
- Public authorities, when we are legally required to disclose data.
5. Transfers outside the European Union
Some providers (RevenueCat, Apple and Google) may process data in the United States. This is done with the safeguards required by the GDPR: the EU–US Data Privacy Framework or standard contractual clauses approved by the European Commission.
6. How long we keep your data
- Your account and profile data are kept for as long as you have an account.
- When you delete your account, we delete your data within a maximum of 30 days. We only keep, blocked, the data that we are legally required to keep or need to handle claims, for the applicable statutory periods.
- Sessions and their telemetry do not expire or get deleted, not even when you delete your account: they form part of the service and, together with the event results, of the history of each event. When you delete your account, they are unlinked from it. You can link them to another account again using the racer code the organiser gave you.
- You can, however, anonymise your sessions in the app at any time and undo it. An anonymised session does not show who it belongs to, to other users or to you: no racer name, race number or profile name, also in the event results and simulation, and it does not count in the rankings. It remains yours, and its telemetry and times are retained. When you delete your account, we ask whether you want to anonymise all your sessions. If someone links them again using the code, they will once again display the data associated with their account.
- The notification identifier for each phone is kept until you sign out on that device or delete your account, and we only retain identifiers for your ten most recent phones. Records of when and where you give or withdraw your consent to news and offers are kept for as long as you have an account, so we can prove that you gave consent. The date on which you accepted the terms of use and the version accepted are also kept for as long as you have an account. Google Analytics data is kept for two months; when you withdraw consent or sign out, the phone deletes its data and stops sending it. Crash reports are kept for 90 days.
- Device data is kept while the device remains signed in. A session expires if you do not use it for 90 days. If you sign out on that device, its data is deleted immediately. If the session is closed from another device or because of the device limit, the data is deleted no later than 90 days afterwards, so we can explain why the session was closed.
- Technical logs are kept for the time strictly necessary to ensure the security of the service.
7. Your rights
You can ask us for access to your data, its rectification or erasure, object to its processing or ask us to restrict it, and receive it in a format you can take with you (data portability). Write to us at home@dptelemetry.com from the email address associated with your account. We will respond within one month. If you request the deletion of your sessions, we anonymise them (section 6): the remaining telemetry will no longer refer to you.
If you believe that we have not handled your data properly, you can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos, www.aepd.es).
8. Children
If you are under 14, you need the consent of your parents or legal guardians to use DPTelemetry.
9. Security
Communications between the app and our server are encrypted (HTTPS). Passwords are stored as hashes, each session can only be viewed by users who have permission, and we limit attempts to guess passwords or codes.
10. Changes to this policy
If we make material changes to this policy, we will notify you in the app.