These documents are visually finished but carry placeholders where actual company and legal details are required. Nothing here is final until reviewed by counsel.
This policy describes how [LEGAL ENTITY NAME] handles information in connection with mcpseal.
Applies to the mcpseal CLI (Track A) and the mcpseal Control Plane (Track B).
Track A runs on your machine. It reads your MCP client configuration and tool definitions to build .mcp-lock.json, and writes local event history to ~/.mcpseal/events.jsonl. None of this is transmitted anywhere by default.
Running mcpseal login connects your machine to a hosted workspace. From that point, fleet and integrity-event metadata associated with your account is processed by the Control Plane. Prompts, tool arguments, and tool results are not intentionally collected.
Prompt content, tool-call arguments, tool-call results, or the contents of files your MCP servers operate on.
Local files remain on your machine under your control. Workspace data is retained per [RETENTION POLICY — TBD]. Workspace credentials are stored in the OS keychain, not in plaintext.
Track B relies on infrastructure providers including [THIRD-PARTY SERVICE PROVIDERS — TBD] for authentication and billing.
Details depend on [JURISDICTION] and will be specified once the legal entity and registered address are finalized.
Privacy inquiries: [PRIVACY CONTACT]. Effective date: [EFFECTIVE DATE].
These terms govern use of mcpseal, a product of [LEGAL ENTITY NAME] ("Kadin Labs").
The mcpseal CLI is provided free of charge for local use, subject to its open-source license — see License below.
Access to the Control Plane requires a workspace account and is subject to any applicable subscription terms, billed through Stripe.
You are responsible for evaluating whether a changed MCP tool should be trusted; mcpseal blocks drift, it does not make that judgment for you. Third-party MCP servers remain third-party dependencies outside our control.
mcpseal is provided "as is." Liability terms, indemnification, and governing law are [GOVERNING LAW — TBD] pending legal review — nothing here should be treated as finalized.
We may update these terms; material changes will be noted here. Contact: [LEGAL CONTACT].
mcpseal is a security control designed to detect MCP tool-definition drift. It does not guarantee protection against every attack.
Users remain responsible for deciding whether a changed tool should be trusted. MCP servers and other third-party software remain third-party dependencies, and compatibility can vary by client and configuration format.
Track A is local-first; workspace connectivity through Track B is opt-in. Roadmap items described elsewhere on this site are directions under consideration, not guaranteed release commitments.
mcpseal's software license is [LICENSE NAME], pending confirmation against the published repository.
mcpseal bundles or depends on third-party open-source packages, each under its own license, listed in the repository's dependency manifest.
Unless noted otherwise, this site's documentation is [DOCUMENTATION LICENSE — TBD].