Skip to main content
Back to radar

Privacy policy

Last updated: 8 November 2026

Controller & contact

HORSERADAR.NL ('we') is the controller for personal data processed on this site. The service is operated from the European Union. For all privacy matters, contact: hello@horseradar.nl.

What we collect

Browsinga visitor identifier, language and theme preferences, consent choices, and usage records such as listing clicks, likes and reports. Optional analytics records help us understand use of the site.
Waitlistyour email and any optional name you provide, plus signup language, source/referrer, visitor reference, an IP-address hash and unsubscribe information.
Sign-inemail, account and session references, login times, expiry information and security hashes. Account records link your subscription status and devices.
Payments and HORCEL creditsorder references, purchased bundle and credit quantity, amounts and currencies, subscription or payment status, Stripe customer/subscription/session/payment references, and payment events received from Stripe. Those events may contain payer or billing information supplied by Stripe. We also keep credit balances, usage and balance changes, purchased-credit review holds, and records used to resolve payment issues.

Listing data we index (horse and sale details, and any personal data a seller chose to publish in a public listing — e.g. a stable, breeder, or agent name) is not collected from you: we obtain it from publicly accessible third-party auction websites. Under Art. 14 GDPR we must name that source, and we do so here. Because individually notifying every person named in a public listing would be a disproportionate effort, we rely on Art. 14(5)(b) and give this notice publicly instead; if you are named in a result and want it removed, email hello@horseradar.nl.

Outbound clicks & partner measurement

When you follow a listing link, you pass through our redirect (/go). We record the click event: target site, time, the listing involved, and a one-way salted hash of your IP address used solely to filter bots and duplicate counts. The click-event record stores the hash rather than the raw IP address. Separate technical access and security logs can contain IP addresses, request paths, user-agent information and timing data to operate and protect the service. Partner auction houses may receive aggregated, anonymous statistics (e.g. total clicks to their sale) — never your identity. Sponsored placements are always labelled ('Partner', 'Featured').

Recipients & hosting

Data is processed on servers in the European Union (hosting: Hetzner Online GmbH, Germany). A content-delivery/security provider (e.g. Cloudflare) may process technical connection data to serve the site. We use no third-party advertising networks and share no personal data with them.

Payments use Stripe-hosted checkout. We send Stripe the account or order references needed to match a payment; Radar subscription checkout also sends your verified email to prefill checkout. We receive payment confirmations and related events from Stripe to manage subscriptions, credits, reconciliation and payment review. Stripe processes information you enter in its checkout under its own notices.

Retention

Visitor cookie12 months from last visit.
Usage countersreset every calendar month.
Outbound-click eventsused for bot-filtering and partner reporting. The previous 24-month deletion/anonymisation schedule is currently suspended under our record-preservation hold; historical records remain retained. Privacy requests are assessed individually, including applicable obligations; the hold does not remove your statutory rights.
Registered emailuntil you request deletion.
Consent choiceuntil you change it.

Browser storage, account records and payment records are separate. Resetting a monthly usage balance or clearing browser storage does not delete account, order, payment-event or credit-ledger records. These records support account access, payment reconciliation and credit accounting. For questions or requests about stored records, contact hello@horseradar.nl.

Your rights

Under the GDPR you can request access, rectification, erasure, restriction of processing, data portability, and object to processing based on legitimate interest. You can withdraw analytics consent at any time (see the cookie page). To exercise any right, email hello@horseradar.nl. You also have the right to lodge a complaint with the Dutch supervisory authority, Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or the authority in your own EU country.

Changes to this policy

We may update this policy as the service evolves. Material changes are announced on this page with a new 'last updated' date. Continued use after an update does not waive any of your statutory rights.

Launch email subscriptions

Launch emails are optional and require separate consent and email confirmation. We store your address, language, consent wording/version, request, confirmation and withdrawal times, and salted IP hashes for abuse prevention. Confirmed addresses and this subscription choice are synced to Resend for email delivery and subscriber management, separately from our EU application hosting. Unsubscribe through the confirmation page or any launch email. Consent and withdrawal history is retained to respect your choice. Google sign-in and requested shortlists do not enroll you. Other email preferences are separate.

Social sign-in

Google or Apple sign-in provides a verified email and stable provider account identifier. We use these to create or authenticate your HORSERADAR account. Linking an existing account requires signing in to that account first. Apple may provide a private relay address. We retain encrypted Apple authorization tokens for validation and revocation, and security event history. We do not receive your provider password. Browser-binding cookies hr_social_flow, hr_consent_flow and optional hr_review_flow expire after ten minutes.

