Little Food Factory — Privacy Policy

Last updated: 16 September 2026

This policy describes Little Food Factory, published under the EastonHill developer name. For privacy questions and requests, contact games@eastonhill.app.

Privacy choices in the updated game

From version 0.2.0, the game uses Google's privacy-message flow to handle applicable advertising and gameplay-analytics choices together. A message is shown where the configured flow requires one. For eligible players, gameplay analytics may start without a separate prompt where that flow does not require consent. An unavailable or unresolved consent decision does not enable gameplay analytics. Analytics and advertising permissions remain separate.

You can turn gameplay sharing off in the game's privacy settings at any time. An earlier choice to turn it off is preserved across the update. Turning sharing off stops future gameplay-analytics collection and resets local analytics data; it does not delete reports already received. Where available, Google privacy choices in the same menu lets you revisit your consent.

Checking for game updates

From version 0.2.0, the game uses Firebase Remote Config and Google Play's in-app update service to check available updates and supported game versions. Remote Config processes a Firebase installation identifier and technical information such as app version, operating system, language, country and time zone to deliver configuration. This service supports app functionality and is separate from optional gameplay analytics. We do not use Remote Config experiments or personalised configuration rules in this update.

An ordinary update can be postponed. An update marked essential can require installation when Google Play confirms an eligible update is available for your device. This does not give us your Google account password or access to your other apps. Google handles the installation. See Firebase's data information.

Google Analytics for Firebase in version 0.2.0 and later

Eligible gameplay analytics includes game starts, active-play time, merges, deliveries, progression, earned-coin actions, ad interactions and estimated advertising value. Google also processes a pseudonymous app-instance identifier and device/app information, and may derive approximate location from network information. We do not send your name, email address or complete saved board as gameplay-analytics fields. This Firebase integration is additional to the separately controlled legacy statistics service described below; its retention and identifiers are separate.

Google processes these analytics under its service terms and the property's retention settings. Aggregated reports may be kept longer for game-performance comparisons. For identifiable records, contact games@eastonhill.app to request access or deletion. Because the game has no player account, we may need limited additional information to locate a pseudonymous record; turning sharing off cannot recall historical reports.

Your game progress

You do not need a player account. Your board, coins, progress, theme and audio preferences are saved on your device. We do not upload your saved board or provide cloud saves. Uninstalling the game or clearing its storage removes local progress.

Separately controlled legacy gameplay statistics

Gameplay-data sharing is off by default. If you enable it in Settings → Privacy & data, we receive sessions, successful merges, completed orders, purchases made with earned game coins, and advertising outcomes. Records include event times, game/build information, item identifiers or coin amounts where relevant, and random installation, session, event and ad-attempt identifiers. Advertising records may include error codes and estimated impression value supplied by the advertising provider; earned coins are not money.

Our gameplay-event records do not contain your name, email address, advertising ID, hardware identifier, full board or precise location. The random identifiers are pseudonymous, not anonymous. We use these statistics to understand game usage, reliability and advertising integration.

You may turn gameplay-data sharing off at any time without losing game features or rewards. This stops new collection by our statistics client and clears its local queue and statistics identifier. It cannot recall records already received. Enabling sharing again creates a new random identifier. These choices are separate from Google's advertising choices.

Queued records on your device are limited to approximately 1 MiB/1,000 events and expire after 30 days. On the service, an hourly maintenance process removes raw events received more than 30 days earlier; service interruptions can delay cleanup. Build records and aggregate analysis are retained separately.

The game uses Google AdMob. Rewarded advertisements are voluntary and offer the ingredient or coin bonus shown before viewing. Version 0.2.0 also supports automatic ads at delivery breaks after at least five minutes of cumulative active gameplay, with additional delivery and timing limits. Earlier versions use only voluntary rewarded ads. No money purchase is required to play.

Google's advertising SDK and its partners may process IP addresses (including to estimate general location), interactions, diagnostics and device/account identifiers for advertising, analytics and fraud prevention. Processing depends on your device, settings, region and consent choices. Our gameplay-statistics switch does not control this separate processing.

Where required, Google's consent interface presents advertising choices. Settings → Privacy & data includes Advertising privacy choices when this option is required by the SDK. See Google's privacy policy and Google advertising information for Google's processing and controls.

Support, hosting and backups

Support email is handled through Purelymail. Messages you send may contain your email address and information you choose to include. Our support dashboard reads incoming messages from the mailbox and stores case status and outgoing replies. Support correspondence and case records currently have no automatic deletion schedule; contact us to request removal.

Game statistics and the support dashboard are hosted on DigitalOcean, with the application database in Frankfurt, Germany. Fly.io continues to forward requests from older service addresses during the migration; the former database in Stockholm, Sweden is temporarily retained for recovery. Connections from the game to our statistics service and connections to the support mailbox use TLS. Providers may process connection and service diagnostics, including IP addresses, separately from our gameplay-event records. Provider diagnostic retention is governed by their services and is not the game's 30-day event-retention period. Provider processing may involve locations outside your country. See DigitalOcean's privacy policy, Fly.io's privacy policy and Purelymail's privacy policy.

Scheduled encrypted logical backups are retained for seven days. Existing Fly database snapshots may remain for seven days. Manual backups are retained until manually removed and may contain older records. New logical database backup exports are encrypted. When restoring a backup, we apply the current statistics-erasure register before reopening collection. A minimal hashed erasure marker and request receipt are retained without a scheduled expiry to prevent erased installation statistics from being restored or accepted again.

Privacy requests

Email games@eastonhill.app to ask about access, correction, deletion, withdrawal of consent, restriction or objection to processing, or portability where these rights apply. You may also contact your local data-protection authority.

For a gameplay-statistics request, Settings → Privacy & data → Support & data requests lets you copy app information and your current statistics ID. Copy this before turning sharing off, as switching off removes the local ID. Copying does not send an email or enable sharing. You can contact support without an ID, but we may be unable to locate your installation's records. We may request proportionate information to verify a request; a copied ID alone is not proof of ownership.

Verified statistics-erasure requests are processed by an operator across the relevant game's builds. The service removes matching raw events and rejects further submissions for that installation. When the game receives confirmation that its installation statistics were erased, it turns sharing off and clears its local statistics queue and ID. This does not delete your game progress, support correspondence or data independently held by Google. Requests involving those records are handled separately.

Intended audience and changes

Little Food Factory is intended for adults aged 18 and over. We do not ask players to provide a birth date. Contact us if you believe a child has supplied personal information through our services.

We may update this policy when the game or its processing changes. The current version and its update date are available at this page and from the game.