Orreria connector privacy notice

Effective October 19, 2026. This notice covers the Orreria MCP connector and its three read-only tools. Other Orreria website features, support messages, and visits to linked sites are separate interactions.

What reaches Orreria

The connector receives the named public place query you ask it to resolve, temporary place or reading identifiers, and optional section or result limits. Requests also include ordinary protocol, connection, IP address and client metadata. Only send public locality names. Do not include street addresses, precise GPS coordinates, personal reflections, names of private individuals or confidential information.

The tools do not request your account records, conversation history, Claude memory, uploaded files, email address or payment details. Personal information mistakenly included in a query can still reach the service.

How it is used and shared

Orreria uses the query to resolve a public place and assemble a reading. Named queries may be sent to OpenStreetMap Foundation’s Nominatim service. Public locality coordinates may be sent to Open-Meteo for weather/timezone context and iNaturalist for nearby public observation records. Those providers receive requests from Orreria’s server, rather than your device’s precise location. Source links are citation metadata; the source-reference tool does not fetch the linked documents.

The backend is hosted on Railway. These documentation pages are hosted by Netlify. The initial connector configuration makes no calls to generative AI models. Claude processes tool requests and results under the Anthropic privacy policy and your Claude account settings. Enabling any optional server-side AI processing requires updating this notice first.

Retention

• Temporary public place records and reading citation/method records use process-local caches capped at 500 entries each. Identifiers expire after 15 minutes. Expired entries are removed on later tool requests; a restart removes the caches.
• To limit repeated upstream requests, named geocoding queries and results are cached in memory, up to 500 entries, for reuse for 24 hours. Expired entries are removed on later geocoding requests or restart. Precise website reverse-geocoding coordinates are not cached by this shared client.
• IP-based rate-limit entries use 60-second windows and are cleared on later requests or restart.
• MCP application logs record tool name, duration and error status, without query text, identifiers, tool results or chat contents. Existing reading composition can retain temporary public place-based state in memory. The connector does not publish readings or create contributor records.
• Hosting providers may retain infrastructure metadata and logs under their policies. Railway documents log retention by plan, from three to 90 days; this is not a promise that all provider records are deleted at that point. Open-Meteo states that its API webserver logs, which can include coordinates, are deleted after 90 days. Other upstream retention is governed by the linked provider policies. Orreria does not promise zero retention or deletion from every provider after 15 minutes.

Your choices and requests

Disable or remove the connector to stop new requests. Use named public places and omit private information. The connector has no account-linked reading archive to export or delete. For questions, correction, access or deletion requests, contact support@orreria.com. We will explain what records we can identify and address requests as applicable. Avoid emailing complete private conversations; a tool name, time and error code is usually sufficient for troubleshooting.

Separate interactions

Following a citation or visiting Orreria’s contribution pages creates a separate website interaction. Submitting local knowledge or contacting support may provide information outside this connector’s read-only workflow. These documentation pages contain no analytics scripts, tracking pixels or external fonts.