Privacy Policy

Who this policy covers

This policy applies to visitors, prospective customers and account holders using RacingAPI.net. For questions about how your personal data is handled, or to make a privacy request, email support@racingapi.net. We provide horse racing data, not a betting service.

Affiliate bank details

Affiliates can privately provide account holder and bank names, bank country and either a UK sort code and account number or international IBAN and BIC/SWIFT. We encrypt saved bank identifiers to administer manual commission payments, display masked identifiers in the account, and restrict full access to authorised administrators through an audited reveal. Format and checksum validation do not establish ownership of an account. Notifications about changes do not contain bank identifiers. You can replace or remove these details unless a payout is pending; contact support to resolve an open payout first. Deleting the saved payment destination does not erase financial, audit or payment records we must retain for accounting or legal obligations. Do not send bank details to our AI assistant or in support messages.

Referral metrics include anonymous cumulative counts of consented tracking events. These aggregate totals may remain after underlying expired click records are removed; visits without consent are not counted.

Affiliate programme

When you apply as an affiliate, we store your full name, application email address, postal address, account identity, website URL, promotion description, payout contact email, accepted terms version and application reviews. We use this information to review your application, administer the programme, prevent fraud and arrange manual payments. Application details are accessible to you and authorised administrators, not other affiliates or referred customers.

With a visitor's explicit consent, an optional referral cookie links a new account to the first accepted affiliate referral for up to 30 days. We record an anonymous click identifier, timestamps, the referred account, subscription invoice references, commission calculations and payout records. Affiliates see anonymous customer labels, not referred customers' email addresses or payment details. You can remove the optional cookie on the Cookies page. Removing it does not erase financial records already required to administer earned commissions or comply with accounting obligations. Unclaimed expired tracking records are removed after a further 60 days; payment and contract records are kept for the applicable accounting and legal retention period.

AI-assisted racing selections

For Enterprise selections, a rule-based system ranks supplied racing records and an AI service writes a two-sentence explanation from the selected evidence. This background process sends racing statistics, not your API keys, account details, payment information or support conversation, through our hosting provider's AI service using OpenAI. We save the analysis, explanation, price observations and internal revisions to maintain a record of what was published. These live selections are not automated decisions about you or your account and are not guaranteed outcomes.

AI product assistant

Our optional AI assistant answers questions using public product information and documentation. When you send a message, the current conversation is processed by our server and our hosting provider's AI service using OpenAI to generate a reply. We do not automatically save AI chat transcripts in our application database or browser storage; the conversation stays in page memory until you clear it or reload. If you choose Ask our team, you can review and submit a separate support request with your name, email and question. Only the reviewed form fields are saved to our support inbox; your full AI transcript is not included automatically. Our hosting and AI providers may process and retain technical and request data under their own policies. Do not send payment, password or API-key details. The assistant cannot access your account or change your subscription. AI replies may be inaccurate; confirm important details in our documentation or contact support@racingapi.net.

Information we collect

When you create an account or contact us, we receive information such as your name, email address, organisation name if supplied, and the contents of your message. Our sign-in provider processes credentials and authentication information. We store account and API-key records; API requests can produce usage and security records, including the endpoint, response status, timing and account identifier.

If you start a subscription, our payment provider handles checkout and card details. We receive customer, subscription and billing status identifiers needed to manage your plan; we do not ask you to enter card numbers into the RacingAPI.net site. Standard server and security logs may also include technical information such as your IP address and browser details.

Why we use it and lawful bases

We use account and billing information to provide your requested service and manage subscriptions (performance of a contract). We use request and security records to apply limits, prevent misuse, troubleshoot incidents and improve reliability (our legitimate interests). We retain information required for accounting, tax and other legal requirements (legal obligation). We use contact-form messages to respond to your enquiry (our legitimate interests or steps taken at your request before entering a contract).

Who handles the information

We use service providers for hosting, authentication, payment processing and support communications. They may process the information needed to deliver those services. Some providers may process information outside the UK; contact us for information about the providers and international transfers relevant to your account. We do not sell your personal information to advertising brokers.

How long we keep it

We retain account and billing information while needed to provide the service and afterwards where necessary for legal obligations, disputes or security. API usage records are kept as needed for metering, troubleshooting and abuse prevention. Support messages are kept as needed to resolve the request and maintain a record of the conversation. There is no single retention period covering every category; email us if you want information about a particular record or wish to request deletion.

MCP connections to AI clients

If you connect an AI client through our MCP server, we record the connection name, the API key you chose to link, the redirect origin you approved and creation and revocation times, together with usage and security records for tool calls. We do not receive your conversations with the AI client beyond the tool requests it sends us.

The racing data returned to a tool call is sent to the AI client you authorised, which processes it under its own terms and privacy policy. You can revoke a connection at any time in Dashboard, Connect AI.

Your choices and rights

Depending on the circumstances, you may request access, correction, deletion, restriction, portability or an objection to certain processing. You can update some account details in the dashboard. For other requests, email support@racingapi.net; we may need to verify your identity first. You also have the right to complain to the UK Information Commissioner's Office (ico.org.uk).

Security and changes

We restrict account access, use authenticated connections and do not display API-key secrets again after creation. No online service can guarantee absolute security. We may update this policy when the service or its providers change; the revision date on this page identifies the current version.