Privacy · Docs MCP
Public documentation in; no customer records out.
The Accordo Docs MCP is a read-only knowledge surface for this framework. It serves the same public documentation, capability ledger and CRM job catalogue already available on this site and in the public repository. It is separate from the project MCP and cannot open an application database or change CRM state.
What a request contains
A client sends a JSON-RPC method and, for a tool call, a documentation query, capability identifier or CRM job question. Normal HTTP metadata also reaches the hosting platform, including an IP address, user agent, request time and routing headers. Do not put customer records, credentials, secrets or other personal data into a documentation query: the server neither needs nor asks for them.
What the Accordo application code stores
Nothing. The Docs MCP has no database, account, cookie, analytics SDK or write tool. Its application code processes a request in memory and returns public documentation. It does not intentionally persist request bodies, tool arguments, document excerpts or client metadata. Operational logs record only the HTTP method, response status and duration; they do not record the request body or query.
Hosting and retention boundary
The endpoint runs on Vercel. Vercel may process and retain ordinary infrastructure, security and function-log metadata under its own service terms and published privacy policy at vercel.com/legal/privacy-policy. Accordo does not add a separate telemetry or advertising system, does not sell request data and does not use Docs MCP requests to train a model. Infrastructure retention is controlled by the hosting account and platform, not by the read-only MCP code.
Sharing and subprocessors
The application code calls no third-party API while answering. Request traffic is handled by Vercel as the hosting provider. No CRM provider, model provider, enrichment provider or customer system is contacted by a Docs MCP tool call.
Your controls
You can use the same documentation without the remote MCP through llms.txt, llms-full.txt, the claims ledger and the public repository. Remove the MCP endpoint from your client to stop sending it requests. For a question or deletion request concerning hosting logs, open a private security report through the repository's security policy; the maintainer can determine what the hosting account actually retains rather than promising deletion of data the application never stored.
Changes to this notice
This notice is versioned with the source. A change that adds authentication, persistence, telemetry, a non-public resource or a write tool must update this page and pass review before deployment. Last substantive update: 9 August 2026.