Privacy

We respect your privacy and keep things simple. Here's what we collect, why, and what we don't do.

What we collect

• Contact form submissions -- only what you type and send us.
• Error monitoring -- we use Sentry to automatically capture JavaScript errors, stack traces, browser/OS info, and page URLs so we can fix bugs. Sentry may receive your IP address (used for rough geo-location and then discarded per their policy). Passwords and form inputs are not captured automatically.
• Aggregate usage signals -- for features that aren't open to the general public yet (firmware code editing, compiling firmware, installing on your Cyber Fidget, publishing apps to the Archives store), we record a one-per-session "you tried this" event to Sentry so we can see how many people are interested in early access. These events are counts only -- they never include your code, your clipboard, file names, file paths, file contents, or anything you typed.
• Feedback you submit -- if you click the "Feedback" button on any page, whatever you type is sent to Sentry so we can read it and improve the site. No email or name is required.
• Error reports you choose to share -- in the App Builder, when a build fails you can click "Share this error" to send the error message, your app name, and which code generator you used to Sentry so we can help debug. A separate, unchecked-by-default checkbox in that dialog lets you also include your code -- only if you tick it does any code get sent. Nothing in this path is sent unless you click Share.
• GitHub sign-in -- there are two entry points and they ask GitHub for different things:
  • Signing in from the site header asks for your profile only (username, avatar). We use it to recognize you. GitHub grants no access to your repositories in this case.
  • Signing in from the firmware code editor (the "My Project" panel on Build) currently asks GitHub for permission to create and update a public repository on your behalf, so the editor can save your work and trigger firmware builds. We're working toward narrowing this -- requesting the elevated permission only at the moment you save, supporting private repositories, and keeping the default footprint as small as possible.
  You can revoke either at any time in your GitHub account settings.
  
  When you trigger a firmware build, your browser passes a sign-in credential from GitHub to our build server alongside the request. We use it once to look up your username (so we can recognize you across builds and keep one person from overwhelming the build server) and we don't store or log it. A future flow will keep this credential in your browser only; this is the honest interim state.
• API keys (BYOK) -- if you bring your own model provider key in the App Builder, it's stored in your browser's local storage only. Keys for Anthropic and Gemini go directly from your browser to their APIs. OpenAI keys are proxied through our server solely to avoid CORS restrictions and are never stored.

What we don't do

• We don't sell, rent, or share your data with advertisers.
• We don't use tracking cookies or third-party ad networks.
• Beyond the error monitoring and aggregate usage signals described above, we don't run user-behavior analytics.

Third parties

• Sentry -- error monitoring and feedback (their privacy policy).
• GitHub -- sign-in and firmware compilation (their privacy policy).
• Shopify -- if/when purchases are available, checkout occurs on Shopify and their privacy policy applies.
• Kickstarter -- backing occurs on Kickstarter and their privacy policy applies.

Sprite Library Credits

The Build tools include a library of pixel art sprites. All sprites are released under CC0 1.0 (Public Domain) by their creators. While no attribution is required, we want to celebrate these generous contributors:

• Kenney -- 1-Bit Pack, 1-Bit Platformer Pack
• tstamborski -- Pixel Art Icons
• drummyfish -- 1-Bit Graphics Collection

Your rights

You can clear all locally stored data (tokens, API keys, app builder state) at any time by clearing your browser's local storage for this site. If you want us to delete any feedback you've submitted or have other privacy questions, contact us.

Last updated: May 2026