Mecha Frontier is operated by Madao San, an individual entrepreneur in Georgia. Contact: amadeusplaystudios@gmail.com.
We store your pilot name, equipment, progress, clan membership and social interactions to run the game. Google, Discord and X sign-in supplies a provider account identifier and basic profile information. The game does not request your account password. Provider access tokens are used to verify your identity during sign-in and are not retained in the game database. Google and Discord sign-in request email for account support; only a verified email supplied by the provider is retained, visible in the owner dashboard. X may not supply email. We do not request contacts, posting or direct-message permissions. Administrator sign-in separately requests a verified Google email to enforce the owner allowlist; admin sessions expire after 12 hours. X requires read-only users.read and tweet.read scopes for this sign-in integration; the game does not retrieve posts.
Essential cookies maintain your account session for up to 30 days and protect sign-in requests for 10 minutes. Local storage remembers a guest pilot access key and sound preferences. Clearing a guest key can lose access to that guest pilot. An unlinked guest pilot can link an unused Google, Discord or X identity to preserve access to the same progress across devices. Existing pilots are not merged. After linking, the old guest access key no longer grants access; use provider sign-in. There are no advertising cookies or third-party analytics trackers in the game.
Links under /go/ measure visits from our social posts on this server. The random first-party cookie mf_visit lasts for 30 days. We store a keyed hash of its identifier, source and visit time for up to 30 days, without saving an IP address with visits. If you create a pilot within 30 days of a tracked visit, we associate the first eligible source with a keyed hash of the pilot ID. We record the server registration date and first observed attainment of level 10 to measure how many new pilots continue playing. Names, email addresses, sign-in keys and messages are not copied into campaign analytics or sent to social platforms. The original source stays fixed; signing in to an existing account does not create another registration. Aggregate account progress is visible only to the owner. Pilot conversion records are retained while the associated game account is retained. Missing historical dates and attribution are shown as unknown. Browser counts are estimates; preview bots and owner visit checks are excluded. You can open the game directly without a campaign link or clear the cookie.
Your nickname, equipped mech and location in a shared hangar are visible to other players there. Room and arena messages are visible in their respective channels. Private messages are shown to the sender and recipient, stored on the game server and are not end-to-end encrypted.
The server looks up your connection country locally from your IP address and stores its two-letter country code for a flag beside your nickname. The lookup does not send your IP to an external service. VPNs and proxy networks may affect the result. This product includes GeoLite2 data created by MaxMind, licensed under CC BY-SA 4.0.
Payment providers shown at checkout process purchases. The game does not receive or store your bank card details. We store order identifiers, selected package, payment status and transaction references to deliver tokens and prevent duplicate credits. Payment providers and public blockchains process transaction information under their own policies. Never submit wallet recovery phrases or private keys to the game.
When you use @MechaFrontierBot, it receives your Telegram user identifier, interface language, messages sent to the bot and payment events. For checkout delivery, duplicate-payment protection and refund support, we retain the order, payment reference, consent record, language, an encrypted Telegram user identifier and a pseudonymous identifier. This associates a purchase with its receiving pilot and does not add a new sign-in method or create another game account. The bot does not receive your bank card details. Telegram processes Stars purchases under its own policies.
The owner can view server health, online pilot names and purchase records in a restricted dashboard. Successful purchase alerts sent to the owner's privately paired Telegram chat include the pilot nickname, order ID, package, amount and payment method, never card details or sign-in credentials. Only the verified owner can pair or remove that chat.
The owner dashboard can show inventory, assembled mechs, verified email, purchase totals, the latest IP addresses and an approximate IP-derived country. IP records and security events are retained for up to 30 days, with a maximum of ten IP addresses per account and 500 recent security signals. Request and country aggregates cover the last 30 days. Shared IP addresses are review signals, not proof of cheating. No external advertising analytics are added.
Administrative grants, removals and bans are recorded in an audit trail. In-game reward mail is retained with the account; attachments can be claimed once. YouTube referral rewards equal 10% of confirmed purchased tokens and are sent through in-game mail only. Refunds cancel unclaimed referral rewards; already claimed rewards require manual review.
We record the accepted terms version and server time when a pilot is created, and retain a separate acceptance receipt with each purchase order. No checkbox is preselected.
Game data and backups are stored on the operator's server. Hosting services may process technical connection logs, including IP addresses, to deliver and protect the service. We retain pilot records while needed to provide the account, and purchase records as needed for reconciliation and applicable obligations. Contact support to request access, correction or deletion; we may need to verify account ownership. Necessary payment records and backups may remain after an account request.