Snake Conquest — Privacy Policy
Last updated: 1 October 2026
Snake Conquest is an Android game offered under the Mezeey publisher name. This policy explains the information processed by the game and its connected services. It does not cover other Mezeey applications, including VaultCam, which has its own policy.
Privacy and support contact: mezeeyinfo@gmail.com. Website: https://mezeey.info.tr.
1. Playing on your device
You can play core Classic and Battle Royale matches as a guest against AI-controlled opponents. The game stores your chosen player name, built-in avatar, game statistics, level and experience, currency, mission and season progress, unlocked items, cosmetic selections, and game settings on your device. This local information is not automatically a verified online ranking or proof of a purchase.
The game does not request access to your contacts, messages, microphone, camera, photo library, or precise GPS location. Its avatar selector uses game-provided artwork. Advertisers may estimate a general location from an IP address; this is different from accessing GPS.
2. Optional sign-in and cloud backup
If you choose Google sign-in, Google and Firebase Authentication process the account information needed to identify you, including a user ID, email address and provider profile information such as a display name or profile reference when supplied by Google. Authentication also uses technical connection and security information. Your Google password is not provided to Mezeey.
Where email sign-in is available, your email address and password are submitted through the Firebase Authentication SDK to authenticate an existing game account. Mezeey does not store that password as plaintext in its game database or local save. Authentication tokens are used to keep you signed in and authorize account requests. A game email sign-in does not give us access to your mailbox.
If you link a cloud backup from Profile, your game progress and statistics are stored under your account in Firebase Cloud Firestore. The backup includes your player profile, progression, owned-item records and game history. After the initial link, progress changes can sync automatically. If device and cloud saves conflict, the game asks you which save to keep rather than adding their balances together. Signing out stops account-linked synchronization on that device; it does not delete an existing cloud backup.
The current game database is in Frankfurt, Germany. Authentication, support, advertising and other provider services may process data in other locations; not all services are restricted to the database's region.
3. Advertising
Advertising is disabled in closed-test build 37 (0.25.4); this build does not initialize the game's AdMob service or request ads. The app includes an AdMob integration for versions in which advertising is enabled. In those versions, ads between eligible matches and optional rewarded videos can process IP-derived approximate location, device or advertising identifiers, ad/app interactions and technical diagnostic information for delivery, measurement and fraud prevention. Test ads, if used in other test builds, can also transmit technical information. Changes to the active advertising configuration will be reflected in this policy and the store disclosures.
Where required, a consent message is shown before eligible ad requests. You can revisit available ad privacy choices in Settings. Android also provides advertising-ID controls. Declining personalized ads does not necessarily stop all technical processing or all ads. Rewarded videos are optional; an unavailable ad does not prevent core guest gameplay.
4. Purchases and reward services
Real-money purchases are disabled in the current closed-test configuration. The app includes Google Play Billing integration and a purchase-result handler. If Google delivers an existing purchase result, its product identifier and purchase token can be sent with your account identity to the verification service; an unverified result does not grant a purchase.
Before sales are enabled, this policy and the store disclosures will be reviewed for the active payment and reward services. Google Play processes checkout and payment details; Mezeey does not receive your full card number. A purchase token or a game transaction is not the same as a card detail. Planned offers, wheel rewards or premium items shown as unavailable are not completed purchases.
5. Play Games and rankings
Opening Play Games features can involve Google's gamer profile, account identifiers, usage and diagnostic information. Visibility of a Google gamer profile is also subject to your Google Play Games settings. The current production app does not submit unverified local match scores to a global leaderboard. Real-time multiplayer and verified monthly ranking rewards are not active in this closed-test configuration.
6. Connections, support and service providers
The app contacts the Mezeey service for information such as server time, active season and content availability. Network requests can expose an IP address, request time and standard connection details to our hosting provider. Account-specific requests also carry authentication information. These details help operate and protect the service.
If you contact support, we process the email address, message and any screenshots or recordings you choose to provide to answer your request and investigate problems. Please do not send passwords, verification codes, full card details or unnecessary information about other people.
Google/Firebase supplies authentication and cloud storage; Google AdMob supplies advertising; Google Play supplies payment and game-platform services; our web hosting provider operates the Mezeey site and API. We disclose information to providers as needed for these functions and may disclose information when legally required or necessary to address abuse. Advertising providers may process certain information for their own advertising and measurement purposes, as described in their policies.
Mezeey does not sell your personal information. The public Mezeey website does not embed third-party analytics or advertising trackers. Essential session and request-security cookies may be set by the website framework; the hosting service also processes standard access/security logs. Following an external Google link takes you to a separate service governed by its own privacy information.
7. Retention and deletion
Local saves remain until you reset or clear the app's data. Uninstalling or clearing local data does not itself remove your cloud account. Cloud account information and backups are retained to provide your account and restore progress until you request deletion or the service no longer needs them for that purpose.
To request deletion of your Snake Conquest account and its associated cloud progress, use Settings → Privacy → Account and data deletion, or visit our account deletion page without reinstalling the game. Email mezeeyinfo@gmail.com from the address linked to your Google or email game account, with the subject “Snake Conquest — Account deletion”. We verify account ownership without asking for your password or a sign-in code. Automatic server deletion is not enabled in the current test configuration: requests are handled through support. Sending a request or seeing an error in the app does not mean deletion has already completed; support confirms completion.
Deletion covers the game's Firebase account, linked cloud save and associated game-account data. It does not delete your Google account. Data remaining on another device must be cleared on that device. Google-held Play Games data can also be managed through your Play Games profile.
Support records are retained while necessary to resolve the request and related disputes. Limited records may be retained where required for legal obligations or necessary, proportionate fraud/security investigations; they are restricted and not used to restore a deleted game profile. If an exception affects a deletion request, we explain the affected records and applicable retention basis. Provider-managed backups and logs follow the relevant provider's retention and deletion processes.
8. Security and your choices
Account and game-service connections use encrypted transport. Cloud access is restricted to the authenticated account under the configured security rules. Access controls reduce risk but no service can guarantee absolute security.
You can play core matches without Google sign-in, choose whether to link cloud backup, manage available ad consent choices and request account deletion. Depending on your location, you may also have rights to access, correct or receive your information, object to or restrict certain processing, withdraw consent, or complain to your local data protection authority. Contact the address above to exercise applicable rights. Where consent is required, withdrawing it does not make earlier lawful processing unlawful.
Where data protection law requires a legal basis, we rely on providing the requested account/game service for authentication and cloud storage; our legitimate interests in proportionate security, abuse prevention and support; applicable legal obligations; and consent for optional processing where required. You may object to processing based on legitimate interests. Providers operating internationally may process data outside your country; applicable provider agreements and required transfer safeguards apply, not a promise that all processing stays in Germany. Contact us for information about a transfer relevant to your account.
9. Young users
The game's permitted availability and intended age groups are described in its store listing. If you are a parent or guardian and believe a child has provided personal information without appropriate authorization, contact us so we can investigate and arrange appropriate deletion or other action. Do not send a child's identity documents in an initial support message.
10. Policy updates
We update this policy when the game's data practices change. The date above identifies the latest version. Material changes may also be explained in the game or its store listing, and consent will be requested where required.
Google privacy: Google Privacy Policy
Firebase privacy: Privacy and Security in Firebase
Account deletion: Request account and data deletion
