Privacy Policy
Information linked to your account is also used to provide sneaker collections, upgrades, random draws, game progress and in-app purchase verification.
Information and purposes
TapMint uses a Firebase user ID and authentication information to identify your account, manage balances and protect the service. Google linking may provide an email address, display name and other profile information to the authentication service. The operator does not receive your Google password.
Step counts, daily claims, coin earnings, balances and exchange records support step display, shoe upgrades, walking rewards, limits and account history. Traditional step counting uses the device step counter from the first app launch each day. On supported TapMint versions and devices, if you optionally grant step-linking permission, TapMint also reads the total steps recorded in Health Connect for the current day, from 00:00 Japan Standard Time to the time of reading. TapMint does not write to Health Connect or read it in the background.
The sensor count and Health Connect total are not added together. TapMint uses the larger value and retains the maximum read for the same user and day to avoid counting the same steps twice. Steps that were never recorded by the device or Health Connect cannot be reconstructed. Not every step taken that day will necessarily be available.
When you choose to apply your steps in the app, the current-day step value is sent to the TapMint server with your user ID for step, upgrade and reward records and to prevent duplicate submissions. Step data, including Health Connect-derived data, is not used for advertising or ad targeting. This is separate from information independently collected by advertising SDKs.
You can revoke step permission in device settings and Health Connect read permission in Health Connect settings. Health Connect step records can also be deleted in that service's settings. Revoking permission alone does not delete records already sent to TapMint. To request deletion of TapMint data, including submitted step records, follow the account and data deletion process.
Collection and game records include owned shoes and items, equipped shoes and cosmetics, upgrade state, item use and draw results, draw counts, game progress and scores, and operation IDs. These records provide and restore collections, upgrades and draw outcomes, manage game results and in-game rewards, and prevent duplicate grants and abuse.
For the runner game, TapMint processes the course, shoe and level used, session and completion information, input history (including input timing and type), and results. The input history is sent to the server to replay the run and recalculate its score, clear status and in-game rewards, and to prevent abuse and duplicate processing.
Google Play purchase information includes product IDs, purchase tokens, purchase, verification and consumption status, cancellation and refund status, and an identifier linking a purchase to your account. This information is used to verify purchases, grant and restore products, reconcile unresolved purchases, reflect cancellations and refunds, and prevent duplicate grants and abuse.
Enabled exchange features may process a destination, requested value, delivery details and transaction records. Requests and support messages are used for identity verification, assistance and request management.
Google AdMob, Firebase and related services may process IP addresses, device and app information, advertising and other identifiers, interactions and diagnostics for advertising, analysis, authentication, service operation and abuse prevention.
Service providers
TapMint uses Google Firebase for authentication, storage, backend processing, configuration and analytics, and Google AdMob for advertising. When an external video service is provided, a stable pseudonymous identifier is sent to Adscend Media / PixelPointTV. That identifier does not directly contain your Firebase user ID or email. Information processed on the external service is subject to its own terms and privacy policy.
In-app purchases use the Google Play purchase screen. TapMint processes product IDs, purchase tokens and related information on its server to verify purchases with Google Play. An opaque account identifier is also sent to Google Play to associate the purchase with your account. Google processes payment-method information; the TapMint operator does not receive your card number.
Information required for an enabled exchange may be used by the relevant delivery provider. Cryptocurrency transactions, when offered and sent, are recorded on a public ledger. The operator cannot erase information from that ledger.
Storage and protection
Information is kept as needed to operate and manage your account and the service. Communications use HTTPS and access to account records is restricted. Your device may also store step baselines and display information.
Collection ownership, equipped items, upgrades, draw results and game progress are stored as game records, separately from step, coin-balance and exchange records but linked to the same account. Raw runner replays (input histories) are used to recalculate results on the server. The server game records do not retain the raw replay; they retain a comparison hash, session information and confirmed result and reward receipts. Purchase records use a hashed purchase-token identifier, product ID, verification status and related information.
To recover from interrupted connections and reconcile pending operations, the device may store unresolved step submissions, run progress and input history, and product IDs and purchase tokens for unresolved purchases. After a confirmed run result is checked, that run's pending submission is removed from the device.
After a deletion request, identity and outstanding exchanges are checked and the account and associated data are deleted. Limited records may need to be retained for legal obligations, outstanding delivery, essential transaction evidence or abuse prevention. The operator will explain the records, reason and retention period to the requester.
Minimal deletion-status and operation records are retained to prevent duplicate deletion and reuse of a deleted user ID. Outstanding exchanges and transaction records needing a retention decision are reviewed separately rather than automatically erased.
Account and data deletion
You can request deletion from Account in the app or use the Web channel after uninstalling. Uninstalling alone does not delete server records. Submitting a request does not automatically cancel your balance or pending exchanges.
Request account deletionYour choices
Google linking and step permission are optional choices. You can revoke permissions and manage advertising identifiers in device settings. Some features may then become unavailable. An unlinked anonymous account may become unidentifiable after device data is erased.
Google's User Messaging Platform (UMP) manages advertising consent and choices. When an entry point for revisiting those choices is required, the app displays “Ad privacy choices” in Wallet, which opens Google's options form.
Contact and changes
Operator: Yuki Amisaki
support@tapmint.app
Changes are communicated on this page and, when appropriate, in the app.