Draft

Privacy policy

1. Who this is about

Bakery Wars is a mobile game published by Omega Software Solutions LLC, which is the company responsible for the personal data described here. This policy covers the game, the server it talks to, and this website. Write to support@bakerywars.com about anything in it, including asking for your data to be deleted.

2. What the game holds about you

• An account row. The game signs you in as a guest. The device holds a credential, the server holds an account identified by a generated number, and no name, email address or phone number is asked for.
• An email address, if you ever sign in with Google or Apple. The game does not offer that today. If a later build offers it and you use it, the game stores the address that Google or Apple hands it. It also builds your public display name out of the part of the address before the @, with four random characters added, so an address starting dev becomes a name like dev-a3f9 that other players can see. You can change that name afterwards. Deleting the account destroys the stored address and the link to the provider.
• Your game state. The bakery name you typed, coins, crystals, stock, prices, plots, guild membership, letters and the record of what you did on the block. This is the save file, and it lives on the server rather than on your phone, which is what stops anyone cheating you.
• Things other players can see. Your bakery name and display name, your storefront, your share of a block, your guild, and your appearances in the Crier. The market is the exception and it is deliberate: no market endpoint returns a user id, a display name, or a stable pseudonym, so trading there is not attributable to you by anyone, including other players.
• Where you signed in from. Every sign-in, every time the app renewed the sign-in, every sign-out and every failed attempt is written down with the IP address and the browser or device string the request carried. The address is also kept on its own as an account-and-address pair, so that two accounts trading with each other from one place can be spotted on the exchange. That pairing is the only fingerprint the game has: it takes no device fingerprint, and the column that would hold one has nothing writing to it.
• How far your clock is from UTC. The app sends the server one number: the minutes between your clock and UTC. It sends it when it starts and again whenever you come back to it. That number is minutes, not a place. The game asks for no location permission and gets no location. It is still a rough pointer at which part of the world you are in, which is why deleting your account sets it back to zero. It is there so that something due at ten past six arrives at ten past six where you are.
• What you do in the game. The app writes down named events. It finished starting up, you reached this step of the opening, you opened a letter, you signed out. It sends them in batches, and each batch carries a per-install identifier, a per-launch session identifier, how many times the game has been launched on this install, the platform name and the app version. Each event can also carry a few details of where in the game it happened: which bakery, which city, which neighbourhood, and for a family letter which letter it was, its mood, which part of the story it belongs to, and the reply you chose. None of it carries anything you typed. The naming screen sends the length of the bakery name you chose and never the name. All of this is there to make questions like “how many people finish the opening” answerable. It is on, and there is no setting that turns it off.
• Ordinary server records. Requests reaching the server carry an IP address and a client version, as every internet request does. The two entries above are where any of it is kept on purpose rather than in passing.

How long each of these is kept. Your account and your game state are kept for as long as the account exists, and section 8 says what deleting it destroys. The records with a clock on them age out on their own, whether or not anyone asks. The server does the deleting itself, once an hour.

• What you do in the game: 180 days. Six months is two full quarters, which is the span these events are actually read over — how many players finish a first bake, and how many of them come back. Nothing needs them after that.
• The account-and-address pairs: 90 days. Counted from the last time an address was seen, not the first. Sign in from an address again and its 90 days start over; stop, and the record goes.
• What the store tells us about a payment: 180 days. When you buy crystals, the store sends the server a note about the payment and the server keeps it exactly as it arrived. For a card payment that note can carry the name and address you gave the store. Deleting your account empties it straight away. Otherwise it empties itself after 180 days, which is past the longest window a bank has to reverse a payment.
• Sign-in, refresh and sign-out records: 90 days. The same period, on purpose, so this log and the addresses above cover the same stretch of time rather than one outliving the other. A session itself is discarded 30 days after it expires or is signed out.

Section 8 says what deleting the account does to every item above. Everything that names you or lets anyone reach the account is destroyed or overwritten. More than two things survive that, and section 8 names each one and says why.

3. Purchases

If you buy crystals, the store processes the payment. Google is the merchant; the game receives a receipt to verify and a record that the purchase happened. Card numbers never reach this game or its server. No purchase in the game resolves at random, so there is no odds disclosure to make.

