TankForge · DoD
Privacy policy
Current Google Play release: TankForge 0.22.0 (build 58), package com.daveonduty.tankforge, requires Google sign-in or a verified email account and synchronises solo careers. It also supports local Wi-Fi multiplayer. Public internet matchmaking and global leaderboards are not enabled. TankForge is publicly available on Google Play.
Google or verified email login links your solo career to your TankForge account so it can be restored on another device. There are no active advertising, analytics or remote crash-reporting SDKs in the game.
Older versions: offline Google Play 0.19.10 (build 51) has no accounts, cloud saves or Internet permission. Version 0.20.1 (build 53) and 0.20 previews have optional accounts and device-local careers. Their local careers are not automatically uploaded. The development preview is a separate installation from the Google Play app.
1. Data on your device
TankForge stores a private save file inside the app’s storage. It can contain:
- campaign stars, unlocked achievements and daily-reward history;
- credits, XP, levels, owned and equipped tanks, paints, upgrades, attachments and garage capacity;
- match totals, personal records and up to 30 recent match summaries for each local career;
- custom battlefields you create; and
- settings such as difficulty, controls, sound, music, motion and graphics quality.
All builds keep local data in TankForge’s private app storage and disable Android’s automatic backup. In 0.22.0, campaign stars, solo credits and XP, owned tanks, upgrades, rewards, achievements, personal records and recent solo match summaries are also sent over HTTPS to the dedicated Supabase project and linked to your TankForge user ID. Device settings, custom maps and the separate local multiplayer progression are not included in this cloud career.
TankForge does not request access to your location, contacts, camera, microphone, photos or files.
2. Local Wi-Fi and direct-IP multiplayer
Multiplayer in 0.22.0 connects participating devices directly using Godot ENet on UDP port 28777. Nearby Wi-Fi Games uses local-network discovery on UDP port 28778 to advertise and find hosted games. You choose to host, select a nearby game or use a room code or host address. During a session, the game exchanges the information needed to run the match, including peer identifiers, movement, shots, hits, objectives, scores and, where used, a validated custom-map layout.
Local discovery and match traffic are not encrypted by the game. Use a trusted network. This is separate from account and cloud-career requests, which use HTTPS. Signing in does not enable public internet matchmaking.
Internet addresses are necessarily visible to the computers or phones taking part in a direct connection. DoD does not provide a relay, matchmaking service or dedicated game server for this feature, and does not receive or retain the match traffic. A host or network provider may have its own technical logs, outside DoD’s control.
3. Accounts, adverts and analytics
Accounts and cloud careers
When you register or sign in, TankForge sends authentication requests over HTTPS to our dedicated Supabase project. Supabase stores your account identifier, email address, pilot name where supplied, sign-in timestamps and authentication records. Email/password registration sends your password to Supabase for authentication; passwords are not stored in plain text by the game. Google sign-in shares the basic identity information you approve, which can include your name, email address, profile picture and Google account identifier. We do not request access to your Gmail messages, contacts or Drive files.
Authentication providers process technical information such as IP addresses and security logs to operate and protect sign-in. Supabase hosts the account service; Google processes Google sign-in; Namecheap Private Email delivers confirmation and password-reset emails from support@daveonduty.co.uk. Your device stores session credentials in the app's private storage so you can remain signed in. Do not share passwords or email verification codes with support.
Account information is used for authentication, account administration and security, not advertising. Cloud-career data in 0.22 is used to back up and restore solo progression across devices. Each cloud save has a revision and update timestamp. Conflicting device saves require an explicit choice; both choices are backed up locally before replacement. Cloud careers are not authoritative competitive rankings. Version 0.20 and offline build 51 do not upload their local careers.
Advertising
The project contains a provider-neutral placeholder for optional rewarded adverts. No mobile advertising SDK, advert identifier or provider is configured, so no advert can load and no data is sent to an advertising company.
Analytics and crash reports
TankForge has no analytics or remote crash-reporting SDK in the current build. If the app stops unexpectedly, no crash report is automatically sent to us.
4. Android permissions
- Internet (0.22.0): used for authentication, cloud-career synchronisation and local-network/direct-IP multiplayer. The older offline build 51 does not request Internet permission.
- Vibration: used for gameplay feedback supported by your device.
5. Retention and deletion
Local progress remains until you clear TankForge’s storage or uninstall it. Direct-IP match traffic lasts for the live connection; DoD does not keep a server copy. See account and data deletion for step-by-step instructions.
Your account and cloud career remain until you delete the account. In Account, sign in again, open Manage account / Delete, type DELETE and choose DELETE ACCOUNT PERMANENTLY. This revokes sessions and removes your online identity, cloud career and associated server records; it does not erase local save or conflict-backup files on your devices, or your Google account. Clear app storage to erase those local copies. You can also request deletion by emailing support@daveonduty.co.uk from the registered address. Provider backups and security logs may follow separate retention schedules rather than disappearing immediately; contact support for details about your request.
6. Your choices and rights
Version 0.22.0 requires a verified account and an internet connection for initial setup or restoration. Account-linked solo cloud saving cannot be switched off independently. Once that career is cached and you remain signed in on the device, you can play solo offline and sync later. Signing out removes access to the cached career until you sign in to that account again. You can erase local data through Android settings; this does not delete your cloud career. Older offline build 51 and 0.20 builds allow solo play without an account.
Players who used only offline build 51 do not have an online TankForge account record. Account users can contact us about their account information, access, correction or deletion at support@daveonduty.co.uk. Support correspondence is handled under the Dave on Duty privacy policy. You may use this address to exercise applicable data-protection rights.
7. Children
TankForge is intended for players aged 13 and above. The game depicts stylised armoured combat without gambling or real-money rewards. Consult your regional store listing for the assigned content rating.
8. Changes
We will revise this page when data handling changes, including before enabling public matchmaking, analytics, crash reporting, purchases or an advertising provider. Accounts and solo cloud saves are already covered above. The updated date at the top will change.
Also for TankForge: terms of use · support · account and data deletion.