Privacy
What the Scotland connector sees when you use it, what it keeps and for how long.
No accounts, nothing asked of you
The connector is a free, read-only service run by Joe McGinley, an individual in Scotland. It has no accounts, sets no cookies, and never asks for your name, email or location history.
A question reaches it as coordinates, dates, walk names and weather limits. It answers from forecast and climate data it has already fetched; your question is not passed on to MET Norway, Walkhighlands or anyone else.
What a request carries
Through a hosted assistant such as Claude or ChatGPT, the assistant's servers make the call, so the connector sees their network address and the tool arguments the assistant sends. Your conversation stays with the assistant.
ChatGPT also attaches hints to each call: a coarse location (city, region, country and approximate coordinates), an anonymised user and conversation id, your locale and a user agent. The connector reads none of them, and since request bodies are never logged, none is kept.
An assistant that runs on your own computer, such as Claude Code or Codex, calls from your machine, so your network address and its user agent reach the gateway. The same holds when you call the REST API directly, where the request itself is visible too: for plan, the point and dates in the URL.
What is kept
The gateway in front of the connector writes an access log line for each request: the time, the network address, the user agent, the path with its query string (so a plan's coordinates), the response status and size. Request bodies, which carry check and MCP arguments, are not logged. These lines live only in the gateway's own rolling log on the server, which new traffic overwrites, and are used only to keep the service running and to stop abuse. They are never shipped to a log service, copied or kept anywhere else.
The connector itself counts calls by tool, by surface (MCP or REST) and by whether the caller is a known assistant, with no address or arguments attached, and logs internal errors with the tool name and the error. Rate limits count requests per network address in memory and keep nothing.
Who else handles it
Requests pass through Cloudflare, which carries the traffic and caches answers under its own privacy policy. The service and its logs run on Google Cloud. Neither gets anything from the connector beyond what carrying and hosting the traffic involves.
Nothing is sold, shared for advertising, or used to train models.
Questions and requests
To ask what is held about a network address you used, or to have it deleted, email joe@jomcgi.dev. Since logs carry no account or name, include the address and roughly when you made the requests.
If this policy changes, the date at the top of the page changes with it.