Cookie Policy

The short truth

GayLab does not set cookies — not for tracking, not for ads, not for anything. There is no cookie banner because there is nothing to consent to.

What exists instead

Your browser holds four per-tab sessionStorage keys. gaylab:consent keeps your consent token for the current tab, gaylab:photo hands your photo from the scan to your result view in the same tab, and gaylab:ref remembers which friend's result link brought you here so their report can unlock when your scan completes.

The fourth, gaylab:battle, remembers which side of a battle this device played (challenger or opponent) so the verdict page knows who it is talking to. It is per-tab like the rest and never leaves your browser.

All four of those vanish when the tab closes. Two values travel with a scan when you run one: your consent token, and the gaylab:ref link code that gets your friend credit for the invite. The photo handoff copy and the battle marker never leave your browser.

Two things outlive the tab. One localStorage value, gaylab:install-dismissed, records only that you closed the install prompt: no identity, no scan data. And an offline cache of the app's own files, layout, icons and fonts. No photos, no verdicts, no scores, no API responses. Clearing site data removes both.

Analytics

Hosting and analytics run on Vercel, whose analytics are cookieless — no cross-site tracking, no ad identifiers, no profiles.