In effect

PRIVACY POLICY

The short version. You can play without giving us your email address, real name or phone number. Linking your account to Apple, Google or an email address is optional; if you do, we get the details listed under Your account. The game asks your date of birth once, to check you're 13 or older. The date stays on your phone; our servers keep only an age range, which we plan to use one day to show sponsorships only to adults. No sponsorships exist today. There are no ads and nothing is on sale yet, but version 1.2.0 of the game includes Google's ads code, which the game sets up on your phone for your age and which can collect data for Google, and RevenueCat's purchase code, which receives your account ID and some details about your phone (see Ads and Purchases). Everything else we collect is what the game needs to run, to keep competitions fair and to keep players safe, or something you choose to turn on, such as reminders. We don't sell your data.

When this page says "today" or "not yet", it means the game as of November 2, 2026: the closed beta on iPhone and iPad through Apple's TestFlight, by invitation, and on Android through Google Play's internal testing, which has carried version 1.2.0 of the game since October 20, 2026. This page describes version 1.2.0; Settings → ABOUT shows which version you have. Test builds older than version 1.2.0, including the Android build some testers installed from our download link, don't have everything this page describes, and the parts that need version 1.2.0 say so. Where it says "phone", it means any phone or tablet you play on.

One tick agrees to both this Privacy Policy and our Terms of Service: when you create your coach, or on the OUR TERMS HAVE CHANGED screen when a new version needs your agreement. One version date covers both.

Who we are

Football Immortals is made by Gak Games LLC, a New York limited liability company. We're responsible for the data this page describes. Questions, requests and complaints go to support@immortals.football.

Your account

The first time the game starts with a connection, before it asks you anything, it creates an anonymous account on our servers and gives it the starting balance every new account gets. The account is identified by a random account ID. Your phone keeps the key that signs in to it in its secure storage (the iOS Keychain or the Android Keystore). There's no password or phone number on the account, and unless you link it to a sign-in (see below), no email address or real name either.

You can link your account to a sign-in in Settings (the gear on the Play screen), under GAK GAMES ACCOUNT. Every version of the game has offered an email address since October 14, 2026. Version 1.2.0 also offers Apple on iPhone and iPad, and Google on iPhone, iPad and Android, and it offers linking right after you create your coach, under SAVE YOUR COACH, where PLAY AS GUEST skips it. Linking is optional and keeps the same account. Once it's linked, you can sign in to the account on another phone that offers the same sign-in, from HAVE AN ACCOUNT? SIGN IN on the CREATE YOUR COACH screen or from Settings. If you don't link it, your phone is the only way back in: if you lose or reset the phone, the account usually can't be recovered; restoring an encrypted backup onto a new iPhone or iPad may bring it back. On iPhone and iPad, an unlinked account usually survives deleting and reinstalling the game. On Android, uninstalling the game removes its key from the phone, so an unlinked account can't be reached again.

Sign-in runs through Supabase, which runs our servers, and Supabase keeps what each sign-in gives us with your account:

  • Apple: a user ID that Apple makes for our games, and an email address: your own or, if you choose Hide My Email, a private relay address that forwards to you. The game also asks Apple for your name, so Apple's sign-in screen may offer to share it; the game doesn't keep it or send it to us.
  • Google: your Google account ID, your email address and whether Google has verified it, your name, and a link to your profile picture.
  • Email: the address you type.

If your account has no email address yet, linking Apple or Google also puts that sign-in's email address on it. When you link an email address or use it to sign in, we email it a six-digit code (see Messages and notifications). We use these details to sign you in. We don't add them to our waitlist or use them for marketing email, and other players never see them.

SIGN OUT, in Settings under GAK GAMES ACCOUNT, takes the account off this phone and starts a new guest coach. A linked account comes back whenever you sign in again. An account with no sign-in can't come back: it stays on our servers, other players can still see its profile, and nothing can sign in to it any more. If you want its data gone, delete it in Settings instead of signing out.

If you switch to another account while this phone's coach has no sign-in, the phone keeps that guest coach (unless it had nothing to keep yet), so you can switch back from GUEST COACHES ON THIS DEVICE. The phone's secure storage holds its account ID and key, plus its coach name, profile logo, favorite team, number of cards and win-loss record. Each guest coach is a separate account on our servers. Deleting your account in Settings deletes only the coach you're signed in as: the other guest coaches, and their accounts, stay until you switch to each one and delete it too.

Your coach name and profile