ChatGPT plugin: data and purposes

News, horse search, horse cards and public photos are available without registering. Registration is optional for discovery. Reported catalogue prices require a connected HORSERADAR account; free accounts qualify. Personal saved data and account features require a connection and the relevant permissions. We receive the tool arguments sent by ChatGPT, such as a horse name, pedigree, filters, selected horse IDs or news headline keywords. We do not receive your full conversation history; text included in tool arguments does reach us. Do not include passwords, payment details or sensitive personal information.

Connecting an account stores its permission grant, scopes, timestamps and credential hashes. An explicit save stores the search criteria or horse ID, intent, request reference and account-linked status history. We process these to provide the features you request. Security and abuse prevention support our legitimate interest in protecting the service. Optional search measurement requires separate consent, starts off, and stores result counts with account/grant references and timestamps, rather than search text. Saving does not subscribe you to marketing or authorize seller contact, bidding or payment.

Separate saved-search, watchlist and alert features use your account’s existing access and plan settings. They store requested search criteria, watched horse IDs, notification preferences and alert/delivery status. Email alerts use your own verified account address, start off, and require an explicit request to enable them. Connecting or saving a request does not enable email alerts or marketing.

We keep daily aggregate counts of search categories sent through the plugin, for example sex, studbook, whether an auction-source filter was used, other filter categories, sort choice and whether results were returned. These counts contain no search text or direct account, connection, visitor or IP identifiers. We use them to understand search demand and improve catalogue coverage. They are stored separately from optional account-linked search measurement.

Plugin recipients and news providers

Tool results are returned to ChatGPT/OpenAIpublic catalogue results, attributed news headlines and, when authorized, your saved requests and statuses. OpenAI processes data under its own terms and privacy notices. Authorized HORSERADAR staff can manage saved requests. Application hosting is with Hetzner in the EU; delivery and security providers may process technical connection data.

News uses cached public Horses.nl and Horse & Hound feeds. Your search words and HORSERADAR account identifiers are not sent to those publishers to fetch the feeds. Opening a publisher or listing link visits that provider under its own privacy notice. The plugin does not send requests to sellers or advertisers.

If you explicitly enable email alerts, our configured email-delivery provider receives the verified destination address and alert content to deliver them. Horse-card photos use a bounded first-party proxy; your browser cookies, OAuth credentials and visitor identifiers are not forwarded to source image publishers.

Operational request monitoring

For security, reliability and troubleshooting, we use self-hosted Langfuse for operational request monitoring under our legitimate interest. It records server-generated request/trace references, route/method/tool categories, timestamps and durations, outcome/status/error categories, result counts, allowlisted argument-field names, whether a query was supplied, sign-in status, bounded result limits and photo response sizes. Raw search/chat text, free-text argument values, credentials, cookies, direct account/visitor IDs, user IP addresses and publisher URLs are excluded from plugin trace payloads.

Operational monitoring is separate from optional account-linked search measurement, which requires your consent. Technical references support correlation for troubleshooting; these individual request records are not described as anonymous statistics. Separate technical access logs may contain IP addresses as explained above. Retention and privacy controls are described below.

Plugin retention and your controls

Access credentials expire after one hour; each rotated refresh credential expires after 30 days. Expiry stops credential use and does not erase the stored hash or history. Connection grants, saved requests, status/security history and optional measurement records currently have no automatic deletion schedule and remain retained under our record-preservation hold. We do not promise a deletion deadline that is not implemented.

In Account, withdraw optional ChatGPT search measurement or disconnect a connection to stop future access to your account. You can review and close your saved requests; closing or disconnecting retains their history. These controls are separate from website analytics and personalisation. For access, correction, export, erasure or other privacy requests, contact hello@horseradar.nl. We assess requests individually, including any applicable retention obligations; the preservation hold does not remove your statutory rights.

You can also manage saved searches, watchlists and alert settings through Account. Alert and delivery history is separate from a connection grant; contact us for privacy requests about these records.

Operational plugin traces currently have no configured automatic expiry in our self-hosted Langfuse project and remain stored indefinitely under our record-preservation policy. Turning off optional search measurement does not disable this separate operational monitoring. Disconnecting removes account access; public requests can still produce technical monitoring records. We assess privacy requests about these records individually, with your statutory rights preserved.

Daily category counts are aggregates; they currently have no automatic deletion schedule and remain retained under our record-preservation hold.

Personalised recommendationsUnavailable

When on, we use your on-site activity to build the 'For you' rail and tailor recommendations. Turn it off to stop personalisation profiling — you keep full access to search.