Privacy Policy
Lastboard is published by Crosswind Games ("we"). Privacy contact: privacy@dfmate.com. Effective: 19 November 2026.
1. What Lastboard does
Lastboard is a multiplayer puzzle game. When you open the app it connects to our server to load your account data; tap PLAY to join the queue and be put in a match with other players; when there are not enough players, computer-controlled players take the empty seats.
The game needs an internet connection; matches run on the server. You play with a guest account (no sign-up) and may link a Google account to keep your coins, items and results on a new phone. There are optional rewarded ads (opened only when you choose to watch one for coins). There are no purchases with real money yet.
2. Data we process
| Data | What for | Where it goes | How long |
|---|---|---|---|
Guest identity: a random gid and a secret gkey made by the app | Recognise your account: coins, rank, owned items | Stored on your phone. Sent to the server in the connection message and in authenticated API requests. In its database the server stores only the gid and a hash of the gkey (never the gkey itself) | On the phone: until you uninstall or clear app data. On the server: until you delete your account (section 6) |
| Session key (random string issued by the server) | Return you to the same seat after a dropped connection; attach your connection to the match you are in | Stored on your phone; sent to the server each time you connect | On the phone: until you uninstall or clear app data. On the server: in memory only; dropped when you disconnect while not in a match; if you drop mid-match your seat is held so you can return; dropped when you delete your account if the session is currently associated with that account; gone when the server restarts |
Auto-generated player name (e.g. AmberFox_123; the interface only lets you re-roll it) and the avatar / frame you pick | Shown in matches and standings | Stored on the phone and the server. The name is shared with other players (in matches, on the leaderboard and, when you finish in the top three, for up to 30 minutes afterwards in a list of recent results given to any other player of the app, guest accounts included, together with your placing (1–3), the game and how long ago; not if you are hidden from the leaderboard or banned, and not after you delete your account). In the app, this list appears only on the main screen (the Lobby, Games tab), one line at a time with the name, placing and how long ago; the app does not show the game. The server shares your avatar/frame choice; the interface does not yet fully display other players' choices | On the phone: until uninstall / clear app data. On the server: until you delete your account |
| Name re-rolls per day and a mark that the server made the name | Apply the re-roll limit | Stored on the server | Erased with the account |
| Match results: match ID, game, placing, ranking points, how many rival boards you helped Jam, coins earned, time, day/week/season | Weekly/season leaderboard; the list of recent results given to any other player of the app, guest accounts included (your name, placing 1–3, game and how long ago, for up to 30 minutes after you finish; at most 3 people in the list, each person once; not if you are hidden from the leaderboard or banned); the Profile stats derived from them (matches played, best placing, daily streak); coin payout | Stored on the server | Until you delete your account. The server currently has no schedule that purges old results |
| Coin ledger and owned items: every coin credit/debit (from matches, ads, cosmetic purchases made with coins) and the items you own / wear | Keep your balance, prevent cheating, restore on a new phone | Stored on the server | Until you delete your account. The ledger is append-only and is erased together with the account. When accounts are merged, the source account's ledger is erased and its balance moves over as one merge entry |
| Account metadata: when the account was created, device keys added, Google linked, each item received | Run the account | Stored on the server | Erased with the account |
Google link (only if you tap "Link Google"): your Google user identifier sub | Keep your account across phones; merge two phones of the same Google account | The app sends the Google ID token to the server; the token may contain profile fields. The server verifies its signature and in its database stores only a hash of the sub; no email, name, photo or token | Until you delete your account (erased with it) |
| Account restrictions: ban flag, hidden from the leaderboard, when it changed | Handle rule violations | Stored on the server | The current flags are erased with the account; the history of admin actions is kept separately (section 6) |
| In-game activity: pieces placed and where, targets picked, joining the queue, leaving a match | Run the match, check the rules, rank players | Sent to the server | In server memory until the match ends |
| Rewarded ads (Google AdMob): the Google Mobile Ads SDK in the app | Show the ad, pay the coin reward. According to Google, the data the SDK collects automatically is used for advertising, analytics and fraud prevention | Google's SDK automatically collects and shares with Google: (1) the device's IP address (Google says it may be used to estimate the device's general location); (2) product interactions: app launch, taps, video views; (3) diagnostic information about the performance of the app and the SDK, such as launch time, hang rate and energy usage; (4) device and account identifiers: the Android advertising ID, the app set ID and, if applicable, other identifiers related to signed-in accounts on the device. The app has the AD_ID permission (added by the ads library when the manifest is merged) so the SDK can read the advertising ID. This list follows AdMob's "Google Play data disclosure" page (read 15 Nov 2026; the app uses version 25.4.0, and the version of the page written for 25.4.0, archived on 13 Jul 2026, lists the same data types as the current one); Google states the SDK's data is encrypted in transit (TLS). Google handles it under Google's policy: https://policies.google.com/privacy (how Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites). When requesting a rewarded ad, the app also sends Google a random account ID (gid) and a reward reference code (nonce). Our server receives the nonce, the account ID and reward-transaction verification data from Google | Google's side: under Google's policy. Advertising ID: you can reset or delete it in Android Settings (section 6). Our server: next row |
Reward verification records: nonce, gid, issue / expiry / credit time, day, Google's transaction ID | Prevent double rewards, apply the daily limit | Stored on the server | An expired, unrewarded nonce is cleaned up when the account starts its next ad; a rewarded row is kept until you delete your account |
| Reward claim not yet sent: nonce and its expiry | Retry when back online | Kept on your phone for a while; sent to the server on retry | On the phone: until it is sent, or until you uninstall / clear app data; once expired the app no longer uses it |
| Ad choices (UMP): each time the app opens it asks Google's User Messaging Platform SDK; if the SDK requires it, the app shows Google's consent form. When Google requires a privacy options entry, you can re-open it in Profile / Settings | Ask for ad consent where Google requires it | Google's SDK stores and manages the choice; Google handles it under Google's policy | Per Google |
| Invite code (test build) | Lets you into the test build | Stored on your phone; sent to the server when connecting | On the phone: until uninstall / clear data |
| IP address | Cap connections/requests; hourly/daily visit counts; stop password guessing on the internal admin page | The game server processes IP addresses in memory to rate-limit connections/requests, to stop password guessing, and to produce hourly/daily visit counts; it does not write players' IP addresses to logs or the database. The statistics data is cleaned up hourly once at least 24 hours have passed since an address was last seen (usually 24–25 hours); the rate-limiting and password-guessing data lives only in memory, is lost when the server restarts, and may last longer than that. When the admin page is enabled, requests to it (sign-in, and denied access) are written with their IP address to the system log to stop password guessing; that part of the log is kept until the system log rotates by size, with no day-based limit. Infrastructure providers (Cloudflare, the server host) process IP addresses under their own policies (Cloudflare: https://www.cloudflare.com/privacypolicy/) | As in the previous column |
| On-device settings and history: sound, language, reduced motion, vibration, latest placings, the downloaded game packs | Remember your choices | Stored on the phone; the app has no flow that uploads them to the server (game packs are only downloaded) | Until you delete it in Settings / uninstall / clear data |
The app does not ask you for your real name, email, phone number, precise location, contacts, photos or audio. For Google linking, see the "Google link" row above.
The app has no standalone analytics or crash-reporting SDK. It uses Google Mobile Ads (AdMob), Google User Messaging Platform (UMP) and the Google sign-in library; it uses Capacitor for the Android shell and a cryptography library to verify the game packs.
Other players see your auto-generated name and rank. Players in your match also receive your board state, score, being knocked out (Jammed), aiming and attack information, and emotes when that feature is on. The server shares your avatar/frame choice; the interface does not yet fully display other players' choices.
3. Security
The release build connects to the server over https:// / wss:// (TLS) and blocks unencrypted connections.
The server runs the rules and decides results; the app sends moves and control messages. In its database the server stores only a hash of the gkey.
4. Separate game download
The app contains only the shell. Each game is a separate package downloaded from our server; the app verifies the package's digital signature and per-file hashes before running it, runs it in a sandboxed frame, and gives it no direct access to the Android bridge (a pack can only ask the app to vibrate). You can delete packs in Settings.
5. Android backup
The app declares allowBackup=true, so Android's backup mechanism may back up the app's local data (guest identity, name, invite code, settings). What is actually backed up depends on your device and settings.
6. Your rights and deletion
- In the app: Profile → Delete my data (two-step confirmation). The server erases the account records in its database: name, avatar/frame, match results, coin ledger, owned and worn items, reward verification records, name re-roll counts, restriction flags, the Google link, and the authentication keys stored in the database. The server also ends the open sessions in memory that are currently associated with that account: it closes the connection, gives up the seat in a match in progress, removes you from the queue, the old session key can no longer reclaim a seat, and no match result is written for that account. The old data is deleted. For a plain guest, the old identity pair can still create an empty guest account. For an account that was linked to Google or has more than one device key, the old identity cannot be used again.
- On the web, no app needed: https://arena.dfmate.com/delete-data/: enter the Account deletion code from the app (Settings/Profile, tap to copy). The code is a secret credential: anyone who has it can delete the account. If you lost both the app and the code, you can write to privacy@dfmate.com with your generated name; without the code we may not be able to verify who owns the account, so we may not be able to delete it.
- On the phone: uninstall, or Android Settings → Apps → Lastboard → Clear data, removes the local data (it does not remove server data; delete the account first).
- Not linked to Google: uninstalling the app or clearing its data may lose your coins, items and rank: you may lose access if you no longer have the credentials or a backup that can be restored. Linking Google is the recovery method the app supports: signing in with the same Google account on a new phone makes the server merge that phone's new guest account into the linked one. To delete the server copy too, tap Delete my data before uninstalling, or contact privacy@dfmate.com.
- Ads: reset or delete your advertising ID in Android Settings; when Google requires a privacy options entry, re-open it in Profile / Settings.
- What remains after deletion: (1) IP addresses: as in the "IP address" row of section 2 (when the admin page is enabled, the system log only records the IP of requests to it; infrastructure providers under their own policies); (2) the admin log (append-only; the system does not allow deleting any row): it keeps the
gidand the content of the admin actions ever taken on the account (coin credit/debit, ban, deletion), including the reason entered by the admin and the old/new values; this content may contain information related to the account; kept for an indefinite period; (3) for an account that was linked to Google, has more than one device key, or was merged into another account: a hash of the identifier and the time, so the old identifier cannot be used again; there is currently no automatic deletion schedule; (4) aggregate counts that contain no IP address; (5) backups of the server database: the server takes a copy every hour (keeping 48 hourly and 14 daily copies) on that same server; not copied anywhere else. Data of a deleted account may remain in these backups for up to 14 days, and then disappears when the old copy is deleted; backups are used only to restore the service after an incident.
7. Children
Lastboard is not directed at people under 16. The app does not ask for age.
8. Changes
The effective date of the current version is shown at the top of this page.