Privacy Policy — Farmia Fields
Last updated:
Information about personal data in Farmia Fields, developed and published by Muonity.
1. Who is responsible
Farmia Fields is an Android farming game developed and published by Muonity. The controller responsible for the processing described here is Lukáš Pokorný, an individual operating under the name Muonity. Muonity is a project name, not a separate company.
For privacy questions or requests, contact dev@muonity.com. Website: muonity.com. This policy covers the game and its associated online services. It describes the current version, including services present in testing; it does not represent a promise that future features are available.
2. Google sign-in and account information
The current Android sign-in flow uses your Google account and Firebase Authentication to identify your game account and restore access to cloud progress. It processes a Firebase user identifier, linked Google account identifiers, sign-in credentials and tokens, and profile information such as a display name and email where supplied by the sign-in service. We do not receive your Google password.
Existing accounts can retain their previous Firebase identity. A fresh installation is directed to Google sign-in rather than creating a new anonymous farm. Authentication services also process technical information, including IP addresses and service logs, to operate the account and prevent abuse. Signing in does not itself authorize optional analytics.
3. Farm progress and cloud services
Our cloudFarm backend uses Firebase and Google Cloud services, including Cloud Firestore, to store and validate game progress. Records include your account identifier, profile, level, EXP, Coins, Gems, seeds and other inventory, crops, trees, flowers, herbs, plots, timers, decorations, achievements, reward claims and relevant activity. Save revisions, timestamps and operation receipts help synchronize changes and prevent duplicate rewards or commands.
The game stores account-specific local caches and pending actions. Online operations and rewards depend on server validation; cached or pending progress is not necessarily a confirmed cloud save. Some activities can be displayed or queued offline, but social actions and other online features need a connection. We do not promise unrestricted offline play or an automatic merge of conflicting changes.
This account-linked gameplay processing is needed to provide the requested game and is separate from optional Analytics events. Turning Analytics off does not prevent the backend from processing the actions needed to play and save your farm.
4. Social profiles and farm visits
When you set up and publish your social profile, other players can find its public Player ID, chosen nickname, preset avatar, level, profile creation date, friend count and achievement completion information. Your Firebase UID and Google email are not included in the public profile returned by the social service. Avoid using sensitive information in a nickname.
We store profile and nickname reservations, friend requests and relationships, visit and interaction records, daily action limits, and recent activity. Confirmed friends can view supported farm areas and perform permitted helping actions or in-game pranks, such as adding bugs or weeds. Farm projections expose the gameplay information needed for these visits, rather than your private account credentials or wallet.
You can decline requests or remove a friend to end further access through that relationship. Recent social activity is limited to 20 displayed records; that display limit does not mean all underlying server records are deleted at the same time. To report misuse or request removal of profile information, contact dev@muonity.com.
5. App Check, Play Integrity and security
The normal Android build integrates Firebase App Check with Google Play Integrity. Google processes integrity and technical signals to assess whether requests come from the expected app and device environment. Our backend receives and verifies authentication and App Check tokens to protect game data and services.
These checks are distinct from analytics and do not depend on enabling the Usage Analytics switch. Private diagnostic builds can use the Firebase debug provider for testing instead of Play Integrity; this is not a claim that a production device-verification test has passed. Technical request, error and security logs may be processed by Google Cloud infrastructure.
6. Usage analytics and crash reports
Google Analytics for Firebase and Firebase Crashlytics are integrated for optional usage measurement and stability diagnostics. In the current introductory screen, the Usage Analytics switch initially appears ON. Collection remains disabled until the choice is successfully saved by pressing Agree and Play. Keeping it ON and confirming enables usage analytics and crash reporting; switching it OFF before confirming keeps both disabled.
You can change the stored choice in Settings → Usage analytics and crash reports. The preference is stored on the device and restored on later launches. Advertising choices are managed separately. A default switch position, Google sign-in or acceptance of the Terms is not, by itself, consent to optional processing.
Enabled Analytics can process app-instance identifiers, app and device information, sessions and defined gameplay events such as game opening, planting, harvesting, seed acquisition, leveling up, fertilizer use and ad interactions. Custom event parameters are restricted to permitted game identifiers and numeric values. We do not intentionally include your name, email, Firebase UID, sign-in tokens or free-form text in those custom events, and do not set an Analytics User-ID. In-game seed acquisition events are not a statement that real-money purchases are active.
Crashlytics can process crash traces, installation identifiers, app version, device characteristics and selected error codes. Crash information can be stored locally while reporting is disabled; enabling reporting can allow pending reports to be uploaded. Technical identifiers should not be assumed to be anonymous.
Disabling the setting stops further configured optional collection, resets local Analytics data and requests deletion of unsent crash reports. This does not erase data already received by the services. Analytics advertising storage, advertising user-data consent and advertising personalization are denied in the current integration. For optional processing we rely on consent where required; the interface must obtain a valid choice, including any necessary parental authorization.
7. Advertisements and advertising choices
The app includes Google AdMob rewarded-ad support and Google User Messaging Platform (UMP). The reviewed configuration uses Google test ads; live verified rewarded-ad grants are disabled. We do not describe commercial rewarded ads or a particular reward as currently available.
Where the ad SDK runs, it can process IP addresses and approximate location derived from them, app/device identifiers where permitted, ad interactions and diagnostic or fraud-prevention information. Test or non-personalized ads are not a guarantee of zero data processing. UMP evaluates privacy requirements after the introductory choice and shows a configured message where required. Ad initialization or preloading depends on UMP allowing ad requests, which may rely on an earlier saved choice.
Use Settings → Ad Privacy Choices when available to review the advertising options provided by UMP. Availability depends on its requirements and configuration. Changing an ad choice discards previously loaded ads. Turning Usage Analytics off is not the same as changing advertising choices. Before any live advertising rollout, the configuration and this policy must reflect the applicable audience and consent requirements.
8. Google Play Billing and purchases
Google Play distributes the app. Google Play Billing and server purchase-verification code are present, but real-money purchases are disabled in the reviewed configuration. Coins and Gems can be game resources without representing a paid purchase.
If purchases are enabled in a later release, their data processing will be disclosed before use. The prepared integration would send product identifiers, purchase tokens, transaction status and account-linked references to Google and our verification backend to validate, grant, restore or revoke entitlements. Google would process payment details; Muonity would not receive full payment card details. This describes prepared functionality, not transactions currently available to players.
9. Notifications and device registrations
Firebase Cloud Messaging supports optional notifications about farm conditions, rewards and social activity. Settings provide a master control and individual categories, and Android notification permission is separate. The app does not request Android notification permission during the first-launch introduction. Device behavior can depend on the Android version and your system settings.
Notification processing uses account-linked installation/device identifiers, an FCM registration token when delivery is permitted, category preferences, timestamps, foreground/background presence, delivery records and the game conditions needed to select a relevant notification. Token collection is gated on the app preference and system permission. A registration and short presence updates can still be sent without a push token when notifications are off, to keep account-wide delivery state accurate and suppress unnecessary messages.
Friend Activity and Special Events preferences default off. Special Events is prepared infrastructure, not a promise of a currently active broadcast service. You can manage notifications in the game and Android settings. Turning off notifications does not delete your account or cloud progress.
10. Purposes and legal bases
- Providing the requested service: authentication, cloud saves, server-validated gameplay and the social functions you request, where necessary to perform our agreement. Providing these functions requires the corresponding information.
- Consent where required: optional Analytics and crash reporting, advertising-related processing and optional notifications. Refusing optional measurement does not remove core gameplay access. Withdrawing consent applies to future processing.
- Legitimate interests: proportionate security, fraud prevention, reliable service operation and handling support, subject to a balancing of your rights. This does not replace consent when consent is legally required.
- Legal obligations: responding to lawful requirements or retaining information when applicable law requires it.
If you contact us, we process the email address and information you supply to respond, resolve the request and document necessary action. Please send only what is needed, not passwords or access tokens.
11. Recipients and international transfers
Google provides the authentication, cloud infrastructure, database, integrity, measurement, messaging, advertising and distribution services described above. Google and its service providers receive the information needed for each service. Their role as processor or independent controller depends on the service and applicable terms. Other players receive the public profile and friend-visible information described in this policy. Information may also be disclosed to authorities or professional advisers when legally required or necessary to protect legal rights. We do not sell your personal information.
Processing may occur outside your country or the European Economic Area. Deployment records place the Firestore database and notification workers in Europe and some backend functions in the United States; this does not mean all Google processing is confined to those locations. Applicable transfer arrangements may include adequacy decisions or standard contractual clauses. You can ask us about the safeguards relevant to our processing.
12. Retention and security
Account, farm and social records are retained to provide the account, progress and relationships until they are no longer needed or a valid deletion request is fulfilled, subject to limited legal or security exceptions. Some operation and reward receipts are needed to prevent replay or duplicate grants. Local caches and settings remain until cleared through app/device controls or removed with the app; device backups may behave differently.
The notification code schedules event, batch and delivery history for deletion after seven days and cleans up device registrations inactive for 30 days, with safeguards for active bindings. Cleanup and provider TTL processing are asynchronous, not guarantees of deletion at an exact second. These periods do not apply to all account data or Analytics retention.
Analytics, Crashlytics, authentication logs, infrastructure logs and backups follow their relevant service settings, policies and legal requirements. We do not state an unverified universal server-retention period. If information must be retained after a request, we will explain the category, purpose and applicable period or criteria.
Network communication uses encrypted connections. Authentication, App Check and server-side access checks protect account operations. No system is completely secure, and transport encryption is not a promise of end-to-end encryption or encrypted local backups.
13. Age and young players
Farmia Fields is intended for players aged 13 and over. It is not intended for children under 13. This audience setting does not mean every player aged 13 can independently consent to all processing: the age for digital consent and requirements for parental authorization vary by country.
Where applicable law requires a parent or guardian to authorize consent-based processing, a young player cannot provide that authorization merely by pressing Agree and Play. Optional measurement should remain off unless the necessary valid authorization is available. We do not claim that a verified age-check or parental-consent mechanism has been implemented.
We do not knowingly ask children under 13 to provide personal contact details through the game. If you believe such information has been processed, or you are a parent or guardian seeking assistance, contact dev@muonity.com. We will assess the request and take appropriate action.
14. Your rights and account deletion
Where GDPR applies, you may request access, correction, erasure, restriction and, where applicable, data portability. You may object to processing based on legitimate interests and withdraw consent without affecting processing lawfully carried out before withdrawal. You may complain to your competent data protection authority, including the Czech Office for Personal Data Protection where relevant.
Use our Farmia Fields Account Deletion page to start an account or data-deletion request by email. You may also contact dev@muonity.com about other privacy rights. We may need proportionate verification; a public Player ID alone does not prove account ownership.
Deleting the app does not itself delete the cloud account. Deleting game data does not delete your Google account or all records Google controls independently. You can use Google privacy controls for those records.
15. Changes and contact
We will update this policy when relevant features, services or requirements change. The revision date appears above. Where required, we will provide additional notice or seek a new choice before new optional processing.
Controller: Lukáš Pokorný, an individual operating under the name Muonity
Email: dev@muonity.com
Website: muonity.com