Privacy / 01

Privacy

A clear record of what we collect, why we collect it, and what we leave alone.

// 02 The policy What you should know

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 -- your name, email address, and message, plus your IP address and browser information. We store it in our database and email a copy to our team (via Resend). If you opt into launch updates, your email address also goes to Mailchimp.
  • Error monitoring -- we use Sentry to automatically capture JavaScript errors, stack traces, browser/OS info, page URLs, and session-level reliability counts so we can fix bugs. We configure Sentry not to send default personal information and to redact recognized secret patterns, but avoid putting passwords or keys in feedback or URLs.
  • 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. Each event carries the feature name and standard technical context (the same error/session context Sentry attaches); it never includes 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 either to Sentry or, if that service is unavailable, directly to us and stored in our database, along with the page URL and standard technical information such as your IP address and browser information. 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, the code generator, and the selected provider and model 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 -- initial sign-in, from the site header or the firmware code editor, asks for your profile only (read access to your public GitHub info). We use it to recognize you and check your access; it grants no permission to change your repositories.
    • Only if you later choose "Connect repositories" does GitHub grant access to your public repositories (the `public_repo` and `workflow` permissions). The editor uses it to create and update your firmware repository and run its build workflow, so it can save your work and trigger builds.
    • You can revoke access at any time in your GitHub account settings.
    When you trigger a firmware build, your browser passes your GitHub credential to our build server. Your browser also sends it to our feature-check and signed-in Archives endpoints to identify your account. Our code uses it to verify your GitHub identity and doesn't intentionally store the raw credential; signed-in Archives features may keep your GitHub id, username, name, public email, and avatar.
  • API keys (BYOK) -- if you bring your own model provider key in the App Builder, it's saved 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 only to avoid cross-origin restrictions, and our code doesn't intentionally store them. In every mode, the provider receives the prompts and code needed to generate or revise your app. Free-tier generations use our Anthropic account, and we keep usage counts (not your key).

What we don't do

  • We don't sell, rent, or share your data with advertisers.
  • We don't display third-party ads.
  • We use Google Analytics on most pages to understand how the site is used -- how many people come and where they get stuck -- so we can prioritize fixes. It may set cookies under Google's policy, and this privacy page itself doesn't load it. We don't sell this analytics data or share it with advertisers for targeted advertising.

Third parties

  • Sentry -- error monitoring, feedback, early-access interest signals, and session reliability counts (their privacy policy).
  • GitHub -- sign-in, account identity for signed-in features, and firmware compilation (their privacy policy).
  • Google Analytics -- site-usage measurement on most pages (their privacy policy).
  • Mailchimp -- launch-update and newsletter email (their privacy policy).
  • Resend -- delivering contact-form messages to our team (their privacy policy).
  • Anthropic, Google (Gemini), OpenAI -- app code generation; the provider you use receives the prompts and code you send (and, for BYOK, your key as described above).
  • 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:

Your rights

You can clear the data this site keeps in your browser -- preferences, sign-in state, API keys, projects, and compiled previews. This lives in cookies, local storage, session storage, and IndexedDB, so use your browser's "clear site data" control to remove all of it; clearing local storage alone won't remove everything. If you want us to delete any feedback you've submitted or have other privacy questions, contact us.

Last updated: July 2026