English
Privacy Policy
HOTARU STUDIO, operated by HOTARU LIMITED LIABILITY COMPANY (“we”), operates Head Clash (the “Game”). This policy explains how the Game handles information. Processing varies by platform, version, region, and the features you use.
1. Accounts and gameplay data
- When you create a guest account, you enter a nickname and the Game generates a random installation identifier on your device. PlayFab stores the associated player account. This identifier is not a hardware serial number. Your nickname is shown to opponents and may appear in weekly leaderboards and battle history. Avoid using a real name or contact details as your nickname.
- If you choose to link or recover an account, native Apple or Google Play Games authorization processes platform account identifiers and authorization credentials. The current Apple sign-in implementation does not request your name or email. Older accounts can sign in with their existing username and password.
- PlayFab and Microsoft Azure services process accounts, matchmaking, and game profiles. Azure Cosmos DB stores points, unlocked and equipped cosmetics, themed challenge progress, match state, the ten most recent online battles, share reward claim status, and weekly points. Battle history includes both players’ nicknames and identifiers, time, map, result, and points. Leaderboards display nicknames, points, and ranks.
- Online battles also send network latency measurements to the server, where they are stored per player in the match document to adjust playback timing and improve network performance.
- We use this data for sign-in and recovery, cloud progress, matchmaking and battles, rewards, leaderboards, and prevention of cheating or duplicate rewards. Guest registration uses hashed installation identifiers and network addresses to limit abuse.
2. Purchases and local settings
Platform versions offering an ad-removal product use Apple App Store or Google Play and Unity IAP to query products, process transactions, and restore purchases. The current Game caches ad-removal entitlement on your device and updates it from store transaction status. It does not upload purchase receipts to the Game’s PlayFab or Azure backend. The store handles full payment card details; we do not receive them directly. Language, volume, and local sign-in credentials are stored on your device. Signing out of a game account does not automatically remove an ad-removal entitlement.
3. Ads and privacy choices
Mobile versions integrate Google Mobile Ads (AdMob) and the User Messaging Platform (UMP). Depending on your choices, region, permissions, and version, these SDKs may process IP addresses and the approximate location estimated from them, app or device identifiers, ad views and clicks, app interactions, and crash, performance, or other diagnostic data for ad delivery, measurement, analytics, security, and consent management.
The current iOS implementation does not request App Tracking Transparency (ATT) authorization. Without authorization, Google does not send IDFA in ad requests, but app- or publisher-scoped identifiers and the other technical data described above may still be processed. Where a privacy choice needs to be offered again, use “Ad privacy settings” on the ad-removal screen. Device privacy settings also control relevant permissions. An ad-removal purchase stops the corresponding ads; it does not automatically delete information previously processed.
4. Sharing and support
The X sharing feature opens X’s post composer with a game introduction and store link. You can edit or cancel the post. The Game does not read your X account or posts and does not receive proof of posting. Share reward claim status is stored against your game account. If you contact support, our email provider and we process the email address, issue description, and attachments you send to respond to your request. Do not send passwords or authorization tokens.
5. Providers, retention, and security
Microsoft PlayFab, Azure Functions, and Cosmos DB provide accounts, matchmaking, and cloud gameplay services. Google AdMob and UMP provide ads and privacy choices. Apple, Google Play, and Unity IAP provide platform sign-in or purchase services. These providers may process information in Japan or other countries.
Account profiles and points settlement receipts currently have no automatic expiry, so progress can be maintained and duplicate rewards prevented. The ten most recent battle records remain in the account profile. Completed, settled match documents expire seven days after their last update; weekly leaderboard snapshots expire after ninety days; guest registration rate-limit records expire after two days. Matches awaiting reward settlement remain available for that processing. Stores and other providers retain data under their own policies. Support emails are retained as needed to handle requests and necessary legal obligations.
Game service requests use HTTPS, and access to account and server data is restricted. No network transmission or storage can be guaranteed completely secure.
Provider privacy information: Microsoft · Google · AdMob · Apple · Unity.
6. Requests and contact
To request access, correction, or deletion of an account or related data, or to ask about applicable privacy rights, contact the email address below. We may need to verify account ownership to prevent accidental deletion. Records that must be retained by law and information held by platform stores may require separate handling.
Privacy and game support: mugencombat34@gmail.com
7. Children and policy changes
Follow the age rating shown by your platform store. If you believe a child provided personal information without appropriate guardian consent, contact us. We will update this page and its date when features, processing, or providers change.