Back to Muonity

Privacy Policy — Pizza Worm

Effective Date:

1. Introduction

Muonity Studio ("we", "us", or "our") develops and publishes Pizza Worm for Android. Muonity Studio is the name used for the independent project operated by Lukáš Pokorný.

This policy explains the information processed by the game, its online services and our purchase-verification backend, why it is processed, and your choices and rights.

Pizza Worm uses Google Play Games Services, Google Play Billing, Firebase Authentication, Firebase App Check with Play Integrity, Google AdMob, Google's User Messaging Platform (UMP), and Google Analytics for Firebase. Online features depend on service availability.

Using the game does not itself constitute consent to optional analytics or personalized advertising. The Usage Analytics switch initially shows ON, but the game does not enable analytics collection on that basis alone. Choose ON or OFF and press Save and play to save your decision. Advertising choices are separate.

2. Information We Process

Game Progress and Preferences

The game stores progress, saved runs, scores and personal records, selected worm skins and tablecloths, sound and music settings, relevant gameplay state and privacy preferences locally on your device. This supports gameplay and preserves your choices between launches.

Local gameplay saves are not automatically uploaded to our backend. Leaderboard scores, purchase-verification information and analytics events are separate data flows described below.

Google Play Games Services

Google Play Games provides player sign-in and online leaderboards. It processes your Play Games player identifier, public player name, submitted scores and authentication or service-related information. Sign-in may be restored automatically according to your Google Play Games settings.

Leaderboard names and scores may be visible to other players. You do not need to create a separate Muonity username and password to play; online features use Google services and may require sign-in.

Firebase Authentication and App Check

Firebase Authentication uses your Play Games sign-in to establish an application identity. Google processes the associated user identifier, authentication credentials and tokens, IP address and technical service information. These are separate from Usage Analytics.

Firebase App Check uses Play Integrity to help verify that backend requests come from the expected app and device environment. Google processes integrity-related technical information and tokens. Our backend receives Firebase authentication and App Check tokens to validate requests and protect purchases against unauthorized use. Turning Usage Analytics OFF does not disable authentication or these security checks.

In-App Purchases and Server Verification

Pizza Worm offers optional purchases of cosmetic worm skins and tablecloths through Google Play Billing. Google processes payments; we do not receive your full payment card details.

The game sends product identifiers and purchase tokens to our verification backend hosted on Google Cloud Run, together with authentication and App Check tokens. The backend verifies purchase status with Google Play and handles purchase acknowledgement, ownership checks and purchase restoration. This processing is needed to provide and protect purchased items.

The backend stores purchase ownership and status records in Google Cloud Firestore, including hashed purchase-token and user references, an obfuscated account identifier, product identifiers, verification timestamps and revocation information. These references remain linkable to purchase entitlements; hashing does not make them anonymous. Raw purchase tokens are processed during verification and in Google purchase notifications, rather than stored as raw tokens in these ownership records.

Google Cloud infrastructure may also process technical request and security logs. Removing the app does not automatically remove backend purchase records, revoke purchases or delete your Google account.

Advertising

Google AdMob provides optional rewarded advertisements. You can choose to watch an available advertisement to continue after a collision. Core gameplay remains available without watching an advertisement.

Ad services may process IP addresses and approximate location derived from them, app or device identifiers where permitted, ad interactions and diagnostic or fraud-prevention information. Non-personalized advertising does not mean that no data is processed. Advertising may be initialized and an available ad preloaded before you choose to watch it, subject to the advertising controls.

The reviewed advertising implementation applies child-directed treatment, disables advertising personalization and requests ads with a maximum content rating of G. It also removes advertising-ID permissions. Google UMP checks whether ads may be requested and provides advertising privacy options where applicable. An advertising consent form is not shown to every player: under-age-of-consent treatment can suppress the European message.

You can manage optional advertising through the game's advertising privacy settings. Ad availability depends on the applicable privacy state and the service. Declining personalization does not guarantee that an ad will be available.

Firebase Analytics — Usage Analytics

Google Analytics for Firebase is used to understand game use and improve the experience. The Usage Analytics switch is ON by default when no saved choice exists, while collection remains disabled until you press Save and play with ON selected. To decline, select OFF and press Save and play. You can change your decision later in Settings → Privacy Settings.

Before the first saved confirmation, neither the default ON switch nor toggling it ON starts analytics collection. Save and play with ON enables collection only after the choice is successfully stored. With OFF, collection remains disabled. On later launches the game restores the confirmed saved choice. An older ON preference without this confirmation is shown again for confirmation and does not itself enable collection; an older OFF preference is preserved.

Analytics can include sessions, game starts, saves and resumes, completed runs, duration, scores, progression, pizza collection, cosmetic selections, rewarded-ad interactions and purchase-related events. The SDK can also collect app-instance identifiers, app and device information, approximate location derived from network information, and automatic lifecycle or purchase events.

Our custom gameplay events do not intentionally include names, email addresses, purchase tokens or leaderboard player names, and we do not set an Analytics User-ID in the reviewed implementation. Analytics is not necessarily anonymous. Advertising-related Analytics consent settings remain denied in that implementation.

