Privacy Policy

This Policy covers mcpip.ai, the MCPIP software we publish, the entitlement licenses we issue, MCPIP Managed Cloud, and our correspondence with you. Our role differs by context, and the difference is not cosmetic:

• Self-hosted deployments — you are the controller of everything your gateway processes. We are neither controller nor processor of it, because it never reaches us. See section 2.
• Managed Cloud — for the content you route through a hosted gateway, you are the controller and we act as your processor under a data processing addendum. For your account and billing records we are the controller. See section 3.
• Website visitors and prospects — we are the controller. See section 4.

The controller for the processing described in this Policy is MCPIP INC, Delaware, USA. Contact: privacy@mcpip.ai.

Your runtime never reaches us.When you run the gateway inside your own perimeter, your agents' traffic, tool-call payloads, arguments, aliases, targets, compartments, identities, keys, secrets, and your audit chain stay in your perimeter. We do not receive, store, process, or have any means of accessing them. Identity is sovereign to your identity provider: the gateway verifies the tokens your IdP issues and never mints identity, and those tokens do not flow to us.

That is an architectural property, not a promise of good behavior — but it should be stated precisely rather than absolutely. Exactly two vendor-facing channels exist in the software, and both terminate at mcpip.ai. Both are off by default and both are enabled only by your own configuration.

(a) The telemetry beacon — opt-in, off by default. Enabled only if you configure a telemetry URL. When enabled it posts a closed payload of exactly eight fields, and nothing else:

• install_id — a random value generated once and stored locally. It is not derived from any tenant, host, customer, or license identity.
• license_tier— your tier, or 'unlicensed'.
• license_id — the identifier of the entitlement license, or null.
• version — the gateway version string.
• governed_agent_identity_count — one integer. It is a cardinality sketch: agent identifiers are folded into a probabilistic register and are never stored in a readable set, so only the count can ever be read back.
• decisions — three integers: allow, deny, staged.
• uptime_seconds — one integer.
• sent_at — a timestamp.

A signature and a timestamp travel as HTTP headers, never inside the body. The payload carries no tenant id, agent id, alias, target, capability, compartment, correlation id, secret, payload, or argument, and no per-tenant breakdown. Our receiving endpoint stores the body and those two headers and nothing else — it does not record the sending IP address, set a cookie, or fingerprint the sender. In air-gapped mode the beacon is structurally impossible: it is only constructed when telemetry is explicitly enabled with a URL, and an air-gapped deployment has no outbound path for it to use.

(b) The entitlement refresher — opt-in, off by default. Enabled only if you configure a license-refresh URL. It runs off the authorization hot path, fetches a candidate signed entitlement license, and verifies it against the existing license root before adopting it. Its request reports usage in the same round trip: either the same closed beacon payload above, or — where the beacon is not wired — a minimal subset of that same closed set: the license id and version, plus the install id only if the beacon has already generated one. It never carries a tenant, agent, alias, target, capability, correlation id, secret, or argument, and it is likewise absent in air-gapped deployments.

Both channels are best-effort side channels that cannot block, delay, reorder, or change an authorization decision, and neither can be used to reconstruct who did what.

MCPIP Managed Cloud is an Early Access hosted offering in which we run the control plane for you.

Controller / processor split. For personal data contained in the traffic you route through a hosted gateway, you are the controller and we act as your processor: we process it only on your documented instructions, to provide the service, and we do not use it for our own purposes. For your account, billing, and license records we are the controller, as described in section 5.

Data processing addendum. Our DPA — incorporating the EU Standard Contractual Clauses, the UK International Data Transfer Addendum, and the Swiss addendum, together with the sub-processor list in section 7 — is available on request from privacy@mcpip.ai and forms part of your agreement once executed. If you are subject to the GDPR, the UK GDPR, or a US state privacy law and you use a hosted offering, you should have it in place.

We do not train on your data. We do not use content you route through a hosted gateway to train, fine-tune, or evaluate any model, and we do not sell it or share it for advertising.

Deletion and export. After termination you have thirty (30) days to request an export of the account data we hold, including your signed audit-chain records; after that window we delete or irreversibly anonymize it within a further thirty (30) days, except for encrypted backups on their ordinary rotation (up to ninety (90) days) and records we must retain by law. This mirrors the termination mechanics in our Terms of Service.

