Skip to content

Research & privacy

What sharing submissions means

GAS is a new language, and the fastest way to make it better is to see how people actually use it. When you first turn on audio in a demo, you can choose to share explicit Play, Retry and Send submissions. It is off unless you turn it on, and the demos work exactly the same either way.

Playback counts and optional Google Analytics

The demos send first-party playback counts independently of research consent. Each attempt has a random identifier used for at most one hour of correlation; expired records are removed by scheduled cleanup. Daily counts expire after 90 days. They contain the demo, audio route, event, outcome and a broad failure category, never your document, key, IP address, or research deletion token. No identifier links separate attempts.

Analytics settings lets you turn these counts off. If Google Analytics is configured, it loads only after you accept, to measure acquisition using sanitized page information. It receives no GAS source, commands, keys or playback events. Rejecting it leaves the demos available. Your choice is remembered locally; you can change it at any time. Optional Google cookies expire after 90 days and are removed when you withdraw.

The research details below describe the separate, opt-in research collection.

What is collected

  • On Play or Retry, the exact source you submitted and its compile diagnostic codes, even if it did not compile. Unedited built-in examples and the game score are recorded by ID only.
  • On Send, your live GAS command, the number of statements applied and bounded warning or failure codes.
  • The demo, submission kind, result, timestamp, site and GAS versions, consent version and a hashed deletion credential.

What is never collected

  • Your API key, in any form.
  • Audio — nothing you hear is recorded.
  • Keystrokes, unsubmitted drafts, or a history of playback or game moves.
  • Your IP address, location, or an identifier shared with audio access or analytics.
  • The page address, referrer, or anything from the contact form.

Why and who reads it

Only to improve GAS: which parts of the language people reach for, where they get stuck, which errors they hit, and what they write when nobody is showing them an example. It is read by the GAS team at Luna Estelar. It is not sold, not shared, not published as a dataset and not used to train models.

How long it is kept

90 days, then it is deleted automatically.

Taking it back

While sharing, the demo shows Stop sharing & delete. Withdrawal stops new submissions immediately and requests deletion of stored samples and upload access. Separate random upload and deletion credentials are kept locally. Only the deletion credential is in the copyable link, so the link cannot submit samples. If local storage is blocked, copy the link before leaving the page. A failed deletion keeps the link and offers a retry. Consent to share new submissions ends with the visit; stored deletion access does not renew it. Unremoved samples expire after 90 days.

If upload access expires or is deleted through a copied link, sharing stops. You can opt in again through the demo’s audio options. Earlier deletion links remain available until cleanup succeeds; rejected submissions are not sent again.

Shared audio

Separately from research, shared audio gives each browser a daily audio allowance, which can be used across multiple sessions without anyone signing in. Stopping spends only the audio generated; another session needs at least 30 seconds remaining. To do that it sets one cookie holding a random identifier — not derived from anything about you or your device — and counts that identifier's seconds for two days. No script on the page can read the cookie, it carries no balance, and it is never joined to research or analytics: those requests are sent without cookies at all. Clearing it creates a new identifier; the address limits still apply.

It also keeps a keyed hash of your address (for IPv6, its network prefix) for as long as your session lasts, and in a daily count, so one network cannot take every slot. Everyone behind one address — a household, an office, a phone network — shares those ceilings, but no longer shares a single turn: two browsers there can play at once. Neither the cookie nor the address count is a count of people. If your browser blocks the cookie, the demo says so and offers your own key instead.

This cookie is not part of the analytics choice above, and withdrawing Google Analytics does not remove it: it keeps turns fair, and is not a measurement.

Consent version 2026-10-10.