Privacy policy

Human Atlas is maintained by Christian Tzurcanu. This policy covers the Human Atlas MCP tools and the linked anatomy viewer.

MCP requests

The tools receive the anatomical search terms and view settings sent by your MCP client, such as a model, selected structures, layers and camera settings. These inputs are used to search the public catalogue and generate a viewer URL. The MCP handler processes inputs for the duration of the request and does not write them to a Human Atlas database or maintain a search history. It does not request your full conversation, patient records, payment details, credentials or government identifiers. Please do not include such information in tool inputs.

Hosting and recipients

Cloudflare hosts the MCP endpoint and optional live-session relay. GitHub Pages hosts the viewer and its public assets. These providers handle network requests and may process IP addresses, request URLs, browser information and operational or security logs under their own policies. Human Atlas does not specify the providers' independent log-retention periods. ChatGPT or another MCP client processes your conversation and tool calls under that client's own policies. Tool-generated viewer URLs contain the requested anatomical selections and view settings.

Viewer and browser storage

The viewer stores downloaded public anatomy assets in IndexedDB and uses localStorage for saved views and preferences. These remain on your device until you remove them, clear site data, or the browser evicts the cache. Asset caching is limited to 512 MiB. Adding ?rc=1 to the viewer address clears the anatomy cache; it does not clear saved views or preferences. Clearing all browser site data removes those too. The viewer can request anatomical descriptions from Wikipedia, sending the structure name and ordinary network request information to Wikimedia. If you open external references, the destination handles that visit under its own policy. Custom hierarchy URLs are fetched only when supplied for that view.

Website analytics

The GitHub Pages website uses PostHog to measure page visits and interface interactions. Analytics can include page addresses and referrers, browser and device information, and a pseudonymous browser identifier stored in cookies or browser storage. Viewer addresses may include anatomical selections and view settings. Analytics is sent to our PostHog US Cloud project. The integration uses identified-only person profiles and does not identify visitors through a Human Atlas account. Local development copies do not send analytics through this integration. See PostHog's privacy policy for information about its processing.

Optional Host/Guest sessions

If you use the viewer's Connect feature, Cloudflare's relay processes a random session code, participant IP addresses, participant names and the shared anatomy state and camera. Participant names and addresses may be shown to people in the session. State is stored to support reconnection. Stopping a broadcast clears the shared view and camera; room metadata is retained while the host keeps the lobby. After the host has been disconnected for 60 seconds, the relay expires the room and deletes its stored state. This feature is separate from stateless MCP searches.

Support and controls

Use GitHub Issues for support and privacy questions. Issues and their attachments are public and retained until removed through GitHub; do not post private information. You can remove the Human Atlas connection in your MCP client, stop a live session, and clear browser site data. Human Atlas does not implement advertising, sell personal data, or use anatomy requests to train its own models.