Subprocessors
Last reviewed 2026-10-17
These are the services that store or receive data from Sightlog or its visitors, as of the review date above. Sightlog’s servers do not send user content to any AI provider. To ask a question: terjetyl@gmail.com.
| Service | Purpose | Based | Data |
|---|---|---|---|
| Hetzner (servers) | Runs the web app, API and PostgreSQL database | Germany | Account details, observations incl. coordinates and notes, connected-account tokens, server logs |
| Hetzner Object Storage | Stores uploaded photos (publicly readable) | Germany (endpoint: nbg1) | Photo files as uploaded, including embedded metadata |
| FjordID (self-operated) | Sign-in / identity | Operated by Sightlog’s maintainer | Email, name, login credentials and session data |
| iNaturalist | Optional account connection, publishing, nearby sightings | US | Your iNaturalist id and username; for publishing: species, time, coordinates, place name, notes; for the feed: search coordinates and radius; for species search in the browser: typed search text, IP address and browser details |
| eBird (Cornell Lab of Ornithology) | Nearby bird sightings in the feed | US | Search coordinates and radius |
| Artsdatabanken (Artskart) | Nearby records in the feed | Norway | Search coordinates and radius |
| OpenStreetMap Foundation (tiles, Nominatim) | Map tiles and place-name lookup in the browser | UK | IP address; coordinates you click or your device position (Nominatim) |
| GitHub | Hosts source code, builds and deploys the app | US | No user data; holds deployment secrets |
Services marked US are outside the EU. Some of these (iNaturalist, eBird, Artskart, OpenStreetMap) receive data directly from your browser or when you use a feature, rather than being contracted processors. Fonts and map marker images are served from sightlog.eu itself. We have not verified data processing agreements with every provider.
Your own MCP / AI client (not a Sightlog vendor). If you create an API key and connect an MCP client such as Claude or another AI assistant to Sightlog’s MCP server, that client receives whatever the tools return, which can include your sightings, locations, notes, photos, field notes and profile details. This happens only because you set it up with your own key, and the client and its provider are your choice, not a Sightlog subprocessor. Sightlog has no agreement with them and does not send data to them. See privacy.