Privacy policy
Updated September 28, 2026 (JST)
This page explains the information used by Emberfort and how to manage your account. Komori is the contact responsible for the service.
Local game data
Language, sound preferences, display name, avatar, practice and campaign progress are stored on your device. In this preview, that progress is not converted into an online purchase balance. Clearing app data can erase local progress.
Online account
When you use account features, the server processes your email, display name, internal identifiers and authentication data. Passwords are stored as hashes. If you choose Google or Apple, we use that provider's identifier, verified email and authentication tokens to confirm your identity. Sessions use secure storage on your device and session records on the server.
Data handled by Google sign-in
When you choose Google sign-in, that provider's authentication software also processes information. On iOS, the privacy declaration for the Google Sign-In software included in the app lists name, email, phone number, approximate location, user and device identifiers, other usage data and other data. Google declares use for app functionality and, for identifiers and some data, usage analytics. This processing by the provider is separate from the information the Emberfort server receives: email, display name, identifiers and authentication tokens. Game registration does not ask for a phone number or GPS position. To manage or delete information held by Google, consult Google's privacy policy and your Google Account settings.
Purpose and connection data
We use information for authentication, account management, abuse prevention, available online features and support. The server and delivery infrastructure process technical connection information such as IP address, requested URL, time and errors. The API uses a hash derived from your IP to limit repeated attempts.
Purchases and external services
Sales are not enabled yet. When purchases become available, the screen will show the price and the payment service for your distribution channel. Purchase verification uses the product, transaction reference, an account-specific identifier and grant history. There is no field for sending your card number to the game server. Choosing Google or Apple authentication also sends authentication information to that provider.
Storage and deletion
In-app deletion removes the profile, authentication links, sessions, recovery data and the online records covered by the deletion process. Local progress is separate. Transaction records and some technical records may remain associated with an internal identifier. This preview does not yet have an automatic purge period configured for those records. Contact us to ask what is retained or request a review and deletion.
Your information and contact
To access, correct or delete information, use the contacts below and identify the product as Emberfort. We may need to confirm your identity. Do not send passwords, login tokens or card numbers. We will update this page when the information processed or available features change.