Glimind // privacy

Glimind is designed so that contributing data cannot leak your inputs.

From SDK telemetry we store ONLY:

• the tool / endpoint identifier
• a salted hash of the input shape (structure only) and an optional value-free skeleton
• success / failure
• a normalized, scrubbed error signature (emails, IPs, tokens, long strings removed)
• latency and timestamp
• an optional coarse region (e.g. us, eu)

We never store

• raw arguments or payloads
• tool outputs
• your reporter id in raw form (it is salted-hashed)

The ingest endpoint hard-rejects any field that resembles a raw payload. Shape skeletons are validated to contain only type tags. See the SDK README for the exact client-side derivation.

Probing

For servers we discover from public registries, we perform only the MCP initialize handshake and tools/list. We never invoke a tool. Probes carry a descriptive User-Agent linking here, honor a do-not-probe list, and are rate-limited. Opt out at https://glimind.com/opt-out.