Abyssborn Privacy Policy
Abyssborn ("the Game" or "the Service") values your privacy and complies with
applicable laws. This policy explains what information the Game (iOS & Android apps and the web
version) collects, and how it is used, stored, and deleted.
1. Information We Collect and Why
- Auto-generated identifier and nickname: A random unique identifier (UUID)
created on first launch, and the nickname you enter (default e.g.
Guest1234). Used to display leaderboard rankings, process feedback,
and prevent duplicates. Stored on your device and sent to the server when submitting scores or
feedback.
- Game records: Your play results — survival time, level reached, kills, and the
phase reached. Stored on the server at the end of a run to provide the online leaderboard.
- Feedback data: When you send feedback in-game, the message, category (bug ·
improvement · other), nickname, identifier (UUID), originating screen, game version, screen
resolution, browser information (User-Agent), and the connecting IP address are stored on the
server. This is used to reproduce bugs and classify suggestions. Please avoid including
personally identifiable information in your message.
- On-device settings (local storage): Language, audio (music/effects) volume,
restart count, and the timestamps of your last feedback/ad. Stored only on your device
(localStorage) and never transmitted externally.
- Advertising identifier: An advertising identifier — the IDFA on iOS and the
Android Advertising ID (AAID) on Android — may be used for personalized ads (see Section 6).
2. Data Retention and Disposal
| Category | Retention period |
| On-device data (settings, identifier, etc.) | Until you delete the app or clear the data |
| Server-stored game records (ranking) | Kept as needed for operation; deleted upon request |
| Server-stored feedback | Discarded after the issue/improvement is addressed; deleted upon request |
Once the retention period expires or the purpose is fulfilled, the data is disposed of without delay.
Electronic files are deleted using methods that make recovery impossible.
3. Provision to Third Parties
As a rule, we do not provide your personal information to third parties, except in the following
cases:
- When you have given prior consent
- When required by law or a lawful request from an investigative authority
4. Processing Entrustment
We entrust processing for advertising as follows. Game records and feedback are stored on a server
operated directly by the operator.
| Processor | Entrusted task |
| Google LLC (Google AdMob) | In-app ad delivery and ad performance measurement |
5. Your Rights and Data Deletion Requests
You may at any time request access to, correction, deletion, or suspension of processing of your
personal information. The Game has no login accounts and uses only a random identifier (UUID) and a
nickname.
- On-device data: Removed immediately when you delete the app.
- Server data (ranking · feedback): To request deletion, email us the nickname or
identifier (UUID) shown in the app at the contact address below.
6. Advertising and Tracking
- The mobile app displays Google AdMob interstitial ads.
- App Tracking Transparency (ATT): On iOS 14.5+, the app requests tracking
permission. You can decline and still use all features of the app; in that case
non-personalized ads are shown.
- In some regions (e.g. the EU), an ad personalization consent (UMP) screen may be shown.
- You can limit ad tracking in your device settings (iOS: Settings > Privacy & Security >
Tracking, Android: Settings > Google > Ads).
- Data processing through AdMob is governed by Google's advertising policies. You can review how
Google uses data from sites and apps that use its services at
Google's partner policy.
7. Children's Privacy
The Game does not collect login accounts, real names, contact details, or other sensitive or
personally identifying information, and uses only a randomly generated identifier.
8. Security
We apply reasonable technical and administrative safeguards to protect personal information, including
transport encryption (HTTPS) and restricted server access.
9. Changes to This Policy
This policy may be revised in response to changes in law or the service. Significant changes will be
announced on this page.
10. Contact
Effective date: July 2, 2026