TRUST & TRANSPARENCY UPDATED 17 NOV 2026

Privacy and data use.

MCP Foundry is an independent developer product in the Noetfield Systems Inc. portfolio. This notice explains the information our application collects, why it is used, and how to request deletion or correction.

Account and workspace

We collect the email address you register, a salted password hash, authentication session hashes, server and tool configuration, API-key hashes, and timestamped product-activation and usage events (such as server creation, test, publication and actual tool invocation). We use this information to operate your workspace, authenticate requests, enforce limits, and show observed tool-call results. API-key secrets are displayed once and not stored in plaintext by the Foundry application.

OAuth and connected providers

If you explicitly authorize a supported GitHub account, we store its OAuth access token and, when issued by GitHub, its refresh token encrypted using authenticated encryption bound to your Foundry account. Connection scope and expiration metadata are stored to manage your private API access. Tokens are not exposed in the web interface. A GitHub binding is permitted only for a private owner-authenticated MCP server whose tools access api.github.com. Disconnecting deletes stored tokens and disables bound endpoints; revoke the authorization separately in GitHub to invalidate any remote grants.

Teams, referrals and marketplace

When you use team invitations or referrals, we store account IDs, invited roles, approval states and observed referral activity. A public marketplace listing displays information you intentionally publish for a public MCP server, including its description, documented tool inventory and your self-supplied listing details. Marketplace participation is not represented as independent identity verification.

Developer and partnership enquiries

When you submit a collaboration proposal, Foundry stores your chosen role, name, email, optional project or organization, public website or GitHub URL, the specific project brief, source category you submitted from, and contact consent. Updates consent is optional and independent. This record is visible to authorized Foundry operators for evaluating and following up on that request. A submitted proposal is not a contract, employment decision, paid commission, investment opportunity or accepted partnership. To request review or deletion, contact us from the same email using the implementation enquiry channel.

Implementation enquiries

When you request a paid MCP implementation proposal, we store the name, email, company, optional website, project details, and your contact consent. This information is used to respond to that request. Product updates are optional and require a separate marketing consent checkbox. Sending a request does not place an order or create a payment.

Upstream API calls

Tools you publish can request third-party HTTPS endpoints. Arguments and the API request are sent to the upstream provider when you test or invoke that tool. Foundry records tool names, timestamps, duration and success/failure status to measure service operation. Never place credentials or private values into a public URL or GET query parameter.

Hosting, payments and third parties

Application data is hosted in PostgreSQL on Railway. A separately scoped one-time public API Quickstart can be purchased through a live Stripe-hosted Payment Link; Stripe processes the payment details and billing address, not the Foundry web form. Recurring Pro subscriptions are not configured; implementation and collaboration forms do not charge users. Merchant tax settings and actual payment receipts must be verified in Stripe. The site loads web fonts from Google Fonts. Third-party service providers process information under their own policies. We do not present unverified security certifications or promise data-residency arrangements not established in a customer agreement.

Your choices

You may revoke personal API keys from Studio. You can request account deletion through the authenticated account API or request assistance through the contact form. To request review or deletion of an enquiry, submit the request through the implementation contact form, using the same email and describing your request. We retain records as needed for service operation, legitimate business obligations, and request handling, and periodically review whether they remain necessary.

Session cookie

Foundry uses a same-site, HttpOnly session cookie to maintain signed-in browser access. The cookie is configured as Secure in production. We do not use a public-facing advertising-tracking cookie in this application.