This English version is a translation provided for convenience. Only the French version is legally binding; in the event of any discrepancy, the French version prevails.
Privacy policy
Last updated: October 14, 2026 — version 1.0
Smartiming is a race timing service, developed and published by Wildpace: a website (smartiming.net), a web application (app.smartiming.net) and a mobile application for iPhone and Android, called “Smartiming”. This page explains which personal data we process, why, for how long, who we share them with, and how to exercise your rights.
1. Who is responsible for what
Publisher of the service: Wildpace, sole proprietorship (French micro-entrepreneur) — SIRET 833338247 00020. Contact for any question about your data: contact@wildpace.net. We have not appointed a data protection officer.
Two situations must be distinguished:
- We are the controller of the data of the users of the service (the organizers and the members of their team who have an account), of credit purchases, security logs and error reports, of the visitors of our website and of the people who write to us.
- We are the organizer's processor for the data of race participants (runners, emergency contacts) and for the results. The organizer of the race decides to collect these data and what to do with them: they are the controller of this processing. We only use these data to operate the service for them, according to their instructions, under the Terms of use, whose section 8 details our role as a processor (clauses of article 28 of the GDPR).
Are you a race participant? Contact the organizer first (their name appears on the results page and on the event documents) for any request about your data: they can correct, hide or delete them. We help them do so, and you can also write to us (section 10).
Are you only viewing results (“participant” mode of the application, or a QR code link)? You have no account and we ask you for no information. Only technical connection data are recorded (section 2, “Technical data” row).
2. The data we process
| Category | Data subjects | Data | Where they come from |
|---|---|---|---|
| User account | Organizers and members of their team | Last name, first name, email address, password (stored only in encrypted, non-reversible form, never in clear text), name of the organization, role, date of last sign-in, email verification status | You, at sign-up, or when an administrator of your organization creates the account |
| Participants | Runners registered for a race | Last name, first name, sex (M/F), date of birth or age category, club, bib number, status in the race; optional: phone, email, “requires anonymity” checkbox | The organizer (manual entry, or import of an Excel file) |
| Emergency contacts | Participants' emergency contacts | Name and phone number | The organizer — it is up to them to inform these people |
| Results | Participants | Split and finish times, race times, rankings | Entered by the timekeepers during the race |
| Audit log | Members of an organization, and participants named in an action | Who did what and when: name and email of the author, role, type of device (phone or computer), subject of the action (for example “bib 1234 — DUPONT Marie”); for a failed sign-in: the email address entered | Generated by the use of the service |
| Credit purchases | Members who buy credits | Amount, number of credits, date, transaction identifiers at Stripe. We neither see nor store your card number: payment takes place on Stripe's page | You, and Stripe |
| Service emails | Users | Your address and the content of the message (email address confirmation link, password reset link) | Generated by the service |
| Technical data | Everyone, including visitors without an account | IP address, date and time, requested address, operating system and application version, type of browser or device | Sent automatically with each connection |
| Mobile application crash reports | Users of the application | Nature of the error, application version, device model and operating system, an identifier specific to the installation, state of the application at the time of the error (see section 9) | The application, only if it crashes |
| Messages you send us | Anyone who writes to us | Your address, your message | You |
What we do not collect: no health data, no photos, no identity documents, no geolocation, no access to your contacts, your camera or your photo library. The application contains no advertising and no advertising tracking or audience analytics tool.
The microphone. The application only asks for access to the microphone for dictating bib numbers, when the timekeeper starts the dictation themselves. Speech recognition runs entirely on the device: the sound is neither recorded, nor sent, nor stored. The recognition model is downloaded once from our servers with your consent; only this download goes through the network.
Minors. Participants may be minors: the organizer obtains the necessary authorizations from their legal guardians. The service accounts (organizers and teams) are reserved for adults (see the Terms of use, section 4).
3. Why we process them, and on what legal basis
| Purpose | Legal basis (GDPR, art. 6) |
|---|---|
| Create and manage your account, operate the service (timing, results, exports) | Performance of a contract (b) |
| Send you service emails (confirm an address, reset a password) | Performance of a contract (b) |
| Sell and add credits, keep our accounts | Performance of a contract (b) and legal obligation (c) |
| Secure the service: limit repeated sign-in attempts, detect abuse, technical logs | Legitimate interest (f): protecting the service and its users |
| Keep the audit log of each organization (traceability of its team's actions) | Legitimate interest (f): allowing the organizer to account for what was entered and changed |
| Detect and fix application crashes | Legitimate interest (f): reliability of the service, especially on race day |
| Answer your requests | Legitimate interest (f), or performance of a contract |
| Participant data and results | The organizer determines the legal basis (for example performance of the registration contract, or their legitimate interest). We act on their behalf |
We do not sell your data, we do not use them for advertising purposes, and we carry out no profiling or automated decision-making about you. We send no newsletter and no marketing messages.
4. Public results
The organizer of a race can activate public links: results of the event or of a race, large-format display screen, “latest splits”. As long as a link is active, anyone who has it can see, without an account: the last name, first name, club, bib number, category, ranking and time of the participants concerned. These links are shared by QR code, by message or on the organizer's website.
- Directory in the application. When an organizer activates the publication of the results of a race, this event, with the name of the organization, appears in the list of the application's “participant” mode, visible to all its users. There is no separate setting to appear only through a direct link.
- Anonymity. The organizer can tick “requires anonymity” for a participant: on the public pages, their bib number, last name, first name and club are replaced (“XXX”, “Coureur Anonymisé”, i.e. anonymized runner), and they do not appear in the public search. Their rank, time and category remain displayed, so that the ranking stays consistent. The organization itself always sees the real identity. A participant who wants this anonymity asks the organizer for it.
- Test events. Events created in test mode hide the identity of all participants on all results pages.
- Search engines. These pages are not meant to be indexed: our server asks search engines not to index them or keep a copy of them. This request has no effect on a page already copied elsewhere, nor on a person who has the link.
- End of publication. The organizer can deactivate a link at any time: the page is then no longer accessible. We cannot erase a copy that someone may already have saved on their side.
5. Who we share the data with
We use service providers (processors) that only process the data to provide their service to us:
| Provider | Role | Data concerned | Country / region |
|---|---|---|---|
| OVH | Hosting of the service, the database, the backups and the logs | All the data of the service | France |
| Resend | Sending of service emails | Recipient's email address and content of the message | European Union region |
| Stripe (Stripe Payments Europe, Ltd., Ireland) | Payment for credits. Stripe is the controller for the payment data it collects itself | Payment data (entered at Stripe), amount, transaction identifiers; we send it the identifier of the organization and the number of credits | European Union, with possible transfers according to Stripe |
| Sentry | Detection of server errors and slowdowns, and of mobile application crashes | Technical information about an error (requested address, code trace, version). For the application: see section 9. No name, contact details or screen content is deliberately sent; the IP address and sign-in credentials are not attached to the server report | European Union region |
| Apple and Google | Distribution of the application (App Store, Google Play) | Data these stores collect themselves, according to their own policies | — |
The data are also accessible:
- to the members of your organization, according to their role (a signed-in member can read the records of all the participants of the organization; only some roles can modify them);
- to us, for support and maintenance: our super-administration account can view the data of all organizations; this access is only used to answer a request or resolve an incident;
- to the authorities, if the law requires us to.
We neither sell nor rent any data.
6. Transfers outside the European Union
All data are processed in the European Union.
7. How long we keep them
| Data | Period |
|---|---|
| User account and organization | As long as the account exists. Deleted at your request (section 10). When an administrator deletes their organization from the application, it immediately stops being accessible, and all its data (accounts, events, participants, results, history) are permanently erased within 60 days. A deleted account — deleted by you from the application, or by an administrator of your organization — immediately stops being accessible; an administrator of your organization can restore it for 60 days, after which it is permanently erased. An account that remains inactive for 13 months (no sign-in) is deleted. |
| Participants and results | They follow the event (rows below): by default, at most about 15 months after the end of the event's last race (13 months, then 60 days), or earlier if the organizer deletes a participant, a race or the event, or if the organization is deleted (within the period stated above). Deleting a participant or a race erases it immediately |
| Finished events | An event whose races are all finished stops being accessible 13 months after the end of its last race, then is permanently erased (with its races, participants and results) 60 days later. Default periods, specific to each organization |
| Deleted events | An event deleted by the organizer immediately stops being accessible; it is permanently erased 60 days later |
| Test events | Stop being accessible 24 hours after their creation, then are permanently erased 60 days later |
| Audit log | 365 days by default (adjustable), with daily automatic deletion. A log entry keeps the label of what it concerns (for example “bib 1234 — DUPONT Marie”): deleting a participant or an event therefore does not erase these entries before they expire, unless the whole organization is deleted |
| Server technical logs (IP addresses, requested addresses, email addresses at sign-in) | 6 months |
| Database backups | 14 rolling days. A deleted piece of data may therefore remain in a backup during this period, then disappears |
| Sessions and sign-in tokens | Web session: expires after 24 hours of inactivity. Application token: 30 days. Password reset link: 1 hour. Handover from the application to the browser for a purchase: a few minutes, single use |
| Credit purchases | Accounting records are kept for 10 years (legal obligation) |
| Crash reports | 90 days |
| Messages received by support | 3 years after the last exchange |
8. How we protect your data
- All communications are encrypted (HTTPS).
- Passwords are stored in encrypted, non-reversible form; we cannot read them.
- The data of each organization are partitioned: a user only sees those of their own organization.
- Rights are assigned by role (read-only, timing, bib handout, organization, administration).
- Repeated sign-in attempts are limited, and the actions of teams are logged.
- In the mobile application, the sign-in token is stored in the phone's secure storage (Keychain on iPhone, Keystore on Android).
- The server is protected (firewall, key-based access, automatic security updates), and the database is backed up every day.
- In the event of a data breach likely to affect your rights, we will notify the CNIL (the French data protection authority) within 72 hours and, where the law requires it, the people concerned.
9. What is stored on your device, cookies and trackers
Mobile application. To work without a network (at a finish line, for example), the application stores on the device: your sign-in token (in secure storage), a copy of your organization's data (events, races, participants, results), the splits entered but not yet sent, a few preferences and the speech recognition model. Signing out erases all of this: the token, the copy of your organization's data, the profile and the results and history caches. Only the splits entered but not yet sent remain (a bib number and a time, without a name: a token that expires in the middle of a race must not make them get lost, they are sent at the next sign-in) and a few device settings. On a device you lend or sell, sign out first; uninstalling the application also deletes the remaining splits.
Crash reports. When the application crashes, a report is sent to Sentry so that we can fix the defect. It contains: the type of error, the place in the code concerned, the application version, the platform, the device model and operating system, an identifier specific to the installation (to count the people affected), the address of the server the application was using, and a few recent actions without their content. Before anything is sent, we remove: the parameters of requested addresses (for example a searched name), the tokens of public links, the text of server error messages (which could name a runner) and the application's internal messages. No screenshot is taken. No name, email, phone number or password should appear in a report. The application also tracks the share of sessions that end without a crash, by version.
Web application (app.smartiming.net). It uses a session cookie (“race_timing_session”) to keep you signed in, and the browser's local storage for your token and a few preferences. These are strictly necessary for the service to work.
smartiming.net website. No tracking cookie, no audience measurement tool, no advertising. The typeface is hosted on our own server: no third party receives your IP address when you browse the website.
10. Your rights and how to exercise them
Depending on the case, you have the right of access, rectification, erasure, restriction, objection and portability of your data, as well as the right to give instructions about what happens to them after your death. Where the processing is based on your consent, you can withdraw it at any time.
- How: write to contact@smartiming.net, stating your request and, if you have an account, the organization and email address concerned. We may ask you for proof of identity if there is a doubt about your identity. We answer within one month.
- Delete your account: from the application, profile menu → “My account” → “Delete my account”. You are signed out immediately and your account is no longer accessible; an administrator of your organization can restore it for 60 days, after which it is permanently erased. If you are the only administrator of your organization, the application offers you either to delete the whole organization (with all its data), or to appoint another administrator first. You can also write to us at the address above.
- What we may keep despite an erasure request: the organization's audit log until it expires (365 days by default), the accounting records of purchases (10 years, legal obligation) and the data still present in backups until they are renewed (section 7).
- You are a participant: send your request to the organizer (access, correction, erasure, anonymity). If you cannot reach them, write to us: we will forward your request.
- Complaint: if you believe your rights are not respected, you can lodge a complaint with the CNIL — Commission nationale de l'informatique et des libertés, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, www.cnil.fr/plaintes.
11. Changes to this policy
We may change this policy, for example when the service changes. The date of the last update appears at the top of the page. In the event of a significant change, we will inform you in the application.
12. Contact us
contact@smartiming.net All contact details: Contact page. Publisher and host: Legal notice.