What Epicure processes
When your MCP client calls a tool, Epicure processes the ingredient names, filters, and other parameters in memory to produce a deterministic result from the bundled flavour model. Epicure has no MCP accounts, cookies, advertising profiles, or conversation database.
Tool arguments, ingredient queries, result content, prompts, chat history, uploaded files, credentials, and raw IP addresses are never written to Epicure application logs.
Minimal operational telemetry
- Timestamp and MCP tool name
- Response size and processing latency
- Success state or exception class
- A 16-character client-IP hash whose random salt rotates at UTC midnight
This telemetry operates the service, diagnoses failures, measures latency, and limits abuse. It is not used for advertising, user profiling, or model training.
Retention
Telemetry stays in a local rolling container log capped at two 2 MiB files. Old records are overwritten on rotation and are not forwarded to a long-term analytics store. Because the random hash salt rotates daily and is not separately retained, KAIKAKU cannot link hashes across salt rotations.
Infrastructure and sharing
Cloudflare provides DNS, TLS termination, DDoS protection, rate limiting, and the outbound tunnel to KAIKAKU's local compute. Cloudflare may process network metadata under its privacy policy. The MCP application does not send tool inputs to Google, OpenRouter, Anthropic, or another model provider. KAIKAKU does not sell MCP data or share it with advertisers or data brokers.
Your choices
Disable or remove the connector to stop future processing. Epicure normally cannot associate telemetry with a named person, but privacy questions and rights requests can be sent to [email protected].
For the complete repository policy and change history, read the versioned privacy policy.