Privacy & credits

What is kept

On your device: local and computer game saves, town and dice choices, computer speed and sound setting, the guest session token, and cached game pages and map pictures for offline play. These support the game and your requested settings; they are not advertising preferences.

For private online games: a guest account identifier (a pseudonymous UUID, not truly anonymous), nickname, room code and membership, seat, game state, action log and timestamps. Please do not use your real name or contact details as a nickname. Online invitations store a one-way fingerprint of the code plus issue, expiry, use and revocation records. Failed join attempts are recorded for abuse prevention. Saved contacts and blocks keep the other player’s guest identifier and nickname against yours.

For beta accounts: if you sign in for the wider beta, we process your email address, your account user ID, sign-in and session records kept by the authentication service, and your beta access status (active or suspended). These are used to sign you in, decide which beta features you can use, prevent abuse and keep the service secure, and to answer support or account requests. We do not ask for your real name, date of birth, phone number or address, and your game nickname stays separate from your email. Other players never see your email. Playing the public beta towns does not need an account; earlier guest play used a pseudonymous guest identifier instead, which is a different identity from a signed-in beta account.

Operator and staff records: to run the beta safely we keep, against account IDs, any staff role or responsibility given to a helper, changes to a tester's access status, short internal notes explaining a suspension, and an audit record of who made each staff or access change and when. These are used only for moderation, security and accountability, are visible only to the operator and authorised staff, and internal notes are not shown to the tester concerned. You can ask about them through the contact address below.

The hosting infrastructure may also process IP addresses, browser or device information, request records and security logs. The game does not integrate advertising trackers or use AI to play your turns. We cannot promise that hosting traffic analytics or operational logs do not exist.

Why and who can see it

Game and session information is used to provide the play you request, including saving your place and processing invitations (the requested service or contract, where applicable). Abuse controls and security records help protect rooms and the service; the proposed basis for that processing is legitimate interests in preventing misuse, balanced against players’ privacy. You may object to processing based on legitimate interests where applicable. We do not sell player data.

Other people in your room see your nickname, seat, game state and match activity. Your saved players and block list are private from other players through access controls, but authorised operators and service providers may process data needed to run or protect the service. The live preset quick messages are visible to room participants; there is no free-text public chat.

Providers and location

The app currently uses Lovable hosting and Lovable Cloud for sign-in, beta accounts and rooms; see the backend provider’s privacy notice. Railway is only a possible future provider, not part of this current setup. Exact service providers, data regions and any international transfers depend on deployment configuration and still need confirmation; this notice does not promise UK-only storage or a particular transfer safeguard.

How long data stays

An automatic daily clean-up removes old game records. An invite stops working after 30 minutes, or earlier if used or revoked; its record is deleted up to 7 days after it stops working. Join attempts, including failed ones, are deleted after up to 30 days. Closed or finished rooms, with their players, game state and action log, are deleted up to 30 days after the room ends; rooms still open or in play are kept. Because the clean-up runs once a day, deletion can happen up to a day after these periods.

Beta accounts and their access status, staff roles and responsibilities, the staff audit record and internal moderation notes are kept until the account is deleted on request, access is revoked, or the operator removes them manually. Contacts and blocks remain until you remove or unblock them, or until operator deletion. Device saves, settings, session and offline copies remain until cleared by you or your browser, subject to browser behaviour.

Clearing browser data does not erase server records. It can also lose your guest identity, room seat and the identity your blocks refer to; a new guest browser identity may not be recognised by a previous block.

Your choices and rights

Where applicable, you can request access, correction, erasure, restriction, objection or a portable copy of your personal data. A request about a beta account can be verified through the email address on that account; a request about older guest game data may need verification through that guest session. Account deletion is handled manually on request; there is no automatic deletion button yet. Send your request to support@ludomytown.app. You can also complain to the UK Information Commissioner’s Office.

Guest membership checks, restricted player lists and one-use hashed invites reduce some risks, but no online service can promise perfect security.