Privacy Policy
Effective date: 19 September 2026 · Last updated: 19 September 2026
This policy explains how Keith Peters ("we", "us") handles information when you use God Mode MCP (the "Service"), including information obtained from Google APIs.
1. Information we access
When you connect a Google Cloud project to the Service, you authorize us — through Google's own OAuth consent screen — to read configuration metadata about that project. In particular:
| We read | Why |
|---|---|
| List of enabled Google Cloud services and their versions | To determine which capabilities your project can reach |
| Project IAM policy bindings (roles and members) | To configure the correct, least-privilege access for your generated server |
| Your Google account email address | To identify the authorizing account |
We do not request or store your Google password. We do not read the contents of your files, mail, messages, or databases.
2. How we use it
- To generate and configure your God Mode MCP server package.
- To show you which capabilities are available in your project.
- To operate, secure, and support the Service.
We do not sell your information. We do not use Google user data for advertising. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
3. What we store, and for how long
- Access tokens — held in memory for the duration of setup, then discarded. We do not store long-lived refresh tokens.
- Capability snapshot — the list of enabled services, retained while your account is active so we can regenerate your server.
- Project identifiers — project ID and the authorization reference, retained so you can re-run setup.
Delete your account, or ask us to, and we delete the snapshot and identifiers within 30 days.
4. Sharing
We share information only with service providers that host and operate the Service on our behalf, and only as needed to run it; or where required by law. We do not share Google user data with third parties for their own purposes.
5. Security
Access is read-only and scoped to the minimum required. Credentials are never written to logs. Tokens are short-lived and transmitted over encrypted connections.
6. Your choices
- Revoke access at any time from your Google Account permissions page or your project's IAM settings.
- Request deletion of stored data by emailing us.
- Ask questions about what we hold.
7. Changes
We will post any changes on this page and update the "Last updated" date above.
8. Contact
Email: rogue-rf@protonmail.com