When you create your coach, the game suggests a random two-word name. You can shuffle it or type your own. Names must be unique and pass a filter for offensive words. You can change your name once right away, then at most once every 7 days. Each change you make is recorded with your account, old name and new name, so we can deal with abuse. That record is deleted with your account.

Your coach name is public. Don't use your real name or anything else that could identify you.

You also pick a favorite team, a team logo for your profile and up to 8 cards to show off. The game picks those cards until you do.

Your age

Before you create a coach, the game asks your date of birth. You must be 13 or older to play. The date itself stays on your phone and is never sent to us.

When you create your coach, the game sends our servers three things: that you passed the check, an age range worked out from your date of birth (13–17, 18–24, 25–34, 35–44, 45–54, 55–64 or 65+), and which version of our Terms of Service and this Privacy Policy you agreed to. We store them with the time.

The age check keeps players under 13 out. On version 1.2.0, the game also uses the date of birth on your phone to set up Google's ads code for your age (see Ads); without that date on your phone, it treats you as under 18. The age range on our servers isn't used for anything else.

We plan to sell sponsorships inside the game ourselves, such as a sponsor's name on a stadium scoreboard. If we do, the age range will let us show a sponsorship only to players 18 and over, and tell the sponsor how many players in each adult age range saw it. Counts only, never who. No sponsorships exist today, and no outside company receives your age range. On version 1.2.0, Google's ads code is told only whether to treat you as under 18 (see Ads).

If you're 13 to 17, we use your data only to run the game, keep it fair and safe, answer your emails, send the reminders you turn on and the sign-in codes you ask for, and, if you joined our waitlist, send waitlist emails. Any sponsorship aimed by age would leave you out. On version 1.2.0, RevenueCat's purchase code and Google's ads code still start on your phone (see Purchases and Ads), and Google's code can collect data for Google. It's set to treat you as under the age of consent and to ads rated PG or lower, and on iPhone and iPad the game never asks you for Apple's tracking permission. On Android, it can still get your advertising ID unless you delete it in your phone's settings.

What other players can see

  • On your profile: your coach name, favorite team, profile logo, showcase cards and their levels, Immortal level, squad and your role in it, how many friends you have, how many games you've played in each mode, and when your account was created (the game shows the month and year).
  • On leaderboards: your coach name and points. Event boards also show how many games you've played.
  • On squad pages: your coach name, favorite team, role, when you joined the squad, and the points you've earned for it this cycle.
  • In other players' inboxes: your coach name, when you send someone a friend request, or when you apply to join a squad (its COACH and CAPTAINS see it).

Any player can open any profile and any squad page. Their game also receives your account ID, which is how it opens your profile, and the exact time your account was created.

Anyone with a game account who knows how can also read squad membership straight from our database, without using the game. Those records show your account ID (not your coach name), your role, whether it's your first squad and when you joined the squad. A squad's own record also shows its leader's account ID. The record of when each of your squad points was earned can be read that way only by your own account.

Our servers can also put together a feed for each squad, and only that squad's current members can ask for it. The game doesn't show it yet, but a member who knows how can ask our servers for it, going back up to 7 days. It lists each current member's Ranked, Blitz, event and Quick Sim results (such as wins, losses, scores and points), their mini-game results that earned a medal (with the score and difficulty), the Road hero cards they claimed and their Ranked promotions, including ones from before they joined the squad. It also lists the squad's activity records (see What our servers store). Each entry shows the exact time and, if it's about a player, that player's account ID. Entries for current members also show their coach name, profile logo and favorite team. Activity records of players who have left the squad show only their account ID.

What our servers store