4. What is not done with it

Game data is not sold, and it is not passed to advertisers or data brokers. The one lawful reason to hand any of it to a third party would be a valid legal demand, and this section will say so plainly rather than hiding it in a clause about partners.

5. This website

This website asks you for nothing. There is no box for an email address and no mailing list. Section 2 lists everything the game holds about you, and none of it is collected on these pages.

The host that serves the site keeps its own request logs, in the ordinary way of web hosts. That is all that happens here.

6. Children

The game is PG-13 in tone and is not directed at children under 13. Its age rating is set by the store, from a questionnaire the store asks. The rating is shown on the store listing rather than here, because the listing is the copy that stays current.

7. What this draft cannot promise yet

Written down here rather than left out, because this is the part a reviewer would find anyway.

• No legal basis or jurisdiction is stated. GDPR and CCPA wording is for counsel to write, not for a developer to approximate.

8. Deleting your account

You can delete your account from Settings → Your account inside the game, or by asking, if you have already uninstalled. The deletion page has both routes and the full list of what goes and what stays. The short version:

• Every sign-in method, session, recorded IP address, install and session identifier, and every analytics event is destroyed — immediately, rather than waiting out the periods in section 2.
• Your display name, your bakery names and your signature-good names are overwritten — including the copies the game had already printed in the Crier, in other players’ inboxes, and on gifts still in transit.
• Anything you were holding is released back into the world: resting market orders are cancelled and the coins or goods they were holding come back, open bounties are refunded in both directions, and a guild you led gets a new leader.
• Trades and ledger entries stay, with no name on them. This is the one thing an erasure here cannot take. Bakery Wars runs one shared economy, so every coin you held was the other side of somebody else’s deal, and removing your half would rewrite their books.
• Purchase records stay, because tax and refund rules need the fact that a purchase happened, and because a store refund can arrive days later and has to find something to reverse. Our copy of the receipt is emptied, and so is the note the store sent us about the payment. What is left is the date, the product and the amount. A payment that never reached your account, because it failed on the store’s side, has nothing in it saying it was yours, so we cannot find it to empty it. Those notes empty themselves after 180 days.
• A numbered row stays where your account was. Sixty-eight parts of the database point at that row and the books cannot balance without something to point at, so it is emptied instead of deleted. The name is replaced, the home city is cleared, the clock offset goes back to zero and every way in is gone. What is left is a number that means nobody.
• Your bakery stays on its corner. The shop keeps standing with its name replaced, and the plot it sits on is not handed to anybody else. Freeing the plot needs a change to the database that has not been made yet.
• A crew you founded keeps its name. A guild name and its short tag are not overwritten. They belong to everyone still in the guild, so closing your account does not take them away from the people left behind.
• Anything recorded about cheating stays. If the game ever recorded that an account was manipulating the market, that record survives the deletion. Deleting it would let somebody wipe their own record by closing an account, and an investigation into what was done to other players is not the closing player’s to erase.
• A record that the deletion happened stays. One row saying an account was erased, when it was asked for, which route it came in through, and how many rows went from each table. It holds counts and no content. If a member of staff carried the deletion out for you, the log of what staff do also keeps the display name the account had, because nothing can edit or remove a line from that log. The sign-in records keep their shape as well, with the address, the device string and the link to you all removed.

It is immediate and it cannot be undone. There is no grace period and no restore, and nobody here has a way to bring an account back.

9. How it is kept

Everything the game sends travels over an encrypted connection, and the server refuses plain ones. The database sits on a private network behind a firewall that lets exactly one machine talk to it, and it is reached over an encrypted connection too. It is not on the internet.

There is no password to steal, because the game does not ask for one. A sign-in gives your app a pass that expires after fifteen minutes and is renewed quietly while you play, so a copied pass is worth very little and not for very long.

The server keeps a log of the requests it answers. That log records what was asked for and how long it took, and it does not record your address, your device or who you are.

Very few people can reach the live database, and none of them works for anybody else. There is no analytics company, no advertising network and nobody holding a second copy. Sections 3 and 4 say who receives anything and what is never done with it.

Drafted 21 August 2026. Superseded the moment a reviewed version exists.

Back to the front page