Switching Usage Analytics OFF immediately stops further configured analytics collection; press Save and play to retain that decision for future launches. Switching back to ON requires Save and play before collection can resume. Custom gameplay events while collection is disabled are discarded rather than queued for later. Changing this preference does not retrospectively delete information already sent or stop separate authentication, purchase-security or advertising processing.

3. How We Use Information

We do not sell players' personal information.

4. Third-Party Services

These Google services process information under their applicable terms and privacy arrangements. For further information:

5. Legal Bases for Processing

Where GDPR or similar legislation applies, providing features you request may rely on contractual necessity; proportionate security and fraud prevention may rely on legitimate interests; and legally required processing may rely on legal obligations. The relevant basis depends on the activity and jurisdiction.

Optional analytics and advertising storage or processing require consent where applicable law requires it. The preselected ON switch is not consent by itself. The confirmation screen explains what ON and OFF mean before Save and play; advertising choices do not authorize separate Usage Analytics. These controls do not replace any additional legal requirements for valid consent, including those that apply to children.

Additional requirements apply when children cannot provide their own valid consent. A general privacy notice or an adult advertising message does not replace any required parental authorization.

6. Advertising and Analytics Choices

Open Settings → Privacy Settings to change Usage Analytics or access advertising privacy choices. Choose your analytics setting and press Save and play. The game stores that confirmed choice locally and restores it on later launches. Advertising choices use the separate local advertising setting and applicable UMP controls.

You may play with Usage Analytics OFF and without watching rewarded advertisements. Turning analytics OFF affects future configured collection; it does not delete previously transmitted information. Changing advertising choices affects future advertising activity according to the service's controls.

On first launch, ON is selected as the proposed setting only. Save and play with ON requests activation of Analytics; Save and play with OFF records your refusal. If saving the confirmation fails, the new ON choice is not activated and you can retry. Core gameplay is available with Analytics OFF.

7. Data Retention and Deletion

To request deletion of your Pizza Worm account and associated personal data, or specific data without deleting the account, follow our Account & Data Deletion instructions.

Local progress and settings generally remain until removed through available game controls, application data deletion or uninstalling. Android backup and restore settings may affect whether local data is restored.

Our backend retains purchase ownership, verification and revocation records to maintain entitlements and prevent reuse of invalid purchases. These records are not automatically removed when you turn analytics OFF or uninstall the app. No automatic deletion schedule for these ownership records is implemented in the reviewed backend.

Firebase identity records, analytics data, advertising data and Google Cloud logs are subject to the relevant service settings, policies and legal requirements. Their retention periods are not all the same. We do not state a fixed server retention period without verifying the applicable configuration.

Contact dev@muonity.com to request access or deletion concerning our processing. We may need information to identify the relevant records and verify your request; do not send passwords, authentication tokens or payment card details. Applicable legal or justified security requirements may limit deletion. Google-managed information may also require using Google's privacy controls.

8. Data Security

Communication with our purchase-verification backend uses HTTPS. The backend validates Firebase Authentication and App Check tokens and verifies purchases with Google Play before confirming entitlements. Access to purchase records is handled by the backend rather than direct client database access.

Google services use their own transmission and security protections. Hashing purchase references, authentication and integrity checks reduce risks but do not guarantee absolute security. No method of electronic storage or transmission is completely secure.

9. International Data Processing

Google services and hosting infrastructure may process information outside your country of residence, including outside the European Economic Area. Applicable safeguards and transfer mechanisms depend on the service and its contractual arrangements.

See Google's information on international data transfers, the Google Privacy Policy and Google Cloud data processing terms.

10. Children's Privacy

Pizza Worm is intended for players of all ages, including children. The reviewed advertising configuration treats every player as a child for advertising purposes, disables personalization and limits ad content to G. It does not collect a player's age through an age screen. These settings do not mean that advertising, authentication or analytics processes no personal information.

The Usage Analytics switch initially shows ON, including for players whose age is unknown, but collection is not enabled until Save and play confirms ON. The reviewed implementation does not provide a separate parental-consent flow. Neither the default switch nor a child pressing Save and play should be interpreted as verified parental authorization. Advertising safeguards and UMP do not establish consent for separate analytics.

We do not ask children to provide personal contact information through the game. A parent or guardian with questions about a child's information may contact dev@muonity.com. Online player names and scores may be visible on leaderboards; Google account and supervised-account restrictions may affect availability.

11. Your Privacy Rights

Depending on applicable law, you may have rights to access, correct or delete personal information, restrict or object to processing, request portability, withdraw consent and complain to a competent data protection authority.

Withdrawing consent does not affect the lawfulness of processing that was lawfully based on consent before withdrawal. Some information is controlled directly by Google and may need to be managed through its privacy controls. This does not remove your rights regarding our processing.

For questions or requests, contact dev@muonity.com. If you contact us, we use the contact information and request details you provide to respond.

12. Changes to This Privacy Policy

We may update this policy when game features, services or legal requirements change. The updated version will appear at this URL with its actual effective date. Where required, we will provide additional notice or request renewed consent.

13. Contact

Developer: Muonity Studio
Operator: Lukáš Pokorný
Website: muonity.com
Privacy contact: dev@muonity.com

For questions concerning this Privacy Policy or privacy-related requests, please contact us using the address above.