For each account, our servers keep:

  • Your account ID and when the account was created.
  • If you link your account to a sign-in: the Apple, Google or email details listed under Your account, when you linked each one, and when you last signed in with it.
  • Your coach name, past coach names, favorite team, profile logo and showcase.
  • If you passed the age check, your age range and when you passed it. Also which version of our Terms of Service and this Privacy Policy you agreed to, and when. The game sends the age details once, when you create your coach, and your agreement each time you agree. If it couldn't reach our servers at that moment, we may not have them.
  • A running log of everything that earns or spends something in the game, each with the time it happened: match results, rewards, pack openings, currency, XP, card upgrades, exchanges, coach name changes, finishing the tutorial, locking and unlocking cards, and test grants of dollar-priced items given earlier in the beta.
  • Your matches: when they started and finished, the game version, the random seed our servers issued, and a summary of the result, such as the score, drive-by-drive or attempt-by-attempt results, the cards you used and, for games since 9:50 a.m. Eastern Time on October 16, 2026, each card's stats from the game (its career stats). Nothing you type and nothing about your device goes in.
  • Squads: which squad you're in, your role, the points you earn for it and when, and a history of joins, leaves, role changes and boots, including ones you made. For a squad you run, also its name, abbreviation, description, Discord invite code, colors and logo style.
  • While you're in a squad, an activity record of Rare-or-better cards you get (which card and where it came from), event entries and top-10 event finishes. The records stay with the squad if you leave. The game doesn't show them yet, but the last 7 days of them are in the squad's feed (see What other players can see).
  • Your friends, and the players you've blocked.
  • Reports you file: which player or squad you reported, when, and whether our team has closed the report.
  • Moderation records: any suspension from the social features on your account and when it ends, and any notes our moderators add to your account. Both are deleted with your account. Reports other players file about you, and how we resolved them, are kept too, as described under Deleting your account and data.
  • Event entries: entry fees, points, games played and the lineup you used.
  • Your inbox: game messages, rewards, invites and friend requests, and whether you've read, claimed or deleted them.
  • If you turn on reminders (on version 1.2.0, in Settings → NOTIFICATIONS → REMINDERS): the push token Expo gives the game on your phone, whether it's iOS or Android, the game's version, your phone's time-zone offset from UTC, when the game last checked in, and whether we've been told the token stopped working. Also a record of each reminder we send you: what it said, which token it went to, when we sent it, whether it was delivered and whether you tapped it.
  • A Founders Pass (the premium row of the season pass), if we've given you one.

Our game servers and database run on Supabase. The database is in the United States, so if you play from another country, your data is stored there.

What stays on your phone

  • The key that signs in to your account, in your phone's secure storage.
  • A second random ID that never leaves the phone. The game uses it to pick your suggested coach name. It's in secure storage, and also in the game's private storage.
  • Your date of birth, which version of our Terms of Service and this Privacy Policy you agreed to, your settings, and a copy of your game data so the game loads fast and works offline. These are in the game's private storage, which other apps can't read. The game doesn't add its own encryption on top of your phone's.
  • Your lineups (apart from event lineups, which our servers also keep). They live only on your phone, so they don't come back after a reinstall and don't move with you when you sign in on another phone. Neither do card career stats from games played before 9:50 a.m. Eastern Time on October 16, 2026. Win-loss records, Ranked season points, this week's Blitz progress and boosts, unopened packs in your pack tray, your place in the 28-day login calendar and card career stats from later games are also kept on your phone, and the game rebuilds them from the records our servers keep.
  • If you've switched between coaches on this phone: each other guest coach's account ID and key, and its coach name, profile logo, favorite team, number of cards and win-loss record, in secure storage, so you can switch back (see Your account). On iPhone and iPad they usually survive deleting and reinstalling the game.
  • If you turn on reminders, on version 1.2.0: your push token, in the game's private storage. Expo's notification code also creates another random install ID and keeps a record of the last push token it sent Expo. On iPhone and iPad, those two are in secure storage and survive deleting and reinstalling the game; on Android, uninstalling removes them.
  • On version 1.2.0, the code from RevenueCat and Google keeps its own records on the phone, such as RevenueCat's copy of your account ID and what RevenueCat last told the game about your purchases, Google's consent record (including your answer if you saw its consent message), and, if you used Google sign-in, the Google account you last signed in with. On Android, Google's Firebase messaging code also keeps its own install ID and push token.
  • A random install ID that Expo's update system creates (see App updates).

Deleting your account in Settings wipes all of this except what Expo's code keeps (its install IDs and its record of your push token), the other guest coaches on the phone, and the records RevenueCat's and Google's code keep for themselves. Each guest coach is a separate account: to delete one, switch to it and delete it too.

What we don't collect

The game never asks to use your phone's location, contacts or photos. Our own code doesn't add your phone's advertising ID or model to anything it sends. The game tells Expo whether your phone runs iOS or Android when it checks for updates (see App updates) and, if you turn on reminders, tells Expo and our servers too (see Messages and notifications). On version 1.2.0, Google's ads code can collect your phone's advertising ID and other details about your phone (see Ads), and RevenueCat's purchase code sends your phone's model and operating system, but not its advertising ID (see Purchases).

Two things reach our servers anyway, as they do for any app that goes online:

  • Your IP address, each time the game connects.
  • A standard header your phone attaches to every web request. On iPhone and iPad it names the game, its build number and the version of iOS; on Android it names only the networking software the game uses.

