What FLORKE ID and Arena process
- Your email address, verification records, session identifiers, and essential authentication records when you request or use an email sign-in code or private link.
- Your permanent public FLK number and handle, approved avatar choice, optional bio, connected game records, and badges derived from recorded activity.
- Arena rating, results, room events, match history, and provisional competition points tied to the same FLORKE ID.
- Limited technical and security signals needed to protect sessions, throttle abuse, diagnose failures, and investigate fair-play concerns.
Do not put sensitive information in your username or bio. Public profiles and standings may expose those fields, earned badges, connected games, match history, rating, record, and provisional points. Email addresses, opaque authentication account IDs, session data, and raw security signals are not public profile fields.
Why it is used
The data supports sign-in and account recovery, one persistent identity across connected games, server-validated games, reconnection, profiles and standings, service security, troubleshooting, and human review of potentially unfair play. The private authentication account is linked by an opaque provider ID, never by matching public names or email addresses. It is not used to require a token purchase or wallet connection, and the service does not sell personal information or use it for third-party advertising.
Cloudflare/OpenAI Sites provides the application and database runtime. Resend delivers requested sign-in email. Those providers may process the limited data needed to perform those services under their own terms.
Storage, retention, and controls
The service uses an essential session cookie and browser storage for saved room, queue, and reconnect state. No advertising cookie is intentionally installed. FLORKE ID public pages are marked not to be indexed during this beta, but anyone with a valid public profile link can open that page. Account, profile, badge, match, and security records are retained while needed to operate and protect the beta and preserve competition integrity.
A complete retention schedule and private self-service access, export, correction, and deletion channel are not published yet. Those controls must be documented before prize certification can open. Until then, avoid submitting information beyond what play requires.