Privacy + Credentials
Privacy, credentials, and local runtime FAQ
SEO Dungeon is designed so the website can explain the model plainly: the game talks to a local bridge, and the bridge talks to user-owned local CLI runtimes and optional API integrations.
Last verified: June 18, 2026
- Model access
- User-owned CLI auth
- Bridge
- Local WebSocket server
- Commits
- Manual review
- SEO APIs
- Optional env credentials
Credential model
SEO Dungeon does not proxy, resell, or store model-provider access. Users authenticate their own local CLI runtimes and optional SEO data APIs.
- Codex, Claude Code, and Gemini CLI authenticate through their own local tooling.
- Google APIs, DataForSEO, Firecrawl, and other SEO data providers are optional.
- The browser interface should never need raw model-provider or SEO API secrets.
What the bridge can see
The bridge receives the active SEO issue, command, and user prompt. It launches a local CLI process and streams output back to the Guild Ledger so the work remains visible.
What happens to code edits
Accepted fixes are still working-tree edits. SEO Dungeon does not auto-commit or auto-push changes. Teams keep their normal review, test, and deployment gates.
FAQ
Does SEO Dungeon store my API keys?
No. The website should describe API keys as local environment or CLI credentials owned by the user. Optional integrations consume those credentials only when installed and invoked.
Does the browser game call hosted model APIs?
No. The browser game talks to a local bridge. The bridge spawns the selected local CLI runtime, such as Codex by default, Claude Code, or Gemini CLI.
Can SEO Dungeon change files?
Yes, through the selected local runtime. Those changes remain in the working tree for review, testing, commit, and deployment under the user's control.