For everyone who visits mcpip.ai, MCPIP INC is the controller. The site is deliberately thin: it has no advertising, no third-party analytics, no cross-site tracking, no data brokers, and no advertising identifiers. What it does have is listed in full in section 5, and the four cookies and storage keys it can set are listed in full in section 6.

Two collections deserve to be called out rather than buried, because they are the two where you type or reveal something:

• The Ask-AI assistant. Every question you submit is stored verbatim, together with your IP address, and is sent to Cloudflare Workers AI to generate the answer. The IP address is what makes the daily question limit work. The answer is not stored. Please do not put personal, confidential, or regulated information into the assistant.
• The access-request and early-access forms. We store exactly what you type, plus a server timestamp — no IP address and no cookie.

Every category of personal data we hold is in this table. If it is not here, we do not collect it.

What we never collect.For self-hosted deployments we do not collect your agents' data, prompts, or tool-call payloads; the contents of the systems the gateway authorizes; your audit chain or WORM log; or your identities, keys, or secrets. Across the whole site we collect no biometric data, no precise geolocation, no government identifiers, and no special-category or 'sensitive' personal information as those terms are used in the GDPR and the CCPA.

Retention periods are maximums. Where a shorter period suffices, we delete sooner, and we may keep records longer where a legal claim, investigation, or statutory obligation requires it — in which case we keep only what that purpose needs.

This is the complete list. There is no other cookie, pixel, tag, beacon, SDK, or fingerprinting script on this site.

The favorable facts, stated plainly. There are no advertising cookies, no third-party analytics, no cross-site or cross-context tracking, and no fingerprinting. Page analytics record a route family and a date and nothing else — not your IP address, user agent, or referrer. The two localStorage keys are written by your browser, hold no identifier, and are never read by our server; they exist to stop double-counting and to let a visit be excluded entirely. We treat both as strictly necessary first-party storage under the ePrivacy Directive; where local law requires consent for any non-essential storage, we will ask for it before setting it.

Do Not Track is honored. If your browser sends DNT: 1, the page-view beacon does not fire at all — nothing is sent and nothing is recorded. Many sites say DNT is meaningless because there is no standard; we simply obey it.

Global Privacy Control. We recognize the Global Privacy Control (GPC) signal as a valid opt-out request under the CPRA and comparable US state laws. We do not sell or share personal information and we run no cross-context behavioral advertising, so there is nothing for a GPC signal to switch off — but we will honor it as an opt-out of any sale or sharing should that ever change, and we will not discriminate against you for sending it.

You can also block or delete cookies and clear site data through your browser settings. Blocking the account session cookie will prevent you from signing in to the Cloud portal; nothing else on the site depends on storage.

We do not sell your personal data, and we do not share it for cross-context behavioral advertising. We disclose it only to the service providers below, who process it on our behalf under written contracts with confidentiality, security, and use-limitation terms.

• Cloudflare, Inc. (United States, with a global edge) — the entire site runs here. Workers for hosting and delivery; D1 as the single database behind every table in section 5; Email Routing for inbound mail to our published addresses; and Workers AI, which receives every question submitted to the Ask-AI assistant and generates the answer. Questions are not sent to any model provider outside Cloudflare.
• Stripe, Inc. (United States) — payments, hosted checkout, the customer billing portal, subscription management, and invoicing. Stripe collects and holds your payment credentials directly; we never receive them. Stripe acts as an independent controller for its own payment-processing, fraud-prevention, and regulatory purposes.
• Resend, Inc. (United States) — transactional email delivery, used for magic-link sign-in messages.

That is the complete list. We use no third-party analytics service, no advertising network, no session-replay tool, and no customer-data platform.

We may also disclose personal data if we are legally compelled to do so (for example, in response to a valid legal request — which we will scrutinize and, where lawful and practical, notify you about), to establish or defend legal claims, to protect our rights, safety, or property, or in connection with a merger, acquisition, financing, or sale of assets, subject to appropriate confidentiality protections and to this Policy continuing to apply to the transferred data.

We publish material changes to this sub-processor list here before they take effect for hosted customers; customers under a DPA may object as that DPA provides.

MCPIP INC is established in Delaware, USA, and our sub-processors are US companies operating global infrastructure. Personal data of individuals in the European Economic Area, the United Kingdom, and Switzerland is therefore transferred to, and processed in, the United States and other countries.

