ZOMDIE
Store readiness
Privacy
A plain-English draft of what Zomdie uses to run accounts, puzzles, and multiplayer rooms.
Account Data
- Zomdie uses Supabase email OTP for account sign-in.
- Your email address is used for sign-in and account management.
- Signed-in players receive a generated survivor nickname/profile.
- Party guests can use a nickname and room session secret without creating a full signed-in Zomdie account.
Gameplay Data
- Daily attempts/results may be stored for official runs, replay personal bests, and leaderboard-style views.
- Training progression may be stored for signed-in players.
- Head-to-Head participation, results, Series history, and room/session state may be stored.
- Party host/guest participation, room state, round results, nicknames, and session secrets may be stored for room continuity.
- Shared multiplayer records may be retained in anonymised form where needed to preserve other players' match or party history.
QR And Camera
- Camera access is requested only when you choose Scan QR.
- The camera is used to read Party or Head-to-Head join codes.
- Zomdie does not intentionally store QR camera frames.
- Manual code entry remains available if camera access is unavailable or denied.
Providers And Tracking
- Supabase is used for auth, database, and backend services.
- Hosting/provider logs may exist for normal security, reliability, and debugging operations.
- No ads, in-app purchases, or third-party tracking are implemented in this repo at this checkpoint.
Deletion And Contact
Account deletion is available from the Account page. Zomdie removes personal solo/profile/progression data where safe, anonymises shared multiplayer references where needed, preserves shared match history where appropriate, then deletes the auth user through a server-side admin path.
Support email: support@zomdie.app.