Last updated: January 2026
Peta is the control plane for MCP: secure vault, managed runtime, and policy-based approvals. These Terms explain how you may use Peta Core, Console, and Desk.
Peta Core, Console, and Desk run in environments you control. Your MCP configs, policies, approvals, and runtime data stay on the servers you deploy and are not sent to Peta without your explicit permission. Secrets (passwords, credentials, API keys) remain encrypted in your Vault-backed storage; we cannot decrypt them.
We only hold the account and payment details you provide for purchasing a commercial license. Those billing records are separate from any MCP configuration or usage data.
You must provide accurate account information and keep credentials secure.
Agents and users authenticate with short-lived Peta tokens. You are responsible for access granted to your users, agents, and workspaces.
Do not misuse Peta or attempt to bypass security controls. Specifically:
External credentials stay encrypted in Vault-backed storage. Peta injects secrets into MCP tools server-side and issues short-lived tokens instead of sharing raw API keys.
Every agent action is evaluated against policies and, when required, human approvals in Peta Desk. Audit logs stay in your deployment; Peta does not receive them unless you explicitly share them for support.
We aim for high availability of Peta Core, Console, and Desk but do not guarantee uninterrupted service. Support channels and SLAs may vary by plan.
Paid plans are billed per the pricing you select. Fees are non-refundable unless required by law. You may cancel at any time; access continues through the current billing period.
We may suspend or terminate access for policy violations, security risk, or non-payment. You may terminate by ceasing use and closing your account.
Peta is provided "as is" without warranties of any kind. To the fullest extent permitted by law, our liability is limited to fees paid for the applicable service period.
Questions about these Terms? Email legal@peta.io.