alm4gest-site

日本語 English 한국어 繁體中文

ALM4GEST Privacy Policy

Last updated: July 26, 2026

Takahiro Kawaguchi (@ekarunian, the “Operator”) sets out below how user information is handled in the mobile application “ALM4GEST” (the “App”).

1. Information we collect

The App collects the following information.

Information Details When it is collected
Play data Per-chart scores, grades, clear status, flare rank, EX score, play count, last played date, and similar When syncing with e-amusement
Player identifiers Per-game player code (DDR code, SOUND VOLTEX player ID) and player name Same as above
Manually entered records Scores and similar entered by the user When entered (sent as described in section 3)
Crash information Error details, where the error occurred, device model, and OS version when the App terminates unexpectedly When the App crashes
Advertising identifier IDFA on iOS, advertising ID on Android When ads are shown (only with the permission or consent described in section 5)

The App does not collect your e-amusement login ID, password, or other credentials.

2. Where data is stored and sent

  1. Collected information is first stored in a database on your device.
  2. When a sync completes, the play data and player identifiers obtained from that sync are sent to a server managed by the Operator, for the purpose of building all-player statistics.
  3. Data sent to the server is stored in a private area and is never published or provided to third parties in its raw form.

3. Backup

The App has a backup feature for carrying your data over when you change devices.

  1. Every time a sync completes, a full set of the play data on your device is automatically sent to and stored on a server managed by the Operator (this includes manually entered records, your player name, saved filters, and app settings). You can also run a backup manually from the settings screen.
  2. The stored data is tied to a restore code issued by the App, and only someone who knows the restore code can retrieve it.
  3. If you want your backup deleted, contact the Operator with your restore code as described in section 7.

4. Purpose of use

Data sent to the server is used only for the following purposes.

  1. Compiling all-player statistics (per-chart average scores, clear rates, T-scores, tier lists, and similar) and delivering them to users of the App
  2. Improving the quality of the App (verifying data consistency and investigating causes of crashes)
  3. Restoring data from a backup (when you use the feature described in section 3)
  4. Publishing statistics aggregated so that no individual can be identified (for example, per-chart clear rates, score distributions, and usage trend analyses), including via the Operator’s social media accounts and websites

When statistics are compiled and delivered, player codes are converted into an anonymous ID via an irreversible hash, and no player code or player name is included in the delivered data. No individual user’s scores are ever delivered in a form that identifies that person.

5. Advertising

The App displays advertisements through Google AdMob.

  1. To deliver ads, AdMob may use an advertising identifier (IDFA on iOS, advertising ID on Android).
  2. On iOS, the App shows a tracking permission dialog before it displays the first ad. If you do not grant permission, the App shows non-personalized ads that do not use the advertising identifier.
  3. In the European Economic Area and similar regions, the App shows a consent screen provided by Google’s consent management tool, and delivers ads within the scope of your consent.
  4. The App does not provide its play data or player identifiers to advertising companies. The only thing used for advertising is the advertising identifier.

Data handling within AdMob follows Google’s policies.

6. Service providers

Except where required by law, the Operator does not provide or sell collected information to third parties. However, the App uses the following services to operate, and information is processed by them within the scope of each purpose.

Service Purpose Information processed
Cloud storage provider Storing data Play data, player identifiers, backup data
Google (AdMob) Delivering ads Advertising identifier
Google (Firebase Crashlytics) Investigating causes of crashes Crash information

The cloud storage provider is entrusted with storage only, and does not use this data for its own purposes.

7. Deleting your data

  1. Data on your device is deleted in full when you uninstall the App.
  2. If you want data stored on the server deleted, contact us at the address below with your player code (we will delete it within a reasonable period).
  3. If you want backed-up data deleted, contact us with your restore code.

8. Changes to this policy

The contents of this policy may be changed as needed. The revised policy takes effect when it is posted on this page.

9. Contact

Operator: Takahiro Kawaguchi (@ekarunian) Contact: kawaguchi.ek@gmail.com