Eggy Snake Privacy Policy

OpenHealth Inc
Contact: info@openhealth.co.jp

Effective date: 2026-11-21

Summary

Eggy Snake works offline and does not require an account. OpenHealth Inc uses Google Firebase Analytics and Crashlytics to understand gameplay and diagnose problems. Usage and crash reporting is optional: it starts only after you allow it in the European Economic Area (EEA), the United Kingdom, Switzerland and in Canada on devices set to French, which we use as a stand-in for Quebec, and is on by default elsewhere, subject to the age and permission protections below. You can turn it off in Settings. We do not sell your personal information for money, and we do not use these Firebase usage and crash reports for targeted advertising or tracking across other companies' apps and websites; Google AdMob and Meta receive what the next paragraph describes.

From 2026-11-21, for eligible players, Eggy Snake also uses Google AdMob to serve optional rewarded hint-refill ads and, from Level 11, a Play-screen banner ad, and uses the Meta SDK to measure ad-campaign installs. Google AdMob receives ad requests with device and consent signals, approximate location derived from network addresses, ad-interaction data, and, only when tracking is allowed, the advertising identifier. Where the optional reporting consent card runs (the EEA, the United Kingdom, Switzerland, Canada on devices set to French, or when your region cannot be determined), Google requests ad consent where required and the Meta SDK stays off. In opt-out regions while Share usage and crash reports is on, the Meta SDK sends the install report to Meta and includes the advertising identifier only when tracking is allowed; switching off takes full effect at the next app start. Players flagged as minors and players without an age answer are excluded from ad SDKs, tracking prompts and install measurement, and receive free hint refills.

Usage and crash reports

When reporting is on, we collect app-instance and installation identifiers; random event, session and attempt identifiers; app and operating-system versions; device information; and gameplay events. Events describe app launches and sessions, tutorial steps, level starts and results, hints and restarts, Daily play, result screens, share-button actions and outcomes, and reminder choices and permission results. They include limited counts, timing information and public puzzle identifiers. Crash reports include technical crash logs, stack traces, device and app state, and limited diagnostic information, including relevant gameplay actions before a failure.

These reports do not contain your name, email address, age, birthday or contacts. Google Analytics derives approximate location, such as country or region, from network addresses. We do not request GPS or precise location. We do not send saved puzzle routes, save codes, shared messages or recipients. We do not use Google Signals or advertising data sharing for these Firebase reports, and we do not assign an account User ID to these reports. Installation identifiers can recognize repeat use of the same app installation; the reports are not anonymous.

Network services receive an IP address when a connection is made; this is separate from location fields in gameplay reports.

Your choices

In the EEA, the United Kingdom, Switzerland and in Canada on devices set to French, which we use as a stand-in for Quebec, usage and crash reporting remains off until you select Allow on the optional reporting card. Choosing Not now or dismissing the card keeps it off. If the app cannot determine which regional choice applies, it shows the same card. The regional choice uses information available on your device, not an IP-location lookup.

Elsewhere, usage and crash reporting is on from first launch once any required store permissions are resolved, unless we know the player is a minor. The privacy information in the app and store describes this collection. You can opt out at any time: open Settings and turn off Share usage and crash reports. The same switch lets eligible players change their choice in every region. You can keep playing when reporting is off.

Turning reporting off stops new optional Firebase collection and uploads and clears Firebase reports waiting in the app. Until the app closes, Meta's component may fetch its configuration (IP address and app ID) and record session timing locally; no event is sent. An install report already in flight may complete. Local Meta data is deleted at the next app start, when switching off takes full effect. It does not automatically delete reports already received. We do not upload earlier gameplay when reporting is enabled later. Reset progress and reporting controls are separate. To request deletion of reports already received, use the instructions below.

Where we ask for opt-in permission, we rely on your consent for reporting, which you can withdraw using the switch. Elsewhere we process optional reports to understand and maintain the game where applicable law permits, with the opt-out described above. Required store permissions are separate from this reporting choice.

Progress and settings

Your saved game progress and settings are kept on your device until you delete the app or reset progress. Settings include a Reset progress control that erases your progress after two confirmations. Your phone's own backup (iCloud on iPhone, Auto Backup on Android) may include your game progress and settings, so they can return when you restore or move to a new phone. We do not receive your saved game through this backup. Gameplay statistics described above are separate from your saved game.

Providers and retention

