Gals — Privacy Policy

Draft under legal review. This is the current working version of our privacy policy, published while our counsel's review is in progress, and it will change. Dated 6 October 2026. Questions: support@galsgame.com.

Last updated: 6 October 2026

This policy explains what personal data the Gals game (the "game") collects, why, who else handles it, how long it is kept, and the choices and rights you have. The game is operated by Le Studios LLC, 522 W Riverside Ave Ste N, Spokane, WA 99201, United States ("we", "us"). For anything in this policy, write to support@galsgame.com.

1. The short version

• You need an account to play. We ask for a handle (the name other players see) and a password. An email address is optional and is used only to help you get back into your account. (once the app offers it) You can also sign in with Apple or Google.
• No ads, no third-party analytics and no tracking. We do not show ads, we put no analytics or advertising company's code in the game, and we do not track you across other apps or websites. Our own server keeps a short record of how the game is played (section 2, "Gameplay events"), which stays in our own database and goes to no analytics or advertising company. We do not sell your personal data, and we do not share it for cross-context behavioural advertising.
• The game is for adults, 18 and over.
• Other players can see your handle, your ranking and record, your side in Gloss and Grit, the pages you play against them, a page you choose to show on your profile, your label's name on its board, and, if you are friends, whether you played today.
• Our staff can see what they need to review reports, and every action they take is recorded (section 5).
• If you buy gems, Apple or Google takes the payment. We give the store a random ID for your account so the gems reach the right account, and we keep the store's record of the purchase.
• Your data, your call. You can download a copy of your data in Settings, and delete your account in the app or at https://api.galsgame.com/account/delete.

2. What we collect

Account information

• Handle. Chosen by you, 3 to 20 letters, numbers or underscores, and shown to other players.
• Password. We store only a salted one-way hash of it (Argon2id), never the password itself, and it is never written to a log.
• Email address (optional). Used only to confirm the address, to send a password-reset link when you ask for one, to tell a confirmed address that you replaced it with another, and to tell you of a change to this policy that matters (section 11). We send no other email, and no marketing.
• Account ID and join date. A random account ID, and the date you joined, which your profile shows as "member since".
• Sign-ins. For each time you sign in, we keep a hash of the sign-in token, when it started and when it expires.
• Recovery links. When we mail you a link, we keep a hash of it, when it expires and whether it was used. A confirmation link also remembers which address it was sent to.
• The terms you agreed to. Which version of our Terms of Use you accepted, and when.
• Signing in with Apple or Google (once the app offers it). If you sign in with Apple or Google, we keep which one, the ID that company uses for you with us, the email address it confirmed (if it sent one), and when you linked it and last used it. The address it confirms becomes your account's address unless another account already has it, and a Hide My Email address from Apple counts. For Apple we also keep a token that lets us tell Apple when you delete your account; it is never shown to anybody, put in your data download, logged or sent in a crash report. We never read or keep the name Apple offers.

Gameplay information

We keep the gameplay records the game needs to work:

• Your collection: the pages you hold, your lineup, the one page you choose to show on your profile, and each page's following: every gain, from play or from likes you spent.
• Packs and pages given: every pack you opened and every page you were given, including the random seed it was drawn from and the rates it was drawn under, so a disputed pull can be checked.
• Battles and ratings: your battles of every kind and their results, your rating changes, and your monthly ratings and records.
• Balances: your history of gems, tokens and likes, and of materials, earned and spent.
• Progress: your daily, weekly, monthly and First Issue quests, the days you claimed on the login calendar, completed issues, daily battle counts, and your progress toward the Art guarantee.
• Your choices in the game: your agent, the title, seal and dateline you show, your favourite model, the side you chose each month and your Cover votes, and your label: its name (made from the game's own word lists), its departments and each week it paid.
• The raid, the wardrobe and the runway: your raid decks, votes, attacks and rewards; the wardrobe pieces you own, which page wears which, and each piece the raid gave you with the seed it was drawn from; your runway shows and Circuits, each with its seed (kept from you until the show is claimed or the Circuit ends); and the pieces you made in the Atelier and the fittings each needed.
• The season pass, the Critics and the story: the rewards you claimed, what each draw gave, and the months settled for you; your sittings at the Critics' tables, the handicaps you chose and your scores; and the story's chapters: your lead, the scenes you cleared, the choices you made and the rewards paid.
• Seals and datelines: the ones you own, how you got each, and what you paid if you bought one.
• Queue: your place in the matchmaking queue, including when you last checked it.
• Quick chat: the remarks you send in a live battle. Quick chat is a fixed list of remarks, so nobody can type free text to another player.
• Gameplay events: a short record of which parts of the game you used and when, of twelve kinds: a session starting (after 30 minutes without the app connecting), a pack opened, a battle finished, a show sent, a raid attack, a calendar claim, a quest claimed, a purchase, a purchase that failed, joining an agency (held), a sync that failed, and a sign-up that was refused. Each holds a few fixed details and nothing else: for example where a pack came from and whether it held an Art, a battle's kind and whether it was won, rated or between friends, a purchase's product and whether it was a test, why a purchase failed and which store it was made in, and for a session the app's build number and your phone's platform. We also keep when your app last connected, which is what a session is measured from. Our own server writes these when the action happens; the app sends nothing extra, and no event holds your name, email address, payment details, a receipt, a page or anything you typed. We use them to see how the game is played and where it breaks. We keep them for 90 days; they are deleted with your account and included in your data export. Every kind is a record of your own account but one: a refused sign-up made no account, so our server records it with no account attached, by a short code saying why, never the name, the address or the password that was typed, and keeps it the same 90 days.

Battles against other players

• Live battles. When you play a live battle, we record each move and when it was due, because a move not made within the time limit loses that round.
• Instant battles. In an instant battle, another player battles pages dealt from your collection while you are not there. That battle is recorded too. Since 16 September 2026 instant battles are not rated.
• Friendly battles. A live battle with a friend is recorded like any other live battle.

Friends

• Your friends: each friendship names both players, and when it began.
• Friend requests: who asked whom, and when. An unanswered request lapses after 14 days, and is deleted the next time any player makes a request or opens a friends list.
• Friendly challenges: who challenged whom, and when the challenge lapses, 30 minutes on.

The Agency and the Annual (held: built, and switched off at launch)

• The Agency, while it is switched on: the agency whose books you are on and your role and joining time there; each request you made to join one and how it was decided; each time you left or were removed (never by whom); the rewards its weeks paid you; the bookings you picked; your requests for materials on its call sheet; and what you gave to another player's request. An agency's join code is kept only as a hash.
• The Annual, while it is switched on: a place you took in one of its categories, with what you counted. A place stays in the year's record after the account that won it is deleted, naming nobody (section 7).

Purchases

Gems are sold through the Apple App Store and Google Play, which take the payment. We never receive your card or payment details.

• Your account ID goes to the store. When you start a purchase, the app gives the store your account's random ID, so the purchase can only be credited to your account.
• What we keep. We check the purchase with the store and keep:
  • the store's transaction number and the product;
  • the quantity and the gems it gave, and any first-purchase bonus it paid;
  • for a season pass, the month it is for; for the Daily Delivery (a single purchase of gems over 30 days that never renews on its own), its terms, its first and last day, and each day's gems it paid;
  • whether the store marked it as a test purchase;
  • any refund;
  • when the store says you bought it;
  • the store's own record of the purchase. That record includes the country or region of your store account and, until you delete your account, the random account ID above (section 7).
• Store messages. Apple and Google send us messages about purchases, for example when they refund one. We check each message's signature and keep a record of it: the store's ID for the message, the transaction it was about, and what we did. Once a day we also ask each store for refunds we may have missed.
• Test purchases. A purchase made in a store's test environment (for example through TestFlight or as a Google Play licence tester) is recorded as a test.

Notifications

If you allow notifications, we store:

• a push token for your device;
• the platform (iOS or Android);
• a random installation ID the app creates;
• when your device last registered.

We use them to tell you when it is your move in a live battle (a friendly battle included) and when a live battle has finished. A notification can include your opponent's handle. We keep a short record of each notification owed to you and whether it was delivered.

The daily reminder you can turn on in Settings, and the notice that a runway show you sent is over, are scheduled on your phone and send us nothing.

Email

• Only these. We send an address confirmation; a password-reset link, when you ask for one; when a confirmed address on your account is replaced with another, a notice to the old address that it was changed; and a notice of a change to this policy that matters (section 11). The address-change notice does not name the new address and carries no link: it says what to do if you did not make the change.
• Who it is from. (once our server is given them) Every email we send ends with the studio's name and postal address and our support address.
• Through Postmark. All of them are sent through Postmark (see section 5), which receives your address, the email's subject, its text (which contains any link) and a label saying which kind of email it is.
• No tracking. Link tracking and open tracking are switched off in every email we send, so Postmark does not record whether you opened it or tapped the link.
• Limits. A reset link is only ever sent to an address you have confirmed. It works once and stops working after an hour. A confirmation link works for three days.

The pre-registration list (before launch only)

Our website offers a list for people who want to hear when Gals is out. If you join it, we keep your email address and, with it, only when you gave it, when we sent you a confirmation link and when you confirmed it, when we sent you the launch email, and a random code that lets you leave the list. We keep no IP address or device details with it, and nothing links it to a game account (joining, confirming and leaving are limited per network address, as "Security records" below says).

• Two emails at most. One asks you to confirm the address; its link works for three days, and asking again sends a new link at most once every ten minutes. The other is one email when the game is out. Both go through Postmark with tracking off, the launch email on a separate broadcast stream (Postmark adds a leave link of its own to such mail unless it hands the handling to us, which we have asked for), and the form says so before you type an address.
• Leaving. Both emails end with a link to leave the list, and carry the same link in the email's own headers, so your email app's own unsubscribe button does it too. Opening the link changes nothing; pressing the button on its page, or your email app's unsubscribe, deletes your address from the list at once, confirmed or not, and we never write to it again.
• Who it is from. Both end with the studio's name and postal address and our support address (once our server is given them).
• An address nobody confirms is never written to again. It is deleted about six days after its last link was sent: once its link has been expired for three days, the next address anybody enters in the form clears it away (or the whole list goes first).
• The count. The website shows how many addresses are confirmed, and that number decides which launch gifts every player receives.
• The end of the list. Once the launch email has gone out we delete the whole list; a backup taken before then keeps it until that backup is deleted.

Reports and moderation

• Reports you file. If you report another player's handle, we store who reported whom, the handle reported, the reason you chose (offensive, impersonation or other) and when.
• Reports about you. If your handle is reported, a person reviews it and we record the outcome: the report dismissed, your handle replaced, or your account suspended.
• Replaced handles. If we replace your handle, we keep your previous handle until you choose a new one, so it can still sign you in.
• Suspensions. If we suspend your account, we record when.
• Players you block. If you block another player, we store which player you blocked and when, until you unblock them or either account is deleted. We use it to keep the two of you out of each other's battles and to hide the quick-chat remarks between you. We do not tell the other player, and nobody else sees it.
• Our staff's record of what they did. When a member of our staff acts on an account, through our staff tool or our server's own commands (dismissing reports, replacing a handle, suspending an account or lifting a suspension, or deleting an account at a request we have verified, section 8), we record which member of staff did it, what they did, the handle it was done to, the number of reports open, what changed (for a replaced handle, the old one and the new one; for a deletion, when the account was made) and when. Nobody can change or delete these records, and they are not deleted when the account they name is (section 7).

Security records

• Attempt counts by network address. To limit repeated sign-in, password and recovery attempts, and repeated use of the pre-registration list's forms, our server counts such requests per IP address. It never stores the address itself: each count is kept under a code made from the address with a secret only our server holds, which cannot be turned back into the address without that secret, beside the count and the time it started. Our server's own regular sweep deletes a count about an hour after it started, however quiet the game is, and these counts are left out of our daily backups.
• Password attempts. We also keep a count of password attempts against each account, whoever makes them. It is deleted when the right password is given, and otherwise by the same sweep.

Server request logs

Our server writes a line for each request it receives. The line holds:

• the IP address it came from;
• the address requested, with any recovery token and any email address removed first;
• the result.

An address requested can include another player's handle, for example when you open their profile.

Render, our host, keeps these logs for 14 days (Render's retention on the studio's workspace plan). Our host also streams them to Better Stack (section 5), which we use to watch the game's health and to be alerted when it fails, and which keeps them for 3 days. The host's own systems may also record addresses requested, including a password-reset link, before our server sees them. Such a link works only once, and only for an hour.

Crash reports (if crash reporting is enabled)

If the app or our server crashes, a report is sent to Sentry, our crash-reporting provider.

• What a report holds: the error, where in the code it happened, recent steps the app took, and technical details such as the device model, the operating system version and the app version.
• What we remove first: before a report leaves the device or server, we remove sign-in tokens, recovery tokens, email addresses, passwords, cookies and the contents of requests.
• Not linked to you: no account is attached to a report.
• No screenshots: screenshots and performance tracing are off.

(once the owner turns on Sentry's setting that prevents storing IP addresses) Sentry does not store the IP address a report came from.

Web pages

• Five pages without the app. Our server has web pages for deleting an account, resetting a password, confirming an address, and confirming an address on the pre-registration list or taking it off.
• Nothing extra. They use no cookies and no scripts, keep nothing you type beyond what the action needs, and are not cached. (Our staff's own pages, which players cannot open, use one cookie to keep a member of staff signed in.)
• Opening a link changes nothing. Opening a reset, confirmation or leave-the-list link does not use it up; only pressing the button on the page does.
• Our website. galsgame.com sets no cookies and loads nothing from any other company's site. Its pre-registration form, and the count of confirmed addresses it shows, reach our own server, whose request log keeps the IP address each request came from for 14 days at our host (and at Better Stack, as "Server request logs" above says).

What we do not collect

We do not collect:

• your location, contacts, photos, files, microphone or camera;
• health data or browsing history;
• advertising identifiers;
• payment card details;
• your real name or date of birth (the name Apple offers at sign-in included);
• anything you type to another player, other than your handle.

On your phone only

These stay on your device and are never sent to us:

• a copy of your game data, which the app keeps so it can show your collection;
• your sound and reminder settings, the daily reminder and the runway show's notice;
• on a phone, your sign-in token, kept in the phone's secure storage;
• the age range your phone's app store shares with the app: Apple's Declared Age Range on iOS 26 and later, or Google's Play Age Signals on Android. The app asks for it once each time it starts, because some US states' laws require an app to ask; keeps the answer in the phone's memory for that launch only; never sends it to us, logs it, stores it or puts it in a crash report; and uses it only to refuse an answer that says you are under 18. Any other answer, or none, opens the game as usual.

3. How we use it, and our legal bases

We make no automated decisions about you that have legal or similarly significant effects. Every moderation decision is made by a person.

4. What other players can see

• Anyone, including people not signed in:
  • the monthly leaderboard. It shows handles, the titles and datelines players chose to show, the side each chose for the month, ratings, ranks, wins, losses and the gems each rank earns;
  • the month's Gloss and Grit standings, which name no player.
• Any signed-in player:
  • your profile. It shows:
  • your handle, the title and dateline you chose to show, your side this month, and when you joined;
  • your season rating, rank and record, and your all-time record;
  • how many pages you own and the issues you completed;
  • the page you chose to show, and your favourite model if you chose one;
  • to a player looking at it, their own win–loss record against you, from the battles they played against you.
  • the weekly raid's board: its top ten players by handle, with the damage each dealt;
  • the label board: the month's top 100 labels, each with its player's handle, its name and its renown.
• Your friends: your handle, whether you finished a battle today (never when), and since when you have been friends. A friend request or a friendly challenge you send shows your handle to the player you sent it to.
• Your opponents:
  • your handle, your side this month and the pages you play, with the name of any wardrobe piece a page you reveal is wearing;
  • your current rating, also shown when the queue matches you;
  • quick-chat remarks, unless either of you has blocked the other;
  • whether you ran out of time on a move;
  • whether you left a live battle because your account was deleted or suspended.

A notification to your opponent can name your handle.

• In an instant battle: another player may battle pages dealt from your collection: your lineup, plus pages drawn at random from the rest of your collection. They see your handle and the pages played against them, even though you do not take part yourself. Instant battles are not rated.
• Held: the Agency, while it is switched on: the players on your agency's books see your handle, your role, when you joined and how many days ago you last played; a request to join shows your handle to its head and bookers; and a request for materials shows your handle to your agency's players. The agency board names agencies, never players.
• Held: the Annual, while it is switched on: if you place in one of its categories, your handle and what you counted are shown to signed-in players in the game's news through the December after the year, unless your account has since been suspended or deleted.

Other players never see your email address, purchases, gem balance, full collection, reports, devices, or who you have blocked. A player you block is not told. A block does not hide you from the boards above or from your profile.

5. Who else handles your data

We use service providers that handle data on our instructions:

Apple and Google take payment under their own privacy terms. For each purchase, they receive the random account ID described in section 2, send us their record of the purchase and tell us about refunds. (once the app offers it) If you sign in with Apple or Google, that company tells us the ID it uses for you with us and, if you let it, your email address; when you delete your account, we tell Apple, so that it can end our access.

Our staff. Members of our staff sign in to our own staff tool with a password and a code from an authenticator app, and each is given one of three levels of access. Depending on it, they can see the reports queue (each reported handle, the handles as reported, how many reports and for which reasons, and when the first arrived, but never who reported), the record of what staff have done, and, while the Agency is switched on, each agency's players by handle with when each last played. They can dismiss reports, replace a handle, suspend an account or lift a suspension, and, from our server's own commands, delete an account at a request we have verified (section 8); every one of those actions is recorded (section 2). The staff tool shows no email address, purchase, balance or password. The people who run our servers can also reach the database itself.

The models whose photographs are in the game are paid a share of sales. What each model is owed is worked out from sales totals and which pages each bought pack held. No player is named to them, and we give them no data about you.

We may also disclose data:

• if the law requires it;
• to protect the rights and safety of players or of us;
• as part of a merger or sale of the game, in which case this policy continues to apply.

6. International transfers

Our providers may process data in the United States and other countries. One is in Australia: the password check (section 5, Have I Been Pwned) is a service of a company there, so while the check is turned on, the first five characters of a hash of a password you choose go to Australia, and nothing else about you does. Where data from the EU, the UK or Switzerland is transferred to a country without an adequacy decision, we rely on safeguards to be confirmed per provider.

7. How long we keep it

When you delete your account, we delete it and everything linked to it. If you are in a live battle, it is finished first. These are kept:

• Purchase records. Each keeps:
  • the store and the store's references for the sale (its transaction number and, for Google Play, its purchase token);
  • what was bought, the quantity and the gems it was worth;
  • whether it was a test purchase, and any refund;
  • the store's own record of the sale, such as its date, price and store country or billing region.

When you delete your account, we remove your account ID from the record, including from the store's own record of the sale. No handle, email address or password is kept with it. We keep these records so one purchase cannot be paid out to a second account, and so a refund the store makes later can still be applied.

• Packs bought with gems from a store purchase. Each keeps the pages it held, its seed, the rates it was drawn under and what the purchase paid towards it, but not who opened it, so the models of its issue are still paid their share of the sale. If the store later refunds that purchase, the models' share is still taken back. Every other pack is deleted.
• Battles another player started against you. They stay in that player's history, under the handle you had then, with the quick-chat remarks sent in them. For up to 14 days, notifications to that player can still name you.
• Reports you made about another player's handle. They stay open for review, no longer linked to you.
• Our staff's record of any action they took on your account, a deletion we made at your request included. It keeps the handle it was taken on (and, for a replaced handle, the old and the new one), and is never changed or deleted.
• (once the app offers it) A note for Apple. If you signed in with Apple, we keep Apple's ID for you and the token Apple gave us, only to tell Apple that your account is gone. Once Apple has accepted it, the token is erased at once and the rest of the note is deleted 30 days later; a note Apple has not yet accepted is kept until it has.
• Held: A place you took in the Annual. It stays in that year's record, naming nobody.
• Backups. Our backups of the whole database are kept for 90 days, as the table above says, so a deleted account is gone from every copy within 90 days. A backup is never used to restore one account.
• The stores' own records. Apple's and Google's records of what you bought are theirs, kept under their own privacy terms.

8. Your choices and rights

• Download your data: Settings, then Download My Data. You get a file with:
  • your account, including the terms you agreed to and when your app last connected; your collection and each page's following; and your gems, tokens and likes history;
  • your packs, with their seeds and the rates each was drawn under;
  • your battles and ratings, your sittings at the Critics' tables and your story fights;
  • your purchases, with each one's quantity, whether it was a test purchase, any gems a refund took back, when a refund was reversed, any first-purchase bonus, and the month a season pass was for; and each Daily Delivery with every day's gems it paid;
  • your completed issues, calendar days, raid decks, votes, attacks and rewards, wardrobe pieces and their drops (with seeds), runway shows and Circuits (with seeds once claimed or ended), materials, Atelier pieces, seals and datelines, season pass claims, your side each month and your Cover votes, your label, the story's chapters and scenes, and (held) your agency records and Annual places;
  • your devices, sign-ins, the Apple or Google sign-ins linked to your account, the reports you filed, the players you blocked, your friends and the friend requests you sent, the remarks you sent, the notifications owed to you, and your gameplay events.

It leaves out secrets: password and token hashes, push tokens, a store's purchase token, the store's raw record of a purchase, Apple's token and Apple's or Google's own ID for you, an agency's join code, and the seed of a show or Circuit still in play. It also leaves out reports other players made about you, any block another player made of you, and friend requests sent to you, because each names the player who made it.

• Your pull history: every page you were given, with its seed and the rates it was drawn under, is in the game's pull history.
• Correct it: change your email address or password in Settings. Both ask for your current password. You cannot rename yourself. If we replace your handle, you choose a new one.
• Delete your account: Settings, then Delete Account, or without the app at https://api.galsgame.com/account/delete. Both ask for your password. (once the app offers it) In the app, signing in with Apple or Google again also does. The web page works even if your account is suspended. Without your password, write to us from your account's confirmed address (below).
• Stop notifications: turn them off in your phone's settings.
• Leave the pre-registration list: use the link at the end of either of its emails (section 2), or your email app's unsubscribe button on them.

If you are in the EU (including Ireland), the UK or a similar jurisdiction, you also have the right to:

• access your data;
• have it corrected, erased or restricted;
• object to processing based on our legitimate interests;
• receive your data in a portable form;
• withdraw consent where we rely on it.

You can also complain to your data protection authority. (This paragraph and the naming of a supervisory authority are held with the territories other than the United States, for a later release; the launch is the United States only.)

If you live in California or another US state with a privacy law, you have the right to know what we collect, to have it deleted or corrected, to opt out of the sale or sharing of your personal information (there is nothing to opt out of, and we will honour a request anyway), and not to be discriminated against for using these rights. We do not sell personal information, and we do not share it for cross-context behavioural advertising. You may make a request yourself or through an agent you authorise; we may ask an agent for your signed permission, and ask you to confirm your identity with us directly. If we refuse a request, you may appeal by replying to our answer, and we answer the appeal within a period to be confirmed.

To use any right not built into the app, write to support@galsgame.com from the address on your account, or tell us your handle. We may need to confirm the account is yours. We answer within one month. To delete your account without its password, write to us from the account's confirmed address: we reply to that address, and once you confirm from it, we delete the account within one month of your request, keeping only what section 7 lists. An account with no confirmed address can be deleted only with its password, in the app or on the web page above.

9. Age

The game is for adults. You must be 18 or older to create an account. We do not ask for your date of birth: when you create an account, and when our terms change, the app asks you to confirm that you are 18 or over, and each time it starts it asks your phone's app store for the age range it shares (section 2, "On your phone only"). We do not knowingly collect personal data from anyone under 18.

If we learn that an account belongs to someone under 18 (for example because you write to support@galsgame.com to tell us), we suspend it at once, and tell its holder, at the account's confirmed address if it has one and in our reply if they write to us, that they may send proof that they are 18 or over to support@galsgame.com within 30 days. If none arrives within 30 days, we delete the account; deleting it keeps only what section 7 lists. A purchase made from it can be refunded only through the store's own refund process (Apple's or Google Play's), as any purchase can.

10. Security

• Passwords and tokens. Passwords are stored only as salted, costly hashes, and sign-in and recovery tokens only as hashes. A new password that is very common or easy to guess is refused.
• On your phone. The sign-in token is kept in the phone's secure storage.
• Connections. Connections to our servers are encrypted with HTTPS (true once the game's server is hosted; the store versions of the app require it).
• Attempt limits. Password attempts are limited per network address and per account.
• Our staff. Staff sign in with a password and a code from an authenticator app; a staff sign-in ends after 12 hours whatever happens, and the record of what staff do cannot be changed.
• Logs. Recovery tokens and email addresses are removed from our server's logs and from crash reports.

No system is perfectly secure. If a breach affects your data, we will tell you and the authorities where the law requires.

11. Changes

If we change this policy in a way that matters, we will say so in the game before the change takes effect, and mail the confirmed address on your account, if it has one. The date at the top shows when it last changed.

12. Contact

Le Studios LLC, 522 W Riverside Ave Ste N, Spokane, WA 99201, United States, support@galsgame.com

In the app, Settings has Contact Support, which opens your email app, with the address written beneath it; the notice the app shows when a phone's store says its player is under 18, and the sign-in screen of a suspended account, offer it too.

(once configured) The support address also appears on the account deletion, password reset and address confirmation web pages, on the pre-registration list's pages, and at the end of every email we send, once the server is given it.