Privacy policy

Last updated: 4 November 2026

XENOPOLIS is a sci-fi war game for one player, made for Android phones. This policy explains, in plain words, what happens to your data when you play. It also covers our website, xenopolis.gazum.ai.

The short version

• Your save stays on your phone. We never receive it.
• There's no account. The game never asks for your name or your email.
• An AI writes the War Dispatch only if you say yes. Then our server sends OpenAI a short summary of your war: game facts, with no ID.
• Usage stats use a random number, and you can turn them off in Settings.
• Delete my data, in Settings, erases what our server holds under that number.
• No ads. We don't sell data.

Who we are

XENOPOLIS is made by GAZUM, Corp., 7345 W Sand Lake Rd, Ste 210, Orlando, FL 32819-5280, United States ("we", "us"). Contact: support@gazum.ai.

What stays on your phone

Your save and your settings stay on your phone, including your city, your fleets and your battle replays. We never receive them.

• Rivals. Rivals are game AI, run by the game on your phone. The War Dispatch is the only thing that uses an AI model.
• Notifications. If you allow them, the game schedules them on your phone. They don't pass through our server or any push service.
• Google backup. If Google backup is on for your phone, Android may copy your save to your own Google account, and put it back if you install the game again. Google runs that backup under its own terms, and we can't read it.

What reaches our server

Of what the game sends, our server keeps only what this section lists, plus the log lines and daily totals under How long we keep it. Network data, below, covers what else it sees.

The War Dispatch, only after you say yes

The first time a Dispatch is due, the game asks you. If you choose Use the AI Dispatch, the game sends our server a short summary of your war, at most once a day.

The summary holds only numbers, times, yes-or-no flags and fixed words from the game:

• the day, the language, your world and its spirit, and tomorrow's world;
• the latest raid: which rival, when, the result, how many ships fell, what you lost, how much of your defense was wrecked, what your depot lost, whether the Crown fired and whether you took command;
• your hunts: which world, which rival, what kind of hunt, the result, and whether you broke through or captured the target;
• your feud with a rival, your Crown's stage and charge, your Command level, your colonies and the Invasion;
• what's coming up next, with its time;
• a few events from a fixed list, such as a truce that held.

It doesn't hold your name, any text you type or any ID, and it doesn't carry your random number. Our server refuses any summary with an unknown field or word, so words from outside the game can't reach the AI model.

Our server sends the summary to OpenAI, whose model writes the headline and the text. Before the text goes back to your phone, we check its length, its words and its numbers on our server, and OpenAI's moderation service checks it too. If the text fails, you read a field report written on your phone instead.

Our server keeps the summary and the text, or the failed text and why it failed. We keep them to reuse a text when the same summary comes again that day, to read a Dispatch someone reports, and to check how the AI's text is working. Since the summary has no ID, we can't tell whose it is. If two phones send exactly the same summary on the same day, the model writes once and both phones get the same text.

If you choose Offline reports only, or don't answer, the game makes no call for a Dispatch, and you read field reports written on your phone. You can change your answer at any time in Settings, under War Dispatch AI.

Legal basis (EEA and UK): your consent.

Usage stats

Usage stats are on unless you turn them off in Settings, under Usage stats. We use them to find bugs, to see how the game runs and to count how many players come back. Each record holds:

• a random number, made once by the game on your phone. It doesn't come from your phone's hardware, from Google or from an advertising ID;
• the app's version;
• what happened and when: the game opening, the steps of the first session, the end of a battle (its kind, its result and its length in seconds), a recovered save, a graphics failure, and an AI text that failed the checks on your phone;
• how it runs: the graphics tier, frames per second and load time;
• error messages: the message, the file and the line. We cut each message to 300 characters and blank anything that looks like an email or a network address.

Our server also keeps the first and last day it saw the number, so it can count how many players come back after a day and after a week.

Legal basis (EEA and UK): our legitimate interest in fixing and improving the game, kept to these few records, with a switch to turn them off.

Reports

If you tap Report on a Dispatch, the game sends our server which Dispatch it was and your reason: Offensive, Wrong facts, Makes no sense or Something else. Our server keeps those with the time of the report, with no random number and no ID of yours, to handle the report and to check how the AI's text is working. It may also email the reason and the reported text, with its language, its date and the Dispatch's id, to our support inbox, so that we can read it.

Legal basis (EEA and UK): our legitimate interest in keeping the AI's text safe and correct.

The game's switches

When it has a connection, the game asks our server for its current switches and the time: whether the AI Dispatch and Usage stats are on, and the oldest version we support. That call carries the app's version and no ID, and our server stores nothing from it, apart from the log line described under How long we keep it.

Deleting

Delete my data sends the random number, so that our server can erase what it holds under it. See Deleting your data.

What we never collect

Your name, your email, your contacts, your precise or approximate location, your advertising ID, your photos, or anything you type. The game has no sign-in and no chat, and it doesn't ask for permission to reach any of these. If you choose to write to us, we get the address you write from: see When you write to us.

