Privacy Policy

Bernat Erta Majó (private individual). Email: contacto@racefinder.io.

No Data Protection Officer has been appointed, as the circumstances requiring one do not apply. Contact for any privacy or data protection matter: contacto@racefinder.io. The owner's full identifying details are in the Legal Notice.

• Account and authentication: email address, password (stored only as a cryptographic hash), account identifier, and registration and access dates.
• Profile: name, country, and category/gender, if provided by the user.
• Athletic performance data: events, personal bests, season bests, target marks, and their years. They are data the user enters voluntarily in order to use RaceFinder's profile and analysis features. They are processed in accordance with the purposes and legal bases described in this policy. These marks and personal bests are not health data. RaceFinder does not process special-category data under article 9 of the GDPR.
• Preferences: preferred regions and countries, competition level, indoor/outdoor track preference, language, unit format, visual theme, and notification settings.
• Saved competitions and comparisons, and the alerts generated from them.
• Subscription data: plan, status, trial and billing period dates, and customer and subscription identifiers provided by the payment provider. RaceFinder never receives or stores card numbers.
• Conversations with Findi, the in-app assistant: the user's name, chat messages, and the profile data used to answer (event, gender and marks), together with that conversation's context.
• Usage data: see the "Usage measurement" section.

RaceFinder's own usage measurement and marketing emails take place only with consent. Own measurement does not start until it is accepted in the banner; if it is rejected, no visitor identifier is created. Marketing consent is separate, optional at sign-up, and can be withdrawn in Settings without affecting the account. Findi is provided because the user asks for it, as part of the service.

Creating a RaceFinder account requires being at least 14 years old. Accounts may not be created by anyone under 14. During registration, the user is asked to confirm they are at least 14: this is a self-declaration by the user, not an identity or age verification. If an account belonging to someone under 14 is detected, it will be deleted.

This minimum age applies only to account creation. It does not mean that 14 is the age at which someone may contract paid services: the capacity to purchase RaceFinder Pro is governed by applicable civil law, and minors need authorization from a parent or legal guardian to subscribe.

RaceFinder does not use Google Analytics, Plausible, PostHog, Mixpanel, or advertising, and it does not share data with advertising networks or track people across sites.

Own measurement, with consent (Art. 6(1)(a)). The service keeps its own usage log, stored in RaceFinder's database. Each recorded event contains:

• a random visitor identifier and a session identifier, generated in the browser;
• the event name (for example, that a search or a feature was opened);
• the interface language;
• the device type (mobile, tablet, or desktop);
• when a session is active, a one-way hashed account identifier.

The usage log does not contain a name, email address, athletic marks, free text, or IP address. To limit abusive requests, only a shortened IP address is stored: its network part (the first three blocks of an IPv4 address or the first three groups of an IPv6 address), never the full address. It is kept with a request counter, outside the usage log, and deleted automatically after about one day.

Own measurement starts only after consent in the banner. Until then no visitor identifier is created and no own usage data is sent. If it is rejected, the identifier from earlier visits is deleted and the choice can be changed at any time from the Cookie Policy. If the browser sends the "Do Not Track" signal, no event is recorded.

Own usage log retention: up to a maximum of 12 months, after which it is deleted or anonymized. A daily automated process handles this.

See the Cookie Policy. In short, without consent only storage that is strictly necessary for the service to work is used, including what is only written at the user's request (the language picked, the comparison and the search profile), and storage that remembers a preference chosen by the user. RaceFinder's own usage measurement keeps its identifiers only after it is accepted in the banner. No advertising or cross-site tracking cookies are used.

Providers that actually process personal data on RaceFinder's behalf:

• Lovable Cloud (built on Supabase) — accounts, authentication, database, and sending account confirmation and password reset emails.
• Lovable hosting (Cloudflare edge network) — publishing the website. Like any hosting provider, it processes connection data, including IP addresses, to serve pages and protect them against attacks.
• Paddle — payments, subscriptions, billing, and refunds. Paddle acts as the Merchant of Record for Pro subscriptions and as an independent controller of the payment relationship, with its own privacy notice: https://www.paddle.com/legal/privacy. When the checkout is opened, Paddle also loads its Paddle Retain tool (formerly ProfitWell), which sends Paddle (api.profitwell-events.com) events from the use of the checkout for subscription management; Paddle carries out that processing under its privacy policy: https://www.paddle.com/legal/privacy.
• Lovable AI Gateway, using OpenAI models — the Findi assistant. To generate each reply, the user's name, the conversation messages and the profile data used to answer (event, gender and marks) are sent. The request is sent with provider-side storage turned off. OpenAI acts through Lovable.
• Lovable AI Gateway, using Google models (Gemini) — transcription of public competition documents, classification of public competition web pages and documents (whether a page or document is about that competition) and translation of public competition entry conditions into the language the page is read in. Those documents, pages and conditions may include athlete names that have already been published. The account profile is not sent.

Services used to obtain competition information that do not receive the account profile or messages: Open-Meteo (weather and venue altitude), OpenStreetMap/Nominatim (location lookup), World Athletics and organizer websites (public competition data), Firecrawl (reading public web pages, which may contain athlete names already published) and Cloudflare DNS (security check before fetching an external page).