Supabase can record both in its sign-in records and system logs. We don't use them to work out who you are or where you are. We haven't yet confirmed how long Supabase keeps those records.

App updates

The game checks Expo's servers for updates when it starts, when you come back to it after at least 10 minutes away, and when you tap CHECK FOR UPDATE in Settings → ABOUT. Each check sends Expo your IP address, the standard web-request header, the install ID above, whether you're on iOS or Android, and which app and update versions you have. If the game crashed the last time it ran, the check also includes the error message.

Expo uses this to deliver updates, and to show us totals for each update, such as how many phones installed it, how often it was opened and how often it crashed. Those totals aren't tied to your game account. Expo handles this data under its own privacy policy.

On iPhone and iPad, the install ID resets when you reinstall the game. On Android, your phone's own backup can restore it.

Crash reports and analytics

We haven't added a crash-reporting or analytics tool to the game. Some companies still see crash or usage data from it: Expo, through its update totals (see App updates); Apple through TestFlight, and Google through Google Play (see Beta testing); and, on version 1.2.0, RevenueCat, whose purchase code contacts RevenueCat each time the game starts and again from time to time when you come back to it (see Purchases), and Google's ads code, once it starts (see Ads). Our own servers, run by Supabase, keep the game records listed under What our servers store.

We may add tools later, such as Sentry for crash reports or PostHog for gameplay analytics. Before either one collects anything, we'll add it to this page and the game will ask you to agree again.

Purchases

In the beta, no real money changes hands. Nothing in the game priced in dollars is on sale yet. Today that means the Diamond bundles, the Starter Kit, the Epic Mega Box, the Iconic+ Pack, the Titanium+ Pack and the Trait Tokens Mega Box in the Shop, Club Immortality and the Founders Pass. None of them is on sale, and nobody has been charged for one. Earlier in the beta, tapping a Diamond bundle, the Epic Mega Box, the Trait Tokens Mega Box or Club Immortality gave you the item as a test grant: nobody was charged, and no app store billed you. We haven't taken those items back, apart from Club Immortality test memberships, which have ended: they no longer double any reward. Our servers keep each test grant in the log of everything you earn and spend, with the item and its listed price. We may give the Founders Pass to testers.

Version 1.2.0 of the game includes RevenueCat, the service that will check purchases once they're on sale. It doesn't start until you've agreed to our Terms of Service and this Privacy Policy, and never on a phone where the age check stopped someone under 13. After that, the game contacts RevenueCat each time it starts, and again from time to time when you come back to it. It sends RevenueCat your account ID, which platform you're on, your phone's model (and, on Android, its brand) and operating-system version, the game's version (and, on iPhone and iPad, its build number), whether it's a test build, your phone's language and region settings, and the country of your App Store or Google Play account. On iPhone and iPad it also sends an ID that Apple gives our apps on your phone (Apple calls it the identifier for vendor), and whether Apple's tracking permission for the game is allowed, not allowed or not asked yet. RevenueCat also sees your IP address, as any online service does. It doesn't receive your name, your email address or your phone's advertising ID.

On version 1.2.0, Settings → ABOUT also has a RESTORE PURCHASES button. If you tap it, the game asks your App Store or Google Play account for this game's purchases and passes what it finds to RevenueCat. Nothing can be bought yet, so there's nothing for it to bring back.

RevenueCat keeps a record under your account ID with details like these and when the game last connected to it. When you delete your account, we ask RevenueCat to delete that record too (see Deleting your account and data).

When real purchases start, they'll go through Apple's App Store or Google Play and RevenueCat will check them. We'll update this page first, and the game will ask you to agree again.

Ads

There are no ads in the game today: the game never shows an ad, and our code never asks Google for one.

Version 1.2.0 of the game includes Google's ads code (the Google Mobile Ads SDK) and Google's consent code, so that ads can be switched on later. Neither runs on older test builds. On version 1.2.0 they don't start until you've agreed to our Terms of Service and this Privacy Policy, and never on a phone where the age check stopped someone under 13.

For this, the game goes by the date of birth on your phone. If the phone has none, for example after a reinstall that brings your account back, or when you sign in on a new phone without creating a coach there, the game treats you as under 18. Google isn't told your date of birth or your age range.

After that, each time you start the game:

  • Google's consent code checks with Google whether the privacy rules where you are need your consent. If you're 18 or older and in the European Economic Area (EEA), the UK or Switzerland, you may see Google's consent message. If you're under 18, you won't.
  • On iPhone and iPad, if you're 18 or older, the game asks once for Apple's tracking permission (App Tracking Transparency), and Google's consent code may show a short message about it first. If you're under 18, you're never asked.
  • Google's ads code starts, if Google's consent code allows it. It's set to ads rated T (teen) or lower. If you're under 18, it's set to ads rated PG or lower and to treat you as under the age of consent.

