Privacy Policy

Last updated: October 24, 2026

Hachiware, LLC. (“we” or “us”) sets out below how we handle user information in “PicoCraft” (the “App”), a game for iPhone and iPad and Android.

1. Information We Do Not Collect

Except for information you choose to provide in an inquiry, the App does not collect information that directly identifies users, such as names, email addresses, phone numbers, precise location, device names, or advertising identifiers (IDFA / Android Advertising ID). The App does not show ads.

Your game progress (save data) is stored on your device. In the iPhone and iPad version, when you save from Settings → “iCloud backup,” a copy is stored in your own iCloud (Apple). This backup is not sent to our servers, and we cannot see it.

2. Usage Analytics and Crash Reporting (Firebase)

In the iPhone and iPad version, we use the following Firebase services provided by Google LLC to improve the App and investigate problems. The Android version does not include these services and does not automatically send usage or crash information.

• Google Analytics for Firebase: to aggregate how the App is used
• Firebase Crashlytics: to record when the App closes unexpectedly or an error occurs

Through these services, the following information is sent to Google’s servers:

• Identifiers assigned to the app installation (app instance ID, Crashlytics UUID, and Firebase installation ID; they do not directly contain your name but can link activity from the same installation)
• Device model, OS version, app version, and language and region settings
• Approximate country or region (estimated from your IP address)
• In-game actions and progress: screens shown, the start and end of digs (depth reached, time, number of blocks dug, etc.), the number of abilities learned (level and job in earlier versions), number of cycles, reaching a new layer, and destroying cores
• The situation when the App closes unexpectedly or an error occurs (the error, the screens and actions just before it, and progress such as the abilities set and number of cycles; level and job in earlier versions)

This information is sent only if you choose “Continue” with “Allow data collection” checked in “Anonymous play data,” which is shown when you first start a game in the App, among other times. It is not sent if you uncheck it before choosing “Continue” or while you have not chosen yet. You can change your choice at any time in the App’s Settings → “Anonymous play data.” Turning it OFF stops further sending and deletes the unsent records and analytics data remaining on your device (including the app instance ID).

To deliver game tuning values, the App also receives settings from Firebase Remote Config at startup or after consent. At that time, an identifier assigned to each app installation and the app version, language, and similar information are sent to Google’s servers, but no in-game actions or progress are included. Settings are fetched only after you allow data collection in “Anonymous play data.” While unanswered or OFF, you can play with the default tuning values. Users who allowed sending in an earlier version, before Remote Config was included in its purposes, are asked again.

Turning OFF stops new fetches and requests deletion of the Firebase installation ID from Google. If a fetch is in progress, deletion follows its completion. Failed deletion is retried on a later launch or consent synchronization. Communication needed for deletion and requests already in progress may still complete. Earlier versions fetched Remote Config regardless of this setting.

Retention on Google’s servers

• Google Analytics for Firebase: our GA4 settings retain event data for 2 months and user data for 14 months. User data retention resets with new activity, so the 14-month period runs from the latest activity. Google deletes expired data through a monthly process. These settings do not apply to aggregate data in standard reports, which continues to be retained. We verified these settings on October 20, 2026.
• Firebase Crashlytics: according to Google, crash information and associated identifiers are retained for 90 days, after which removal from live and backup systems begins. This does not mean every copy is deleted on day 90.
• Firebase Remote Config: Firebase installation IDs are retained until deletion is requested, and are removed from live and backup systems within 180 days of that request.

Turning OFF “Anonymous play data” or uninstalling the App does not immediately delete analytics or crash data already sent to Google. Resetting analytics data on your device and deleting server data are separate operations. Section 9 explains deletion requests and cases where individual data cannot be identified. These retention details are based on Google Analytics data retention and Firebase Privacy and Security.

The App does not collect the advertising identifier (IDFA) and does not track you across other companies’ apps or websites. For how Google handles information, see Google’s Privacy Policy and Firebase Privacy and Security.

3. Checking for Game Updates

To deliver bug fixes and game adjustments, the App checks our server for new update data when it starts and when it returns to the foreground (at most once an hour). If there is any, it downloads it and uses it from the next launch.