Data may also be disclosed to professional advisors or public authorities when required by law. Personal data is never sold.

Some processors handle data outside the European Economic Area, in particular in the United States. Where the provider is certified under the EU-US Data Privacy Framework, the transfer may rely on that adequacy decision. Otherwise, or in addition, the transfer relies on the European Commission's Standard Contractual Clauses or another Chapter V GDPR safeguard. The exact region of each processing operation cannot always be determined from the application.

• Lovable Cloud (Supabase) — database, authentication and account email. Provider established in the United States; processing may take place outside the EEA. Safeguards: the EU-US Data Privacy Framework where the provider is certified, and/or Standard Contractual Clauses.
• Cloudflare — edge network that publishes the site and processes connection data, including IP addresses. Provider established in the United States, with a worldwide presence. Safeguards: the EU-US Data Privacy Framework where it applies, and/or Standard Contractual Clauses.
• Paddle — payments and invoicing, as an independent controller of the charge. Paddle operates from the United Kingdom, which has an adequacy decision, and may also process data outside the EEA, including in the United States, under its own safeguards.
• OpenAI, through the Lovable AI Gateway — messages and profile data sent for Findi. Processing in the United States. Safeguards: the EU-US Data Privacy Framework where the provider is certified, and/or Standard Contractual Clauses. The request is sent with provider-side storage turned off.
• Google (Gemini), through the Lovable AI Gateway — public competition documents, web pages and entry conditions. Processing in the United States. Safeguards: the EU-US Data Privacy Framework where the provider is certified, and/or Standard Contractual Clauses.
• Firecrawl — reading public web pages to enrich competition information. Processing may take place outside the EEA, including in the United States. Safeguards: those in the contract with the provider, in particular Standard Contractual Clauses where the transfer is not covered by an adequacy decision. The exact region is not recorded in the application.

RaceFinder displays athlete names and their marks when they appear in historical competition results. Those data are not collected from the athlete: they come from sources that have already published them, in particular official organiser results and World Athletics. Informing each person individually would be impossible or would involve a disproportionate effort, given the volume and the public origin of the data (Art. 14(5)(b) GDPR). This section meets the information duty in Art. 14.

• Categories: athlete name, mark, event, sex or age category where shown, place, competition and edition.
• Source: public organiser results and World Athletics.
• Purpose: to show the sporting history of competitions. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in informing users about competitions from data the source has already published.
• Rights: the person may object and request erasure by writing to contacto@racefinder.io. RaceFinder will act on the request unless there are compelling legitimate grounds or a legal obligation to keep the data.

• Account and profile: for as long as the account exists. There is no automatic deletion for inactivity: no account is currently deleted automatically.
• Saved competitions, preferences, alerts, and settings: deleted together with the account.
• Usage log: up to a maximum of 12 months, after which it is deleted or anonymized by a daily automated process.
• Findi conversations: 180 days from the last user message. Reading or renaming a conversation does not extend that period. They are also deleted when the account is deleted.
• Subscription and billing: upon account deletion, RaceFinder deletes or anonymizes its own subscription records once they are no longer needed, keeping only what must be retained for legal, accounting, or transaction-evidence purposes, or to defend against claims. Tax receipts and invoices for purchases are kept by Paddle, which acts as the Merchant of Record for Pro subscriptions, under its own legal obligations.
• Pending payment tickets: expire after 60 minutes and are deleted after 7 days at the latest.

Users can delete their account at any time from Settings → Account → Delete account. Personal data associated with the account — profile, events and marks, preferences, saved competitions, notes, alerts, settings, account-linked usage logs, and the login identity itself — is deleted or anonymized once it is no longer needed for the purposes described in this policy. If a Pro subscription is active, trialing, past due, or paused, RaceFinder asks Paddle to cancel it immediately so that no renewal occurs; if that request does not complete, account deletion still proceeds. RaceFinder does not keep accounts merely "deactivated".

Deleting the account does not necessarily mean immediate deletion of every record: certain data may be retained, on a limited basis and only for as long as strictly necessary, where there is a legal, tax, or accounting obligation, where evidence of a transaction is required, or where it is necessary for security reasons or for the establishment, exercise, or defense of legal claims.

Users may exercise the rights of access, rectification, erasure, restriction, portability, and objection, as well as withdraw consent where it is the basis for processing, by writing to contacto@racefinder.io. A response will be provided within one month. A complaint may also be lodged with the Spanish Data Protection Agency (AEPD), C/ Jorge Juan 6, 28001 Madrid, www.aepd.es.

Technical and organizational measures are applied, such as encrypted connections, access controls, and row-level restrictions in the database. No online service is completely secure.

We keep a technical, temporary record (30 days) of the security blocks applied by the browser, to detect errors and attacks; these records include no data that identifies you.

Users may voluntarily authorize an external application or assistant to view and manage their own saved competitions. Access exists only when the user expressly authorizes it, is limited to their own account data, and can be revoked. RaceFinder does not grant external access without that authorization.

This policy may be updated. Significant changes will be made visible within the application.