Once it starts, Google's ads code can send Google your IP address, which Google can use to estimate your rough location; details about your phone and the game; how you use the game, such as when you open it; identifiers for the game on your phone; and reports on how the game and the ads code perform, including crashes. On iPhone and iPad it can get your phone's advertising ID only if you allowed tracking. On Android it can get the advertising ID unless you've deleted it in your phone's settings. Google handles this data under its own privacy policy and says it can use it for advertising, analytics and fraud prevention.

Our own code never reads your advertising ID, and our servers never receive it.

Planned, and not in the game today: rewarded ads, short videos you can choose to watch for in-game rewards such as extra fuel, and an occasional full-screen ad between screens, never during play, that you don't choose to watch. Before any ad appears, we'll update this page and the game will ask you to agree again.

Beta testing

  • If you're on our waitlist, we email you when a spot opens (see This website).
  • On iPhone and iPad, the beta runs through Apple's TestFlight. To add you as a tester, we give Apple your name and email address so TestFlight can send the invite.
  • Feedback and screenshots you send through TestFlight, and crash reports from TestFlight builds, go to Apple, which shares them with us. Apple also shows us the name and email address you were invited with, which builds you've installed, how often you've opened them, and the device model and iOS version attached to any feedback or crash report. Apple handles all of this under its own privacy policy.
  • On Android, the beta runs through Google Play's internal testing, which has carried version 1.2.0 since October 20, 2026. To add you as a tester, we give Google the email address of your Google account, and Google Play delivers the game to your phone. If your phone shares usage and diagnostics with Google, Google Play can show us crash and performance reports from the game, including the phone model and Android version. Google handles all of this under its own privacy policy. Some testers may still have an older test build they installed from a download link hosted by Expo, which sees each download like any website visit, including the IP address.

Messages and notifications

There's no chat and no private messaging between players. The in-game inbox carries messages from us (news, patch notes, rewards) and automatic game messages (squad invites and applications, friend requests, squad notices and event results).

Push notifications are off unless you turn them on, and they need version 1.2.0. After you collect a reward, the game may show a card asking if you'd like reminders. Your phone asks for its permission only after you tap TURN ON on that card, or switch on REMINDERS in Settings (the gear on the Play screen) → NOTIFICATIONS. If you don't turn them on, the card can come back once more, at least a week later, and then not again. You can turn reminders on or off any time in Settings → NOTIFICATIONS → REMINDERS, and you can also turn them off in your phone's settings.

Reminders are only about the game: your daily login reward is ready; your Ranked, Blitz or Daily Challenge fuel is full; a new Blitz week has started, or the current one ends within the hour; an event you registered for in advance has opened; a reward is waiting in your inbox; a reward on the Road or your season pass is ready to claim; or you've finished a daily or weekly achievement. You get at most two a day, not counting inbox rewards, and none between 10 pm and 9 am in the time zone your phone was set to the last time you opened the game. If you haven't opened the game for 30 days, you get none.

