Aether Grid · bsoft

Privacy Policy

Aether Grid is a turn-based strategy game developed by bsoft (Beka Ivanidze). This policy explains the data handled by the game, its multiplayer service, and its advertising integration. Contact: developerbivanidze@gmail.com.

Request deletion of your data · Contact support

Playing on your device

No account or payment is required. Campaign progress, preferences, saved solo games, cached ad settings, ad-frequency counters, review-request cooldowns, and update reminder preferences are stored locally. The game does not upload your campaign save to our servers. You can erase local data through Android's app storage settings. Uninstalling normally removes local app data; operating-system backup or restore settings may affect restoration.

Multiplayer

When you use multiplayer, the host or dedicated server receives your chosen display name, room information, moves, and connection information such as your IP address. Temporary member identifiers and reconnect tokens keep your session working. Other players in your room can see your name, slot, readiness, and game actions. Public room discovery also exposes the room name, host name, and player count to people browsing rooms. Use a nickname rather than private identifying information.

Room and match state is held in server memory while the room exists and is removed when the room closes or the server restarts. Service logs record operational events such as room creation and match completion. These logs are rotated according to server storage limits. We do not operate a permanent player-account database or cloud campaign history.

Direct play connects to a player-operated host. Nearby discovery sends local-network requests and advertises host addresses, room names, and player counts. Direct/LAN traffic may be unencrypted, and the host can process connection and game data. Our hosted online service uses DTLS. Avoid sending sensitive information in names or rooms.

Google Play reviews and updates

For installations from Google Play, the game can ask Google Play to show its review form or check for an app update. Google Play handles these flows under its own terms and privacy policy. Update checks use device metadata, the installed app version, and information about this app’s installed modules and asset packs. Google encrypts this information in transit and uses it to determine update availability and size.

If you choose to submit a rating or written review, it goes to Google Play. Reviews can be public, or private developer feedback on a test track. You can remove a review through your Google Play or Google Account controls. The game itself cannot read your rating or review text, and Google does not tell the game whether you submitted a review. We keep only local counters to avoid prompting too often.

Configuration requests and service logs

The app checks our HTTPS configuration endpoint at startup and when returning to the foreground to determine whether banner and interstitial ads are enabled. These requests do not include your campaign save or an account login. Like other internet connections, the server sees an IP address. Web-server access logs may contain IP address, request path, time, status, and client headers for operation, troubleshooting, and abuse prevention. They rotate daily and keep up to 14 rotated archives; empty logs may not rotate.

Ads and Google Mobile Ads SDK

The Android app includes Google AdMob through the Poing Studios plugin. Development and Firebase test builds use Google's sample ad units. Production-configured Android builds use our real banner and interstitial ad units. Test mode does not mean the SDK is offline or that no data is transmitted.

Google's Mobile Ads SDK can collect and share IP-derived approximate location, ad/app interactions, diagnostic and performance information, and advertising, app-set, or other device identifiers. Google uses these data for advertising, measurement, and fraud prevention. The SDK encrypts its transmissions. See Google's Privacy Policy and Google Mobile Ads data disclosures.

Ads are not used in desktop or dedicated-server builds. Google advertising identifiers can be reset or deleted through supported Android advertising/privacy settings. Resetting an identifier does not necessarily erase data already held by Google. Production-configured Android builds ask for an age range before enabling ads. The choices are under 13, ages 13–15, and 16 or older. The game is intended for ages 13 and older; users who indicate they are under 13 may receive child-directed, non-personalized banner and interstitial ads with Google’s most restrictive content rating (G). For this group we enable child-directed treatment in Google Mobile Ads and the under-age flag in Google’s consent SDK, with the same ad placements and frequency as other age groups. For ages 13–15, we request restricted, non-personalized, G-rated ads and send an under-age-of-consent flag to both Google’s consent and advertising SDKs. The age range is stored locally; we do not collect a date of birth or send the range to our game server. Google’s User Messaging Platform checks the applicable consent requirements at launch and presents a privacy message where required for users aged 16 or older. You can revisit Ad privacy on the main menu to change your age range and, where available, manage or withdraw consent. Declining personalized advertising does not prevent gameplay. Whether an ad can be requested after a choice is determined by Google’s consent SDK; this may allow limited or non-personalized ads.

What we do not request

The game does not request your precise GPS location, contacts, camera, microphone, health information, or payment details. It has no built-in chat, purchase system, or account creation. We have not integrated Firebase Analytics or Crashlytics into the game. Firebase App Distribution and Google Play may separately process tester information under their own terms when you use their distribution services.

Support, retention, and deletion requests

If you email us, we receive your email address and the information you choose to include. We use it to respond and resolve your request; do not send passwords or unnecessary sensitive information. Contact us at developerbivanidze@gmail.com to request access, correction, or deletion of information we hold. Provide enough context to locate the data without sending a password. We will explain if data cannot be located, is no longer held, or must be retained for a legal or security reason.

Local game data can be removed on your device. Temporary multiplayer state is removed as described above. Service logs have limited, rotating retention rather than an account archive. Google controls retention and deletion of data it independently processes; use its privacy controls or contact Google for those requests. Our public policy page is hosted on Firebase Hosting, which processes technical web-request information to deliver the page.

Audience and changes

Aether Grid is a strategy game for a general teen and adult audience, not a child-directed service. If you believe a child has provided personal information to us, contact us so we can investigate and address it.

We may update this policy as the game changes. The effective date above identifies the current version. Material changes to data handling will be reflected in the policy and relevant app/store disclosures.