MCP connector privacy policy
What the golfdata.online MCP endpoint processes when an AI assistant calls it, and for how long. Plain language; this page is the binding text for the connector. The site-wide policy is on the legal page.
Last updated: 22 November 2026
Controller
Canary Tech Labs S.L., contact hello@golfdata.online. We process personal data under the GDPR (EU 2016/679) and the Spanish LOPDGDD 3/2018.
- Company
- Canary Tech Labs S.L.
- Tax id (CIF)
- B19373414
- Registered address
- Calle Villalba Hervás 2, planta 4, puerta C, 38002 Santa Cruz de Tenerife, Spain
- Commercial registry
- Registro Mercantil de Santa Cruz de Tenerife, Sección 8, Hoja TF-72898, inscripción 1.ª (09/09/2024)
- Contact
- hello@golfdata.online
What the endpoint processes
Requests to the endpoint go through golfdata.online to our server function (hosted on Supabase, EU data centre; the website runs on Vercel, Frankfurt region). The website forwards your client's IP address and user-agent string to the function so that limits and counts work per client instead of per website server.
IP address: used only as the key of the rate limiter. It is kept in the function's memory for one-minute windows. When the shared limiter is switched on, only an HMAC-SHA256 hash of it is written to the database, for the current one-minute window; expired rows are deleted. The IP is never stored with a club, a question or a booking request, and it is never written to our logs: error messages are stripped of IP addresses, URLs and credentials before logging. Server logs of the hosting providers keep technical request data for security for a short time.
User agent: read once to recognise the assistant family (for example anthropic, openai, google, perplexity). Only that family name is stored, as a per-club, per-day count of lookups, so that a club can see how often assistants ask about it. The raw user-agent string is not stored.
Tool arguments: search terms, coordinates, club identifiers and the optional golfer's question or topic. Search results are cached in the function's memory for 60 seconds; the cache holds public club data only.
The golfer's question
When an assistant passes on the question a golfer asked (the optional question and topic arguments), we store it to show clubs what golfers want to know. Email addresses, links, handles and long digit runs such as phone numbers are replaced by placeholders on arrival; the original text is deleted after 30 days and the cleaned copy after a year. Clubs only ever see counts and reworded summaries, never the text. Passing the question is optional and never changes the answer.
Booking requests
When an assistant sends a booking request on a golfer's behalf (only possible for a club whose card says booking.requests_enabled is true, and only with the golfer's consent), we store the golfer's name, email, optional phone, the play date, tee time, players and holes, and the message, and forward them to the club you chose so it can reply directly. golfdata only forwards the request and does not confirm the booking.
The golfer's details are kept for 24 months and then anonymized: name, email, phone and message are deleted and only non-personal booking statistics remain. A golfer can ask us to erase them sooner at any time by writing to hello@golfdata.online. For the email channel the request is also sent to the club's booking address; for the WhatsApp channel the golfer opens a link to the club's WhatsApp number themselves.
What we do not do
No cookies and no advertising identifiers are set by the endpoint. We show no advertising and we never sell data. We do not record identities of golfers or of the people using an assistant, and we never count or see visits to a club's own website.
Hosting providers (Vercel, Supabase) act as processors under data-processing agreements.
Your rights
Access, rectification, erasure, restriction, portability and objection, by email to hello@golfdata.online. You can also complain to the Spanish Data Protection Agency (aepd.es).