Where such a transfer requires a safeguard, we rely on the following:

• EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) — Module 2 (controller to processor) where we act as your processor for a hosted offering or engage a sub-processor, and Module 4 (processor to controller) where we return personal data to a controller outside the EEA;
• the UK International Data Transfer Addendum (IDTA) to those Clauses, or the standalone UK IDTA, for transfers subject to the UK GDPR;
• the Swiss addendum for transfers subject to the Swiss Federal Act on Data Protection, reading the Clauses with the Swiss Federal Data Protection and Information Commissioner as the competent authority and extending protection to legal entities where Swiss law requires; and
• where a recipient participates in the EU-US Data Privacy Framework and its UK Extension or the Swiss-US Data Privacy Framework, that certification as an additional or alternative mechanism.

We carry out a transfer-impact assessment for each mechanism and apply supplementary measures: encryption in transit and at rest, strict data minimization (the analytics and beacon payloads are designed so there is little to transfer), and — for self-hosted deployments — an architecture in which the runtime data never leaves your jurisdiction at all. A copy of the relevant clauses is available from privacy@mcpip.ai.

Depending on where you live, you may have the rights to: access the personal data we hold about you and receive a copy; have inaccurate data corrected; have data deleted; restrict or object to processing, including processing based on legitimate interests and any direct marketing; receive your data in a portable format; withdraw a consent you gave, without affecting processing already carried out; and not be subject to a decision based solely on automated processing that produces legal or similarly significant effects (see section 11). Californian residents additionally have the rights described in section 10.

How to exercise them. Email privacy@mcpip.ai and tell us which right you are exercising. There is no charge, and we will not discriminate against you for asking.

Verification. We verify a request against the data we already hold — normally by asking you to send it from the email address associated with the record, or, for account holders, by having you sign in. If we cannot verify you to a reasonable degree of certainty we will say so and explain what would let us; we will not create an account or collect new identity documents merely to verify a request, and any information you give us for verification is used only for that purpose and then deleted.

Deadlines. Under the GDPR and UK GDPR we respond within one month, extendable by up to two further months for complex or numerous requests, with notice to you. Under US state privacy laws we acknowledge within ten (10) business days and respond within forty-five (45) calendar days, extendable once by a further forty-five days with notice.

Authorized agents. An authorized agent may submit a request on your behalf with written permission signed by you or a valid power of attorney. We may ask you to verify your own identity directly and to confirm that you authorized the agent, except where the agent holds a power of attorney.

Appeals. If we decline a request, our response will say why. You may appeal within sixty (60) daysby replying to that response with 'Appeal' in the subject line, or by writing to privacy@mcpip.ai. We will decide the appeal and give you a written explanation within forty-five (45) days. If we deny the appeal, we will tell you how to complain to your state Attorney General.

You also have the right to lodge a complaint with a supervisory authority — your local data-protection authority in the EEA, the Information Commissioner's Office in the UK, or the Federal Data Protection and Information Commissioner in Switzerland. We would appreciate the chance to resolve it first.

If you are a customer of a hosted offering and the request concerns data we process on your behalf as processor, we will refer the individual to you and assist you in responding, as the DPA requires.

In the twelve months before the date of this Policy, we have collected the following statutory categories of personal information, in each case only as described in section 5:

• Identifiers — name, work email address, IP address (Ask-AI log only), account email, Stripe customer and subscription identifiers, license identifiers.
• Commercial information — plan, purchased quantity, subscription status, and transaction records.
• Internet or other electronic network activity — the route family and date of a page view, and the text of questions you submit to the assistant.
• Professional or employment-related information — company, industry, fleet size, and tier of interest, as you provide them on a form.
• Inferences — none. We build no profiles and draw no inferences about you.
• Sensitive personal information — none. We do not collect it, and therefore there is nothing to limit the use of.

Sources: directly from you (forms, the assistant, email, checkout); automatically from your device (page path and date); and from Stripe (billing and subscription status).

Business purposes: providing and securing the site and services; responding to enquiries; billing, fraud prevention, and audit; abuse prevention and rate limiting; product improvement; and legal compliance.

Disclosures for a business purpose: to the service providers named in section 7 (Cloudflare, Stripe, Resend), each of which is a service provider or contractor under the CCPA and is prohibited from retaining, using, or disclosing the information for any purpose other than performing the service.

