1. This Website
The marketing pages on globalconflict.co.za, including this one, are plain static pages. They set no cookies at all and load no third-party scripts, fonts or tracking pixels.
They store nothing in your browser either. While you are on a page, it
works out where you arrived from (for example that you came from a Facebook ad, or from a
Google search) and adds that to the links on the page, both to our other pages and to the
Game, so that if you go on to create an account it can be counted against the right source.
Nothing is kept once you leave the page. If an earlier visit stored a value called
gc_acq on this site, it is removed.
2. The Browser Version of the Game
The playable browser app at play.globalconflict.co.za stores data on your device. Most of it uses your browser's local storage rather than cookies, and is strictly necessary to run the Game:
- Your login session. A signed token so you are not asked to sign in on every screen. Removed when you sign out.
- Your settings. Small preferences such as whether you have already been shown the first-launch prompts.
- A cached copy of the game artwork. Held in the browser cache and by the offline service worker so the app loads quickly and works on a poor connection.
None of the above is shared with anyone, used to track you across other websites, or used for advertising.
Where you arrived from. If you accept the cookie banner, the Game also
stores one value in your browser's local storage, under the name gc_acq: where
you first arrived from (for example a Facebook ad and which one, or a Google search). It is
recorded once, on the first visit after you accept, is not updated afterwards, and is sent
with your account when you create one, so that we can tell which ads and channels bring
players who go on to enjoy the Game. It is not shared with anyone. If you do not accept, it
is never stored: the Game only reads the source from the link you arrived through, keeps it
in memory, and sends it once if you create an account during that visit. If you decline, or
later withdraw your consent, any gc_acq already stored is removed.
The Game also uses one advertising cookie, the Meta Pixel (run by Meta, the company behind Facebook and Instagram), so we can see whether the ads we run on those platforms actually bring players to the Game. It is not loaded until you accept it in the cookie banner shown the first time you open the Game in a browser; if you decline, it never loads and no advertising cookie is set. It tells us things like which ad you clicked and whether you went on to create an account, and it may set a cookie Meta uses across sites that also run the Pixel. We do not use it to collect anything beyond that, and we have no way to see your general Facebook or Instagram activity through it. See Meta's own Privacy Policy for how they handle Pixel data on their side.
Rewarded ads (Google AdSense). The Game shows no ads unless you choose to watch one, for example to swap a Daily or Weekly task. Nothing from Google's ad service loads until you make that choice. When you do, Google loads its ad script, which may set cookies Google uses to serve and measure ads, limit how often you see the same ad, and prevent fraud. The first time, Google's own consent message asks whether ads may be personalised, where the law requires it; that choice is held by Google and is separate from the Meta Pixel banner. Players aged 18 or under are never shown personalised ads. See how Google uses cookies in advertising.
3. Managing Your Cookie Choice
The first time you open the browser game, a banner asks you to Accept or Decline the Meta Pixel. Declining still lets you play; it only stops that one cookie from being set. Your choice is remembered on that device so the banner does not ask again.
When you sign in, your choice is saved to your account, together with the date you made it and the version of this policy you made it under. From then on your account's choice applies on every browser you sign in on.
To change your mind later, open Settings in the Game and choose Manage Consents. A change takes full effect the next time you reload the page. Clearing this site's data in your browser forgets the choice on that device only; your account's choice is applied again when you sign in.
If we change this policy in a way that affects the Meta Pixel, a choice made under the earlier version no longer counts, and we ask you again.
4. The Android App
The Android app does not use cookies and does not carry the Meta Pixel. It stores your session and settings in the app's own private storage on your device, and the downloaded artwork in its cache directory. Clearing the app's data or uninstalling it removes all of it.
If you choose to watch a rewarded ad in the Android app, Google AdMob serves it and may use your device's advertising ID. Google's consent message asks first where the law requires it, and you can reset or delete the advertising ID in your phone's Google settings at any time.
5. Third Parties
A few third-party services may set their own storage when you actively use them:
- Meta Pixel, described in section 2 above, only in the browser version of the Game and only once you accept it.
- Google AdSense and Google AdMob, described in sections 2 and 4 above, only when you choose to watch a rewarded ad.
- Google Sign-In, if you choose to sign in with a Google account.
- Firebase Cloud Messaging, if you enable push notifications, which registers a token for your device.
Those are governed by the relevant provider's own policies. We receive only the account identifier, the push token, or the ad-performance data described in our Privacy Policy.
6. Clearing It
You can clear everything the browser app stores at any time through your browser's settings for this site. If the browser app ever gets stuck at the login screen, we host a one-click reset that clears the saved session, the caches and the service worker: play.globalconflict.co.za/?r=1. Clearing this data signs you out. It never deletes your account or your progress, which live on our servers.
7. Contact
Questions go to our Discord server, which is our support hub.
Last updated: 19 October 2026.