Google processes Firebase usage and crash reporting data on our behalf as a processor or service provider under the applicable Firebase and Google Analytics terms, and we do not enable the use of those Firebase reports for advertising; Google AdMob and Meta receive the ad and install-measurement data described in Summary. Processing can take place outside your country, including in the United States. We use the international-transfer safeguards provided in the applicable Firebase and Google Analytics data-processing terms. You can contact us for information about these safeguards. See Google's Firebase privacy information and Google Analytics terms.

Our configured Google Analytics user-level and event-level retention period is 2 months. This setting does not set the lifetime of all aggregate reports or separate exports. We keep raw measurement exports only for as long as needed to analyze gameplay and verify reports, then delete them. Crashlytics retains crash traces and associated identifiers for 90 days before its removal process begins; removal from live and backup systems is not instantaneous. Installation identifiers used by Firebase services have a separate deletion lifecycle. We keep support correspondence only for as long as needed to resolve your request and meet applicable legal obligations. See Analytics retention controls and Firebase retention information.

Security

Reporting data is encrypted in transit to Google. Access to the reports is limited to people who need it to operate and improve the game. Your saved game remains on your device and in any backup managed by your phone's operating system.

Reminders

If you choose a daily reminder, it is a local notification scheduled by your device. No push token is sent to us. You can turn it off at any time in the game's Settings or in your device's notification settings. When reporting is on, we record limited reminder actions and outcomes as described above.

Sharing

Sharing a result uses your device's share sheet. The text and store link you share go to the person and app you choose, not to us. When reporting is on, we record the share action and its available outcome, but not the message, recipient or chosen app.

Deletion and privacy requests

To ask OpenHealth Inc to delete your usage or crash reports, email info@openhealth.co.jp with the subject Eggy Snake privacy request. No game account is needed. Tell us which app and device installation your request concerns. Do not send passwords, identity documents or your saved game. We may ask for limited information needed to verify your request and locate the relevant reports.

Because we do not attach your name or email address to reports, an email address alone may not let us find them. We will explain any identification or deletion limits, what we can delete, and any data that must remain for a legal reason. Provider retention and backup-removal periods can apply. Turning reporting off, resetting progress or uninstalling the app does not by itself delete reports already received by Google.

Your privacy rights

Depending on where you live and which laws apply, you may ask to know whether we process your personal information, access or receive a copy of it, correct it, delete it, restrict its use, or object to processing. Where we rely on consent, you may withdraw it without affecting earlier lawful processing. You can complain to your local privacy regulator.

Residents of Texas and other US states may have rights to access, correct, delete and obtain a portable copy of personal information, and to opt out of sale, targeted advertising or certain profiling that makes important decisions about them. We do not sell personal information for money, use Firebase usage and crash reports for advertising, or use personal information for profiling that makes important decisions about you. For eligible players from 2026-11-21, Google AdMob and Meta receive what Summary describes: the install report and, where tracking is allowed, the advertising identifier are used to measure our ads, which some US state laws treat as sharing for targeted advertising. You can opt out by turning off Share usage and crash reports in Settings (which stops optional Firebase reporting and takes full effect for Meta at the next app start, subject to the residual behavior described in Your choices) and by denying or turning off the system tracking permission in your device's privacy settings. We will not discriminate against you for exercising applicable rights.

Send rights requests to info@openhealth.co.jp. If we deny a request, you may appeal by replying with Privacy appeal in the subject. We will explain our decision and any further complaint route. Texas residents can contact the Texas Attorney General. Applicable rights and exceptions depend on your jurisdiction.

Contacting support

If you email us, you choose to send your email address and the contents of your message, including any attachments. Please send only what is needed to explain the problem and avoid passwords or sensitive information. We use your message only to answer your request and to fix the problem. To ask about your message or to have it deleted, write to info@openhealth.co.jp.

This website

This website is a static page hosted on Cloudflare Pages. It contains no analytics scripts, cookies, external fonts or embedded media. Like any web host, Cloudflare may process technical request data, such as your IP address, when you load the page.

Children

Eggy Snake is not directed at children under 13. We disable usage and crash reporting for players we know are minors, including teenagers under 18. Where the platform indicates an age or parental-permission requirement, we use the store's age-range and permission signals to apply it. We do not ask players for a date of birth, send store age information to Firebase, or use it for marketing. Raw age information is discarded after verification. Required permissions that are pending, declined or revoked do not enable the changed feature. A parent's approval does not turn on reporting for a known minor. If you believe we have collected a child's information, contact info@openhealth.co.jp.

Changes

If the app's data practices change, this page will be updated and the effective date above will change. Before a significant change takes effect, we provide notices to the platform stores and request any notices, acknowledgements or parental permissions required for affected users.