To deliver reminders, your phone uses a push token from Apple (on iPhone and iPad) or Google (on Android). While reminders are on, each time the game starts (and sometimes again while it's open), it sends that token to Expo, the company whose service sends our notifications, along with which app it's for, whether it's an Apple or a Google token, a random install ID that Expo's notification code keeps on your phone and, as with any web request, your IP address. Expo gives back its own push token. The game then sends our servers the Expo token, whether you're on iOS or Android, the game's version and your phone's time-zone offset, which is how we know when it's night where you are. To send a reminder, our servers give Expo the token, the reminder's text and which screen it opens, and Expo passes them to Apple or Google to deliver. When you tap a reminder, the game tells our servers. On Android, version 1.2.0 also includes Google's Firebase messaging code, which contacts Google when the game starts to set up push delivery, whether or not you ever turn reminders on, and before the game asks your age. The game passes that token on to Expo and our servers only if you turn reminders on.

After reminders have been on once and your phone has allowed them, Expo's notification code also sends Expo your phone's current push token and its install ID from time to time when the game starts, even after you turn reminders off or delete your account. On Android, uninstalling the game stops this. On iPhone and iPad, Expo's code keeps its record in your phone's secure storage, so it starts again if you reinstall the game.

The only email the game sends is the six-digit code you ask for when you add an email address to your account or sign in with one. It comes from GAK Games (noreply@immortals.football). Resend, our email delivery provider, sends it for us, so Resend receives the address and the email. Our servers keep the address with your account (see Your account).

When you email us

If you email support@immortals.football, we get your email address and whatever you send, such as your coach name, device model or screenshots. Cloudflare runs that address and forwards the email to a Google mailbox our team reads. We use it to help you. We don't delete support email on a schedule yet; ask us and we'll delete your messages.

How we use your data

  • To run the game and your account: signing you in, your collection, balances, matches, squads, friends and inbox.
  • To keep competitions fair: recording results, pack openings and balances, and looking into cheating.
  • To keep players safe: the name filter, reports, blocks, suspensions and the record of name changes.
  • To keep players under 13 out: the age check.
  • To fix problems, and to answer you when you email us.
  • On version 1.2.0, to get ready for purchases: RevenueCat's purchase code runs so it can check purchases once they're on sale (see Purchases).
  • On version 1.2.0, to get Google's ads code ready for the ads we plan to show later, set up for your age and with the consent and tracking choices described under Ads. The game doesn't show ads yet.
  • To send waitlist emails: beta invites and the occasional big update.
  • To send the reminders you turn on, and the sign-in codes you ask for by email.
  • To follow the law.
  • Later, for sponsorship counts by adult age range, as described under Your age.

How long we keep it

  • Your account and everything on it: until you delete the account. We don't delete inactive accounts on a schedule, including accounts that never finished setup and accounts no one can sign in to any more, such as a guest coach you signed out of.
  • Inbox messages sent to you personally: messages you delete are removed from our servers 7 to 14 days later. Messages you read that carried no reward, rewards you claim, and invites and requests you answer are removed 45 to 52 days after you read, claim or answer them. Unread messages, unclaimed rewards and unanswered invites and requests stay until you act on them.
  • Messages we send to every player: we keep whether you read, claimed or deleted them until your account is deleted.
  • Reminders: your push token and what the game sent with it, until you turn reminders off, sign out or delete your account. If you turn reminders off in your phone's settings, the game removes the token the next time you open it. If you delete the game with reminders on, the token stays with your account until the account is deleted, and we stop sending to it once Expo tells us it no longer works. The record of reminders we've sent you, which names the token each went to: until your account is deleted.
  • Squad activity records: the newest 100 for each squad.
  • RevenueCat's record for your account ID, on version 1.2.0: until you delete your account, when we ask RevenueCat to delete it (see Deleting your account and data).
  • Supabase's sign-in records, system logs and backups: we haven't yet confirmed how long (see What we don't collect).
  • Records Resend keeps of the code emails it sent for us: we haven't yet confirmed how long.
  • Support email: no set period yet (see When you email us).
  • The website waitlist: until you unsubscribe.

Deleting your account and data

You can delete your Football Immortals account in the game. Open Settings (the gear on the Play screen), go to ACCOUNT, tap DELETE ACCOUNT & START OVER, tap it again, then confirm with DELETE EVERYTHING. It needs a connection. It deletes your account and its data from our servers first; if that fails, nothing on your phone changes, and you can try again. Then it wipes the game's data from your phone (apart from the items listed under What stays on your phone), and the game starts over with a brand-new anonymous account. It deletes only the coach you're signed in as: if you've switched between coaches on this phone, each one is its own account, so switch to it and delete it too.

That removes from our servers: your coach name and profile, your age range and agreement record, the log of everything you earned and spent (and with it your balances and cards), your matches, event entries, squad membership and squad points, friends and blocks, reports you filed, your inbox, a Founders Pass if we gave you one, your phones' push tokens and the record of reminders we sent you, and any Apple, Google or email sign-in linked to the account. We also ask RevenueCat (see Purchases) to delete any record it holds for your account ID; if that request fails, the record can stay. Deleting doesn't tell Apple or Google, so they may keep listing the game among the apps you've signed in to with them. You can remove it yourself: for Apple, under Sign in with Apple in your Apple Account settings (on iPhone or iPad, Settings → your name → Sign-In & Security; the menu names differ between iOS versions); for Google, under your connections to third-party apps and services in your Google Account.

A few things stay after deletion:

  • The history of squads you joined and left, and of boots and role changes you made, under your old account ID with no name. It has no set end date; it keeps squad records and bans correct.
  • Reports other players filed about you, with no set end date, for player safety.
  • Squads you created or led, with the name, abbreviation, description and Discord invite code you wrote. Leadership passes to another member, if there is one.
  • Game messages in other players' inboxes that show your coach name and hold your account ID, such as a friend request or a squad application. Each is removed 7 to 14 days after that player deletes it, or 45 to 52 days after they answer it; one they never answer stays.
  • Squad activity records, with your account ID removed.
  • Supabase's sign-in records, system logs and backups, which can include your account ID, your IP address and, if you linked one, your sign-in email address, until Supabase clears them.
  • Any record Resend keeps of the code emails it sent you, until Resend clears it.

If you delete the game without deleting your account, or sign out of it, the account stays on our servers. If it's linked to Apple, Google or an email address, signing in brings it back on any phone that offers that sign-in. If it isn't, reinstalling usually brings it back on iPhone and iPad, but nothing brings back an unlinked account you signed out of.

If your account is linked to Apple, Google or an email address, you can sign in to it on any phone that offers that sign-in and delete it from Settings. If you can't get into the game (lost phone, uninstalled, or you don't want to agree to a new version), email support@immortals.football with your coach name. Coach names are public, so a name alone doesn't prove the account is yours. We'll reply and ask for details that do before we delete anything.

Your choices and rights

  • See or get a copy of your data: email us. There's no download button in the game. Once we've checked the account is yours, we'll send you what our servers hold about it.
  • Correct it: change your coach name, favorite team, profile logo or showcase in the game, or email us.
  • Delete it: see Deleting your account and data.
  • Stop all collection: delete your account in Settings, then delete the game. If the phone holds other guest coaches, switch to each one and delete it too. Deleting the account alone starts a fresh anonymous account: while the game is installed it checks for updates; on version 1.2.0, once the new account has passed the age check and agreed to our Terms of Service and this Privacy Policy, RevenueCat's purchase code and Google's consent and ads code start again; and if reminders were ever on, Expo's notification code keeps updating Expo with your phone's push token.
  • Waitlist emails: every email has an unsubscribe link.
  • Reminders: turn them off in Settings → NOTIFICATIONS → REMINDERS, or in your phone's settings.
  • Ads, on version 1.2.0: on iPhone and iPad, change the game's tracking permission in your phone's Settings → Privacy & Security → Tracking. On Android, open your phone's ads settings (often Settings → Privacy → Ads, or Settings → Google → Ads; the menus differ by phone) to delete or reset your advertising ID, or to opt out of personalized ads on older phones. If you saw Google's consent message in the EEA, the UK or Switzerland, change your answer with PRIVACY CHOICES in the game's Settings → ABOUT.

Wherever you live, you can make these requests by email. If you're in the European Economic Area (EEA), the UK or Switzerland, we rely on running the game you asked for, our legitimate interest in keeping it fair and safe, and your consent where we ask for it. You can also complain to your local data-protection authority.

Children

Football Immortals is for players 13 and over, and it isn't directed at children. The game asks your date of birth before you create a coach, and stops anyone under 13.

The game makes its anonymous account the first time it starts, before it asks anyone's age. When the game stops someone under 13, it deletes that account from our servers, the same way DELETE ACCOUNT & START OVER in Settings does (see Deleting your account and data), and removes the key to it from the phone. If the phone is offline at that moment, the account is deleted the next time the game opens with a connection. A phone the age check has stopped never makes a new account. The deleted account held no coach name, no age and no date of birth: only a random account ID, the time it was made and the starting balance. On version 1.2.0 there's one exception: if someone uses Apple or Google under HAVE AN ACCOUNT? SIGN IN on the CREATE YOUR COACH screen before the age check stops them, the game can link that sign-in to the account first. In that case the deleted account also held what that sign-in gave us (see Your account), and Apple or Google saw the sign-in.

Earlier versions of the game left that empty account in place. The game now deletes it the next time it opens with a connection on that phone. Until then, or if the game is never opened again, that empty account stays on our servers.

The phone keeps the date of birth that was entered and a note that the age check stopped it, so the game stays stopped. Neither is sent to us. On Android, version 1.2.0's Firebase messaging code still contacts Google when the game starts, even on a phone the age check has stopped (see Messages and notifications). Supabase's sign-in records, system logs and backups (see What we don't collect) can still hold the deleted account's ID, the phone's IP address and, in the exception above, the sign-in's email address, until Supabase clears them.

If you think a child under 13 has created a coach, email us the coach name and we'll delete the account.

Security

Everything the game sends to our servers is encrypted in transit (HTTPS). The key that signs in to your account is kept in your phone's secure storage. On our servers, your records can be read by your account, our server code and our team. Other players see only what's listed under What other players can see, including the squad records and the squad feed described there. No system is perfectly secure.

This website

immortals.football collects one thing from visitors: your email address, if you join the beta waitlist. Buttondown, our email provider, runs the list. Signups are double opt-in, and every email has an unsubscribe link.

We use the list to send beta invites and the occasional big update about the game. We never sell it. We pass an address on only to invite you to the beta: to Apple, so TestFlight can send the invite, or to Google, to add you as a tester on Google Play if you play on Android. Unsubscribing removes you from the list.

The site sets no cookies and runs no analytics or ad trackers. Cloudflare hosts it, so Cloudflare handles each visit, including your IP address, to deliver and protect the site. Cloudflare may also receive network error reports from your browser, and it adds a small script to pages that show an email address, to hide the address from spam bots. The site also has a private upload page our team uses to send us game art; it isn't for visitors.

Do Not Track: this website doesn't track you across other companies' sites or let other companies do so, so a browser's Do Not Track signal has nothing to switch off here. The game shows no ads yet, but on version 1.2.0 Google's ads code can collect your phone's advertising ID, which lets Google recognize your phone across apps: on iPhone and iPad only if you allow tracking when the game asks, and on Android unless you delete the advertising ID in your phone's settings (see Ads).

Who we share with

These companies handle data for us, or receive it through the game, each for the job listed:

  • Supabase: our game servers and database, including sign-in.
  • Expo: app updates; sending the reminder notifications you turn on (Expo's push service sees your phone's push token and the text of each reminder; see Messages and notifications); and the download link for the older Android test build.
  • Apple: TestFlight, which delivers the beta on iPhone and iPad. We give Apple the name and email address we invite you with. Apple also delivers reminder notifications to iPhones and iPads, if you turn them on.
  • Cloudflare: hosting this website, and handling email sent to support@immortals.football.
  • Google: Google Play, which delivers the beta on Android (we give Google the email address of your Google account to add you as a tester, and it can show us crash and performance reports); delivering reminder notifications to Android phones, if you turn them on; on Android in version 1.2.0, Google's Firebase messaging code, which contacts Google when the game starts to set up push delivery, even if you never turn reminders on (see Messages and notifications); on version 1.2.0, its ads code and consent message, which start only after you've agreed to our Terms of Service and this Privacy Policy (never on a phone where the age check stopped someone under 13) and run now, though the game doesn't request any ads yet (see Ads); and the mailbox where support email arrives.
  • Apple and Google: signing you in, on version 1.2.0, if you link your account to them. They see when you use them to sign in to the game.
  • RevenueCat: checking purchases once they're on sale. Its purchase code has been in the game since version 1.2.0, starts only after you've agreed to our Terms of Service and this Privacy Policy (never on a phone where the age check stopped someone under 13), and already receives the details listed under Purchases. No purchases go through it yet.
  • Resend: sending the one-time codes you ask for when you add an email address to your account or sign in with one, from noreply@immortals.football. It receives the email address and the email.
  • Buttondown: the website waitlist.

Planned, and not in the game today:

  • Apple's App Store and Google Play: taking payment for real-money purchases, which RevenueCat will check.
  • Google AdMob ads: optional rewarded ads, and occasional full-screen ads between screens. Google's ads code is already in version 1.2.0 of the game (see the list above); the ads aren't.
  • Sentry and PostHog: crash reports and gameplay analytics.

Before any of these starts, we'll move it to the first list with what it receives, and the game will ask you to agree again.

Each of these companies has its own privacy policy and handles your data under it. We don't sell your data. On version 1.2.0, Google's ads code can collect data that Google can also use for its own advertising (see Ads). Your phone's tracking and advertising ID settings decide whether it can get your advertising ID.

We'll also hand over data if the law makes us, such as under a valid court order, or when we need to in order to stop fraud or protect someone's safety. If Gak Games LLC or Football Immortals is ever sold or merged, your data would go to the new owner, who would have to follow this policy, and we'd tell you in the game first.

Changes to this policy

When this policy changes in a way that matters, such as a new company, a new kind of data or a new use, we'll update this page, change the date at the top, list the change under What changed, and the game will ask you to agree to the new version before you keep playing. Test builds older than version 1.2.0 no longer get updates, so they can't ask.

Earlier versions stay readable at their own addresses: the October 16, 2026 version and, before it, the July 9, 2026 placeholder.

Contact

Privacy questions and requests: support@immortals.football.