Last updated 2026-11-06.
cairo-medicines-mcp serves official medicine label information to AI assistants. It has no user accounts and does not ask for personal data.
To operate and protect the service we record, per request: a timestamp, the tool called, the query text your assistant sends (for example a medicine name and topic), the response's coverage outcome and a short summary of what was served (such as the medicine and document type), latency, and the connector token or API key that made the request. Connector tokens identify an installation for rate-limiting; they are not linked to your name, email, or account, and we do not ask for any of those.
We also record technical details your assistant's app sends with each request: the app's name and version, its user agent and language settings, and a session identifier. If the app names itself with the prefix "cairo-", as CAIRO's own testing tools do, or the request comes from an app name or connector link that CAIRO uses itself, we mark the request as internal so our own use isn't counted as usage. The app declares its name itself; we don't verify it. Some assistant apps (for example ChatGPT) also send a pseudonymous user identifier, the user's locale and an approximate location (country, region and city). ChatGPT also sends its own session identifier for each conversation; we store it only as a one-way keyed hash and use it only to group the requests of one conversation together. We store connector tokens, session identifiers and user identifiers only as one-way keyed hashes. For each hashed user identifier and hashed connector token we also store the time it was first seen, so we can tell new installations from returning ones; this record holds the hash, the app channel and that timestamp, and no IP addresses. These usage records do not include IP addresses, precise coordinates, or free-text messages beyond the query fields above.
Operate the service, apply per-consumer rate limits, investigate abuse, and understand aggregate usage (for example, which topics go unanswered so coverage can improve). We do not sell this data and do not share it with advertisers.
Nobody outside the service's operator. The service runs on a cloud hosting provider (currently Railway), which processes traffic and storage on our behalf like any host; we do not pass logged data to any other third party, and there is no analytics or advertising tooling in the service.
Connector links can be discarded at any time. Get a new one from the install page and the old identity goes stale (we can also revoke it on request). To have request records associated with your connector link deleted before the retention window ends, contact us with the link.
Request records are deleted after 90 days. Aggregated statistics that contain no query text may be kept longer. First-seen records may also be kept longer: a pseudonymous hash of the user or connector link and the time it was first seen. They have no fixed deletion date, and we delete them on request.
The service is operated for users in the EU among others. Query text may incidentally contain personal information if your assistant includes it. Avoid sending personal details; the service never asks for them. To exercise data rights or ask questions, use the contact below.
If you run the server yourself, no data reaches us at all: telemetry is written only to your own machine, and can be disabled outright.
alex@cairoplatform.com