We do not sell or share personal information, as 'sell' and 'share' are defined in the CCPA, and we have not done so in the preceding twelve months. We do not sell or share the personal information of consumers we know to be under sixteen. We do not use or disclose sensitive personal information for purposes requiring a right to limit.

Californian residents may exercise the rights to know, access, delete, correct, opt out of sale or sharing, limit the use of sensitive personal information, and not be discriminated against, by the process in section 9. Residents of other US states with comparable laws — including Virginia, Colorado, Connecticut, Utah, and Texas — may use the same process, including the appeal route.

We do not use personal data for automated decision-making that produces legal or similarly significant effects about you, and we do not profile you.

The site's Ask-AI assistant runs on Cloudflare Workers AI over a fixed knowledge document about MCPIP. It answers questions; it makes no decision about you, evaluates nothing about you, and does not personalize its answers using anything other than the question you just typed. Its answers are generated automatically and may be inaccurate, incomplete, or out of date; they are not advice and must not be relied on. Questions are logged as described in section 5.

The only automated rule that affects you is the per-IP daily question limit on the assistant, which exists to prevent abuse of an unauthenticated endpoint and has no legal or similarly significant effect.

We apply technical and organizational measures proportionate to the very small amount of personal data we hold, including:

• TLS for all traffic to and from the site, and encryption at rest at the platform layer;
• signed, HttpOnly, Secure, SameSite session cookies with constant-time verification, and purpose-tagged sign-in tokens that expire in fifteen minutes so a leaked link cannot be replayed as a session;
• Stripe webhook signatures verified over the raw request body before any write, so the billing store cannot be written by an unauthenticated caller;
• secrets held as platform secrets, never in the client bundle and never in source control; administrative surfaces fail closed and are disabled entirely unless explicitly configured;
• data minimization as a design rule — no payment credentials on our systems, no IP addresses in page analytics, no answers stored from the assistant; and
• least-privilege access to the database, limited to those who need it.

No system is perfectly secure, and we cannot guarantee absolute security. You are responsible for keeping your own credentials and your communications with us secure.

Breach notification. If we become aware of a personal-data breach, we will notify the competent supervisory authority without undue delay and, where feasible, within seventy-two (72) hours of becoming aware of it where the GDPR or UK GDPR requires, and we will notify affected individuals without undue delay where the breach is likely to result in a high risk to their rights and freedoms. Where we act as processor for a hosted customer, we will notify that customer without undue delay after becoming aware, with the information they need to meet their own obligations. Report a suspected vulnerability or incident to security@mcpip.ai.

The website and our services are directed to businesses and professionals, not to children. We do not knowingly collect personal data from anyone under 16 (or under 18 where applicable law sets that threshold), and we do not knowingly sell or share the personal information of anyone under 16. If you believe a child has provided us personal data, contact privacy@mcpip.ai and we will delete it.

MCPIP INC has no establishment in the European Union, the United Kingdom, or Switzerland. Our offering is directed at organizations rather than consumers, and we do not monitor the behavior of individuals in those territories: we run no advertising, no cross-site tracking, and no profiling, and our page analytics record only a route family and a date. On that basis we have not appointed a representative under Article 27 of the GDPR or UK GDPR.

If our processing changes so that Article 27 applies, we will appoint a representative and publish its name and address in this section. In the meantime, individuals in the EEA, the UK, and Switzerland may contact us directly at privacy@mcpip.ai, and we will not object to a communication on the ground that no representative has been appointed.

We may update this Privacy Policy. If we make material changes — including adding a category of collection, a purpose, or a sub-processor — we will update the 'Last revised' date above and, where required, provide additional notice or seek your consent. We will not apply a materially different use to personal data already collected without a lawful basis for doing so. Your continued use of the website after a change takes effect indicates your acceptance of the updated Policy.

Questions, data-subject requests, appeals, and DPA requests may be sent to privacy@mcpip.ai. Security reports go to security@mcpip.ai, and contractual matters to legal@mcpip.ai.

MCPIP INC, Delaware, USA — privacy@mcpip.ai
Controller: MCPIP INC · Governing law: Delaware, USA

These documents state our commercial and privacy terms; they are not legal advice, and we recommend you have your own counsel review them before relying on them.