Only a value identifying the App’s build and information commonly included in network communication, such as your IP address and OS type, are sent. No in-game actions or progress, and no identifiers for you or your device, are included. This happens regardless of the “Anonymous play data” setting. You can keep playing when you are offline.

4. Inquiries from the App

Messages sent from the App’s Settings → “Contact” are sent to our server together with the following information:

• The type of inquiry (Bug or Feedback) and the message
• App version; device type, model, OS and its version; language and region settings; screen size
• Progress (number of cycles, number of digs, deepest depth reached, play time; also level in earlier versions)
• For bug reports, the state of the game when the send screen was opened (the screen shown, the abilities set, the depth being dug, the record of the latest dig, etc.; job in earlier versions)

Device names, device identifiers, and email addresses are not automatically attached. However, any personal information you type in the message is sent with it. We generally cannot reply individually to inquiries sent from the App.

If you would like a reply, you can contact us with your email app by choosing “Agree and open email” on the Contact screen. In that case, in addition to what you entered, the app version and the device and progress information above are included in the body of the email (you can check and delete them before sending). Such emails are handled as described in “Inquiries by Email” below.

The explanation near the send buttons states that the message and diagnostic information (and your email address for email inquiries) may be shared with external AI services to help draft replies and investigate problems. The providers are named in this policy, accessible through the “Recipients & Privacy Policy” link. Choosing “Agree and send” submits the inquiry; “Agree and open email” opens your email app. Consent is requested for each inquiry. For in-app submissions, we store the disclosure version and receipt time with the message; for email, the disclosure version you agreed to is included in the body.

The sender’s IP address is used only temporarily to prevent a large number of messages from being sent in a short time, and is not stored.

The content of inquiries is stored for 180 days after receipt and then deleted. If you tell us the ticket number shown after sending, we can also delete it earlier.

5. Inquiries by Email

If you contact us by email, we use your email address and the content of your inquiry (including the device and progress information in the body) only to respond and to investigate problems.

6. Purposes of Use

We use the information we obtain only for the following purposes:

1. Providing the App, and investigating and fixing problems
2. Improving game balance and features by analyzing usage
3. Responding to inquiries

7. Outsourcing to Service Providers

For the above purposes, we entrust the storage and processing of information to the following service providers. Their servers may be located outside Japan, such as in the United States.

We use these AI services with settings under which the content we enter is not used to train AI models. We may share inquiries with AI as needed, but only after explaining the recipients and purpose and obtaining explicit consent. Inquiries from earlier app versions or direct emails without confirmed consent are not shared with AI unless we obtain consent separately.

Except as required by law, we do not provide the information we obtain to third parties without your consent.

8. Changes to This Policy

We may change this Policy as necessary. The changed Policy takes effect when it is posted on this page.

9. Contact and Data Deletion Requests

For questions about this Policy or requests to delete the content of your inquiries, please contact us at support@hachiware.co.jp.

To delete an inquiry sent from the App, email support@hachiware.co.jp with the ticket number shown after sending and a request to delete your PicoCraft inquiry data. We will delete the message, the device and progress information, and the game state from bug reports that we store. Even without a request, we delete it 180 days after receipt.

To delete an inquiry sent by email, send a deletion request to the same address from the email address you used. We will delete that email address, the message, and any attached diagnostic information.

To request deletion of analytics or crash data already sent to Firebase, or to withdraw consent to AI use of an inquiry, contact the address above. For Firebase, include “PicoCraft Firebase data deletion request,” when you used the App, the OS, and the app version. We will investigate and use the service’s deletion tools for data we can identify. The App has no accounts, and we do not link analytics or crash identifiers to email addresses, so these details may not be enough to identify individual records. In that case, we will explain the limitation; after you stop sending data, deletion follows the retention periods in Section 2. Individual contributions cannot be removed from aggregate data that cannot be linked to a person.

Neither the save data on your device nor its iCloud backup is sent to our servers. To delete your save data, clear the App’s storage in Android Settings or uninstall the App. The iCloud backup remains after you uninstall the App; to delete it, delete the App’s data from iCloud storage management in the iPhone or iPad Settings. Deleted data cannot be restored.