Zipline Jam

Privacy policy

Effective date: 11 November 2026

Developer: MKTeam, https://kodsiz.uz/

App: Zipline Jam for Android (package com.mkteam.ziplinejam)

Zipline Jam is a puzzle game. The built-in levels can be played offline; your progress is saved to your game account when you are online, and the world ranking, the daily wall and new walls need an internet connection. This policy says what data the game uses, why, who receives it, how long it is kept and how you can delete it.

In short

Data we collect and why

Account and game data, stored on our game server

DataWhy
Account id. An anonymous Firebase Authentication account is created automatically the first time you start the game.To recognise your game, keep your progress and place you on the leaderboard.
Player tag. A short code shown in your Profile (for example "Player tag: 3f04ca14"). It is derived from the account id and identifies a player without revealing the id.To refer to a player in reports and deletion requests.
Player name. Generated for you (for example "Climber 1234"), or one you type yourself.Shown to all players on the leaderboard, together with your level and stars.
Verified level clears: level number, stars, the ropes of the winning solution, time.To check results on the server and rank players.
Cloud save: progress, coins, village, streak, missions, attempt counts and the game's settings (sound, vibration, language).To keep your game and restore it.
App version, platform, language, time first seen and time last seen.To serve the right game version and to operate the service.
IP address of each request.Rate limiting. It also appears in web-server access logs, which we use for security and troubleshooting.
Reports. If you report another player's name: your account id, the reported player's tag and the reason.So that names can be reviewed.

Data collected by Google services built into the game

ServiceDataWhy
Firebase AuthenticationThe anonymous account id and sign-in tokens.Sign-in without asking for personal details.
Google Analytics for FirebaseGame events (such as app open, level start, win and fail, hints, ads shown, tab opened, language, errors in the game); an app-instance id; device model, operating system and country-level location as collected by the SDK. Where consent rules do not apply to you, events also carry the Firebase account id as the user id and the SDK may use the advertising ID.To understand how the game is played and to improve levels and difficulty.
Firebase CrashlyticsCrash and error reports with the account id, device model and operating system version.To find and fix crashes.
Firebase installation idAn identifier of this installation of the app.Used by the Firebase services above.
Google AdMob and Google's consent SDK (User Messaging Platform)Advertising ID, approximate location derived from the IP address, device information, ad interactions, and your consent choice.To show ads: rewarded ads, which you choose to watch, and interstitial ads.

Data stored on your device

Saved progress, settings, cached levels, the ropes of your winning solutions, level results waiting to be sent to the server, and your consent choice (stored by Google's consent SDK).

Public information and reports

Your player name, level and stars are visible to every player on the leaderboard. Do not put personal information in your name. You can change it in Profile.

A player can report another player's name from the leaderboard. Offensive names can be replaced by a generated one.

Ads and consent

The game shows ads through Google AdMob. Rewarded ads are always your choice.

In the European Economic Area, the United Kingdom and Switzerland the game asks for your consent, through Google's consent form, before any ad request. If the consent request itself fails (for example because there is no connection), only non-personalised ads are requested. In these regions Google Analytics runs in consent mode with analytics storage, ad storage, ad user data and ad personalisation all set to "denied", and the account id is not sent to Analytics as a user id.

Where Google's consent rules require it, a "Privacy choices" entry appears in Settings. You can change your choice there at any time.

You can also reset or delete the advertising ID in your Android settings.

Who receives data

We do not sell personal data.

Where data is processed

The game server is in the European Union (France). Google services process data on Google's servers, including in the United States.

How long we keep data

Deleting your account and data

In the game: Settings → "Delete my account" → tap again to confirm. This:

The game then starts as a new player.

If the game is no longer installed: use the form on the delete page. It asks for your player tag and a way to reach you (email or Telegram). These requests are handled manually within 30 days.

Uninstalling the app alone does not delete the data on the server.

After deletion, copies can remain in database backups for up to 30 days, and data held by Google (Analytics events, crash reports, ad data) is removed according to Google's retention rules described above.

Legal bases and your rights (EEA and UK players)

We process data on these bases:

You have the right to access your data, to have it deleted and to object to its processing. Use the delete page or the website (https://kodsiz.uz/). You can withdraw consent at any time under Settings → Privacy choices, where it is shown.

Children

The game is not directed to children under 13, or under the age of digital consent in the player's country (up to 16 in parts of the EEA). We do not knowingly collect their data. A parent or guardian can ask for a child's data to be deleted through the delete page.

Security

Data is encrypted in transit (HTTPS).

Changes to this policy

When the policy changes, the new version is published on this page with a new date at the top.

Contact