Network data

Like any server, ours sees your IP address to answer. We don't store it, we don't log it, and we don't use it for location. It also sees the standard headers any web request carries, such as your language and the user agent, which can name your phone's model. We don't store those or log them either. OpenAI never sees your IP address or these headers, because the call to OpenAI comes from our server, not from your phone.

Legal basis (EEA and UK): our legitimate interest in answering the game's calls.

This website

xenopolis.gazum.ai is a small static site. Amazon CloudFront delivers its pages, and sees your IP address to answer, like any server. The site sets no cookies, has no analytics and loads nothing from other companies, and we keep no log of visits.

When you write to us

If you write to support@gazum.ai, we use your address and your message only to answer you and to do what you ask, and keep them for as long as we need them for that, or to show how we handled a request about your data.

What others can see

Nothing from the game. XENOPOLIS is played alone: it has no profiles, no chat and no public boards.

Who processes your data for us

• OpenAI (United States) writes the War Dispatch and moderates its text, only if you said yes. It receives the summary, our instructions to the model and the finished text, never your random number or your IP address. We ask OpenAI not to store the response. Data sent through its API isn't used to train its models. OpenAI may keep it in abuse-monitoring logs for up to 30 days, or longer if the law requires it or if that's reasonably necessary to protect its services or anyone else from harm. What OpenAI says about API data.
• Amazon Web Services (United States) hosts our server, its database and its logs in its us-east-1 region, delivers this website through CloudFront, and sends the report emails to our inbox.
• Cloudflare (United States) runs the DNS of our website's domain, and forwards the email sent to support@gazum.ai to our mailbox at Microsoft (United States).

Each of these providers processes your data only to provide its service to us, under its data processing terms. When your data leaves the EEA or the UK, it is protected by the European Commission's Standard Contractual Clauses or the EU–US Data Privacy Framework.

We don't sell data, and we don't share it with anyone else. Google runs Google Play, where you get the game, under its own privacy policy. It shows us totals, such as installs and crash rates, that don't name you.

How long we keep it

• Usage stats: 90 days for each record.
• The first and last day a number was seen: 90 days after the game last opened with that number.
• Dispatch summaries and texts, failed ones too: 30 days.
• Reports: 90 days. The email of a report stays in our support inbox for as long as we need it to handle the report.
• Our server's logs: 30 days. Log lines hold the route, the answer's code, the time it took, counts and short codes. When an AI text fails, a code can quote the number, time or word that failed. AWS adds its own lines, with the call's request id, how long it ran and how much memory it used. A log line holds no IP address and no random number. A line about a report holds the Dispatch's id and the reason.
• After that, only daily totals, such as how many battles ended that day. They hold no ID, and we keep them with no end date.

AWS removes expired records within a few days of these dates.

Deleting your data

In the game: open Settings, then Delete my data. It erases everything our server holds under your random number, at once, and the game makes another random number. If your phone is offline, the request waits until it connects. Your save stays on your phone. To erase the save too, use Start over.

What can't be picked out. Dispatch summaries and reports carry no ID of yours, so we can't tell which are yours. They age out: summaries in 30 days, reports in 90. Daily totals hold no ID and stay.

By email: you can write to support@gazum.ai, but we hold no name or email to look you up by. Send us the number that Settings shows under Your random number, and we can find what our server holds under it. Without that number we can't find your records from an email, and we'll point you to the Settings option above.

Uninstalling removes the save and the random number from your phone, apart from any copy of the save in your own Google backup. What our server holds under that number can then no longer be tied to your phone, and it ages out in 90 days.

Your rights

Depending on where you live (for example in the EEA, the UK or California), you can ask to access, correct, delete or receive a copy of your data, object to how we use it, and withdraw your consent. You can withdraw your consent to the AI Dispatch at any time in Settings: you'll keep playing, with field reports written offline. You can turn off Usage stats in Settings too, and Delete my data erases what our server holds under your random number.

For anything else, write to support@gazum.ai; we answer within one month. To get a copy of what our server holds, or to correct it, send us the number that Settings shows under Your random number. We can't tell from an email alone which records are yours, as Deleting your data explains, so without that number we can't do it, and our answer will say so. You can also complain to your data protection authority.

Children

XENOPOLIS is not meant for children under 13, or under the age of digital consent where they live (up to 16 in some EEA countries). We don't knowingly collect their data. If you believe a child is using the game, tell us. Because we hold no name or age, we can't find that child's records from an email. To erase what our server holds, use Settings, then Delete my data, on that phone.

Security

Connections to our server are encrypted (HTTPS only). Our database isn't public, and AWS encrypts it at rest. The key we use to call OpenAI stays in AWS Secrets Manager: it's never in the app.

Changes

We post any change here, and the date above shows the latest one. If a change is big, we show it in the app.