Website Cookbook connector privacy
Effective October 22, 2026. FidelicAI, a DBA of Memetica Corp.
This notice covers the published Small Business Website Cookbook at mcp.fidelic.ai/mcp, and these documentation pages. It supplements the FidelicAI privacy policy.
What is processed
Your AI sends bounded requests such as a short search, guidance identifier, section or edition. The application processes these in memory to return published expertise. It does not store request bodies, tool arguments, conversation histories, customer projects or session records. No customer account, payment information, website credentials or private uploads are required.
Operations and hosting
During the hosting transition, Railway and Vercel provide the service infrastructure. The provider handling a request maintains standard operational HTTP and application logs. Application usage events contain fixed operation labels, such as initialization or a named tool call, without search text, document contents, request bodies, authorization headers or customer identifiers. In-memory IP-based rate limiting protects each application instance; Vercel deployments also require an edge rate-limit rule that uses source IP and maintains regional counters. These protections are not a single global request quota. The connector has no advertising or analytics cookies.
Operational log retention follows the handling provider’s service settings and the main FidelicAI privacy policy. This notice does not claim that infrastructure logs contain no network metadata or that both providers have identical retention. No additional customer-work database or session store is used by the cookbook.
On Vercel, access is restricted by estimated source-IP location to the contiguous United States, including Washington, DC. Health and readiness probes are exempt. A hosted AI connects from its provider’s server IP; that location may differ from the owner’s. Unknown locations are blocked. Denied requests produce operational security logs containing the source IP, estimated country and state, host, path, method, user agent, timestamp, request identifier and blocking reason. These application records exclude query strings, request bodies, tool arguments, cookies and authentication headers. They support analysis of access restrictions and unwanted traffic. Standard Vercel Pro runtime logs are retained for one day; no separate blocked-IP archive is maintained.
On Railway, when enabled, a successful initialization can send FidelicAI a content-free operator notice through Resend containing a fixed event label and server time. No request text, caller identity or network metadata is included in the notice. A temporary one-way source digest suppresses repeat notices in memory. This optional email channel is disabled in the Vercel application entry point.
Your AI platform
The AI provider processes the conversation and tool responses under its own terms and settings. FidelicAI does not control that provider’s retention or training practices. Copyright and permitted-use notices do not technically prevent model training or authenticate agreement acceptance.
Keep private material in your workspace
Ask for the relevant method using minimal context. Keep credentials, personal customer details and private audit evidence in the owner-controlled environment. The service neither connects to your business accounts nor publishes changes. A website’s own separate connection has its own data handling and permissions.
Contact hello@fidelic.ai for privacy questions or concerns. Return to cookbook setup.