Your challenge data.

When you start, AlfaZulu stores your answers, timing, pauses and result on its server. Timed runs use 15 seconds per question. A small session-storage entry can preserve a pending answer until it reaches the server. An essential HttpOnly cookie lets this browser resume the run and proves ownership when you save it.

Anyone with your unguessable result link can see your score, discipline breakdown, time, challenge title and answer debrief. The public page does not show your name, email or account identifier. Do not share the link if you want the score to remain private.

Unsaved runs stop being accessible after 30 days. Saving a completed run links it to your AlfaZulu account. Account deletion removes linked challenge results. An expired run is not necessarily immediately erased from backups or storage.

Creator and referral codes on your challenge link are saved with the run to support challenge comparisons and campaign reporting. Optional page, answer and sharing analytics follow your existing analytics-consent choice. A share-button click does not tell us whether you actually sent the link.

If you allow advertising cookies, Meta Pixel can measure completed timed Checkrides for our Facebook and Instagram campaigns. Meta may receive browser/network information, advertising cookies or click identifiers, the challenge page URL and referrer, and a random deduplication event ID. We do not send Meta your score, answers, email, account identifier or private result link. Practice and labelled QA runs are excluded. This is optional advertising measurement, not anonymous usage analytics. Declining it does not prevent play. Change or withdraw your choice from the cookie controls in our full privacy policy.

Abuse controls use a short-window, keyed hash of your network address. Raw IP addresses and device fingerprints are not stored in challenge records. Hosting providers may maintain their own security logs.

These campaign results currently appear on the web, not as badges in the mobile app.