ALM4GEST Privacy Policy

Last updated: September 10, 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, GITADORA 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)
User settings data	Per-chart memos, judge timing values, challenge songs you have pinned, saved filters, tier lists you have made, and app settings	When entered or set (sent as described in sections 3 and 4)
Friend data	Your friend code, your relationships with other users (requests, approvals, removals, blocks), and the version of the notice you agreed to	When you use the friend feature (sent as described in section 5)
Crash information	Error details, where the error occurred, device model, and OS version when the App terminates unexpectedly	When the App crashes
Usage information	App launches, screens viewed, sync runs and their results (games covered, records fetched, time taken), the start of first-time setup and whether a first record was saved, device model, OS version, country, App version, and an identifier assigned per installation (this is not the advertising identifier)	While you use the App
Advertising identifier	IDFA on iOS, advertising ID on Android	When ads are shown (only with the permission or consent described in section 7)
Health data	Body weight, body fat percentage, and active energy	Only if you turn on the health app link (Health on iOS, Health Connect on Android), when you open the App and when you open the weight entry screen

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

2. Where data is stored and sent

Collected information is first stored in a database on your device.
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.
Data sent to the server is stored in a private area and is never published or provided to third parties in its raw form. The only exceptions are a tier list that you choose to publish yourself (section 4) and the records written out for your friends (section 5).
Usage information is sent to Google Analytics for Firebase (section 8), not to the Operator’s server. Play data, player identifiers, manually entered records, and user settings data are not sent there.
Health data (body weight, body fat percentage, and active energy) is stored only on your device and is not sent to our servers. It is not included in the backup described in section 3, so it does not carry over when you change devices. Body weight is an exception in one direction: when you ask the App to, it is sent to the e-amusement site to update your registered weight there, which that site uses for its calorie calculation. If the health app link is on, the App also writes your DDR sessions to your device’s health app as workouts.

3. Backup

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

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, app settings, per-chart memos, judge timing values, and challenge songs you have pinned). You can also run a backup manually from the settings screen.
The stored data is tied to a restore code issued by the App, and only someone who knows the restore code can retrieve it.
If you want your backup deleted, contact the Operator with your restore code as described in section 9.

4. Publishing a tier list

The App lets you share a tier list you made with other users. This works only when you choose to publish it.

When you publish, the title, target game, target levels, tier names, chart placements, and your player name are sent to and stored on a server managed by the Operator. Scores, clear status, and player codes are not included.
A published tier list can be retrieved only by someone who knows the 8-character share code issued by the App. It cannot be found through any listing or search.
The share code itself is not stored on the server. The server keeps only an irreversible transformation of it.
You can have up to 20 tier lists published at a time.
When you stop publishing, the tier list stored on the server is deleted. Copies that other users imported while it was published remain on their devices.
Only when you publish does the App check the title for words that are not suitable for publication. If a word matches, the tier list cannot be published. We do not tell you which word matched. Tier lists you keep to yourself are not checked.
A tier list is deleted automatically two years after it was last retrieved.
If you find a problem with a published tier list, contact us through “Send feedback / report a problem” on the settings screen.

5. Friends

The App has a feature for sharing your records with other users. It only works once you issue a friend code.

When you issue a friend code, your player name, the games you choose to publish, your per-game official identifiers (SDVX ID, DDR code, and similar), and the band your core metric falls into (for example, a VOLFORCE bracket) are sent to and stored on a server managed by the Operator.
The records shown to your friends are written out after your visibility settings have been applied on your device, and are then stored on the server. They cover per-chart scores, grades, clear status, flare rank, EX score, play count, last played date, and the date your personal best was updated, together with your core metric (VOLFORCE, FLARE SKILL, GITADORA SKILL). Anything you set to private is removed at that point and is never sent to the server.
Only friends you have approved can retrieve the stored records. However, users you have not approved can see the items you set to “public”.
Other users can find you by your friend code, by an official identifier you publish, or by your player name. You can stop others from finding you by player name in the App’s settings.
Declining a request, removing a friend, and blocking someone are never disclosed to the other person.
When you block someone, the relationship kept on their side is deleted and the fact that you blocked them is kept only on your side. While a block is in place, neither of you appears in the other’s search results.
You can register up to 50 friends.
When you stop using friends, your friend code, your relationships with other users, and the records written out for them are deleted from the server. Records that friends imported to their own devices while you were friends remain on those devices.

6. Purpose of use

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

Compiling all-player statistics (per-chart average scores, clear rates, T-scores, tier lists, and similar) and delivering them to users of the App
Improving the quality of the App (verifying data consistency, investigating causes of crashes, and analyzing usage to improve features)
Restoring data from a backup (when you use the feature described in section 3)
Storing a tier list you choose to publish and delivering it to users who know its share code (when you use the feature described in section 4)
Storing the records shown to your friends and delivering them to the people you have approved (when you use the feature described in section 5)
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.

7. Advertising

The App displays advertisements through Google AdMob.

To deliver ads, AdMob may use an advertising identifier (IDFA on iOS, advertising ID on Android).
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.
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.
The App does not provide its play data, player identifiers, or health data to advertising companies. The only thing used for advertising is the advertising identifier. Health data is never used for ad delivery, targeting, or measurement.

Data handling within AdMob follows Google’s policies.

8. 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, published tier lists, friend data
Google (AdMob)	Delivering ads	Advertising identifier
Google (Firebase Crashlytics)	Investigating causes of crashes	Crash information
Google (Google Analytics for Firebase)	Analyzing usage	Usage information

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

9. Deleting your data

Data on your device is deleted in full when you uninstall the App. Health data (body weight, body fat percentage, and active energy) is stored only on your device, so uninstalling removes it completely.
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).
If you want backed-up data deleted, contact us with your restore code.
A published tier list is deleted from the server when you stop publishing it in the App (section 4).
Data stored on the server for the friend feature is deleted together when you quit the friend feature in the App (section 5).
If you cannot open the App, you can also request deletion from the deletion request page.
Usage information is not linked to your player code, so we cannot delete it for an individual user. What is stored in Google Analytics is deleted automatically once Google’s retention period has passed.

10. 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.

11. Contact

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