How we handle data across our websites, MCP endpoints, and open-source projects.
We collect as little data as possible and never retain or train on source code submitted for verification. This page explains what information is processed when you visit thunderbearstudios.dev, connect your editor to resonantexo.com, or play angband3d.com.
Minimal telemetry and local-first game saves
Static Websites (thunderbearstudios.dev & resonantexo.com): Our informational pages are served through Cloudflare Pages and Workers. We do not use third-party advertising trackers, behavioral profiling cookies, or cross-site marketing pixels. Standard edge network metadata (such as client IP address and request timestamp) is processed transiently for basic delivery, rate limiting, and abuse prevention.
Angband 3D (angband3d.com): Dungeon save states, character sheets, and audio/visual preferences are stored locally in your own browser via localStorage and IndexedDB. When optional cloud features (such as AI Dungeon Master narration or cloud high-score leaderboards) are used, request payloads are rate-limited and processed transiently without selling or sharing personal data with third parties.
Direct Correspondence: If you email founder@thunderbearstudios.dev or dev@thunderbearstudios.dev, we use your contact details solely to reply to your inquiry or provision requested evaluation keys.
Your source code is not persisted to disk or used for model training
Transient In-Memory Code Verification (resonant_verify_cegar, resonant_architect_orient, resonant_honesty_audit, resonant_ci_gate): Source code snippets passed to our public or pilot MCP endpoints are parsed transiently in isolated memory solely to compute AST contracts, boundary bytecode counterexamples, or OASIS SARIF v2.1.0 reports. Submitted source code bodies are discarded upon returning the HTTP response and are not persisted to disk, stored in application telemetry, shared with third parties, or used to train any machine learning or AI model.
AST-Fingerprinted Belief Memory (resonant_memory_jtms): When you explicitly invoke resonant_memory_jtms with action="commit", only the normalized 16-character SHA-256 structural hash of the target function’s AST and your short architectural rule statement (subject, predicate, object) are stored—never the raw source code body.
Sandbox vs. Pilot vs. Local Isolation: Anonymous public sandbox calls (50 calls/day per IP) use an isolated, bounded ephemeral /tmp SQLite slot keyed by a one-way SHA-256 hash of the client IP. VIP Pilot Key holders (X-Resonant-Key: rk_pilot_...) receive a dedicated per-tenant SQLite database that can be purged on request at any time. Users of the Local & CI/CD Edition execute 100% offline on their own workstation or runner with zero external network calls.
Licensing, attribution, and studio status
GPL-2.0 Attribution (Angband 3D): Angband 3D is an open-source derivative of the classic Angband dungeon crawler and is distributed under the GNU General Public License v2.0 (GPL-2.0). Complete source code and upstream credits are available at github.com/ThunderbearStudios/angband3d.
Studio Status & Trademarks: Thunderbear Studios™ is an independent software and applied-AI engineering studio. Resonant Exocortex MCP, Resonant Cloud, and the Studio-12 Ensemble DSP Workstation are proprietary software platforms currently in Public Sandbox & Early Access (pre-revenue). All proprietary software, verification engines, and architectural specifications not explicitly released under an open-source license remain copyright © 2026 Thunderbear Studios™, all rights reserved.
Legal Notice: Product documentation and benchmark receipts on this website are published for technical evaluators, early-access users, and cloud/technology partners. Nothing on this site constitutes an offer to sell or a solicitation of an offer to buy any financial security.