MCPGoose
Privacy information
Clerk handles account sign-in. The hosting control plane stores account ownership, deployment configuration, usage records and encrypted instance environment values. Hosted code and dependencies are retained separately from temporary runtime files. If connected, GitHub access credentials are encrypted in the control plane. Optional notification delivery stores encrypted destinations and delivery status; email uses your verified primary Clerk address.
MCPGoose stores OAuth grant metadata and token verifiers for client access and revocation. The client receives access credentials through OAuth authorization; deployment secrets remain server-side and are not stored in browser storage.
Hosting actions contact the control API and its configured cloud services. External repository and documentation links open their respective sites. These notes describe the personal pilot and are not a complete privacy policy for a public commercial service.