WhiteMagic hosted lane — terms & privacy

Applies to mcp.whitemagic.dev (hosted recall service). Last updated 2026-10-02. The self-hosted MIT product is unaffected by these terms. See the current Terms and Privacy Policy.

What this service is

• A read-only recall lane over a curated public corpus. It answers search/recall queries; it cannot write to any store and holds no personal memory.
• Access may use an evaluation key, an anonymous trial, OAuth, or a metered request, depending on the route and access method. Rate limits apply.
• No SLA. Best-effort evaluation infrastructure: it may change, throttle, or be withdrawn at any time.

Acceptable use

• Use it to evaluate WhiteMagic, build integrations, and test agents.
• Do not attempt to bypass authentication, caps, or the read-only boundary; do not scrape at volume; do not use it to process personal or confidential data. Keys that abuse the lane are revoked.
• Outputs are provided as-is, without warranty of any kind.

Data & privacy

• The gateway processes request content to answer recall queries and does not add submitted queries to its curated corpus. Audit entries can include key name, timestamp, HTTP method and status, byte count, normalized route, JSON-RPC method and tool name, client family, bounded User-Agent family, latency, and decision details. Tool arguments, query text, response content, bearer tokens, and raw User-Agent strings are not written to these entries. An unrecognized non-empty User-Agent is represented by a truncated SHA-256 fingerprint.
• The anonymous trial uses client IP in a per-day in-memory counter. The faucet uses IP and an optional payer/address identifier for daily anti-abuse limits; selected faucet audit entries include those values in persistent gateway logs. There are no cookies or cross-site profiling identifiers.
• Operational tool-call spans are sent to Glimind: bounded tool name, HTTP status, latency, service labels, and error class. Arguments, results, payloads, tokens, keys, and IP addresses are excluded. Glimind's handling is subject to its own privacy terms.
• Gateway audit logs have a 90-day retention target under periodic rotation; old archives may not expire immediately. Backups of the hosted store and durable authorization state retain up to four weekly remote and twelve weekly local copies; service records removed from active storage may remain in those backups. Audit logs are excluded from that backup set. Replay nonces are retained through assertion expiry plus the clock-skew allowance. Other durable state, including owner mappings, service signing keys, receipts, and crystal ciphertext, has no general expiry schedule. The in-memory counters follow service process lifecycle; do not treat this as a deletion guarantee.
• Evaluation keys are bearer tokens, not identities. Ask us to revoke a key at any time.
• The curated corpus is public documentation and public-domain material; nothing you send is added to it.

Contact

Questions, key requests, or data requests: whitemagic.dev/contact or lbailey94@protonmail.com.