Privacy policy

Player ID and nickname

When the app first opens, it generates a random player ID and stores it on your device; this ID is not linked to your name, phone number or the device's advertising ID. You are given an automatic nickname such as “Climber_4821”; you can change it in Settings > Player name. Nicknames are unique and are shown to other players on leaderboards, in the league, in Royale and in challenges. Do not use your real name or personal information as a nickname.

Game information sent to our server

• Scores: player ID, nickname, mode (daily or free), date, run seed, score, camp, run duration, control type (tilt or touch) and app version; to show leaderboards and your rank.
• League: your league tier in 4-hour rounds, your best score in the round and your last round result.
• Ghost recordings: position samples of your character (40 per second) during your best daily run, runs you share and challenge runs, together with the score and player ID. These recordings are shown, with your nickname, as a rival “ghost” to people who open your challenge link and to other players racing the same course in Royale.
• Challenges: the creator's ID and nickname, course and score; and the ID, nickname and score of everyone who plays the challenge.
• Friends: your friends list is stored on your device as nicknames. To show your friends' scores, these nicknames are sent to the server as a query; adding a friend does not notify them.

When you share a challenge link, the link contains your nickname, score and player ID; anyone you send it to can see them.

Royale and AI rivals

Royale is a 10-player ghost race. Rivals are ghost recordings of real players who played the same course, shown with their nicknames. If there are not enough real players, no internet connection or the server cannot be reached, missing rivals are filled with AI rivals. AI rivals are generated entirely on your device by the game's own simulation and carry a bot icon next to their names. Taking part in Royale means your ghost recording may be used as a rival in other players' Royale races.

Technical records and hosting

The server runs on Cloudflare Workers and Cloudflare D1. To prevent abuse, your IP address is used temporarily, in memory, for request rate limiting; it is not written to the database. Cloudflare may keep request logs to operate the service and investigate errors. Communication between the app and the server is encrypted over HTTPS.

Information kept on your device

Settings, your records, skins and achievements, your own ghost recordings, your friends list, purchased packs, ad counters and consent status are stored on the device. In-game measurement events are held only in device memory while the app is open and are not sent anywhere; the app contains no analytics SDK.

Notifications

The mobile app (Android and iOS) does not send notifications and does not ask for notification permission. The web version of the game, played in a browser, offers optional web notifications: if you turn them on, the notification subscription created by your browser (endpoint and keys) is stored on the server with your player ID; it is deleted when you turn them off or the browser invalidates the subscription.

Ads and Google services

The app includes Google Mobile Ads (AdMob) and Google’s ad privacy choices framework (User Messaging Platform). Test builds use Google's test ads; using test ads does not mean that no data is processed. When it runs, the SDK may collect IP address (from which approximate location can be inferred), device or other identifiers (the advertising ID on Android; the IDFA on iOS if you allow it), app interactions and diagnostic information for advertising, analytics and fraud prevention, and share them with Google. This data is processed under Google's own policies; the app does not send it to us.

When are ads shown? There are no ads during play or at launch. Rewarded ads are optional: after a fall you can choose to watch one to continue. Interstitial ads appear only when leaving the end-of-run screen and never in your first session; the consent form (where required) appears in the main menu after your first three runs, and no interstitial is shown before that. Ad frequency settings may be read from a remote configuration file; that request contains none of your game data, but your IP address may appear in the logs of the service hosting the file.

Consent. In regions where it is legally required, such as the European Economic Area and the United Kingdom, Google's consent form is shown for personalised ads. You can change your choice later in Settings > Privacy choices (this row appears only where consent is required). If consent cannot be obtained or there is no internet connection, ads that are not permitted are not loaded; the game keeps working. Ad requests do not tag the app as child-directed, because the game is not directed at children.

Tracking permission on iOS (App Tracking Transparency). On iOS, Apple's tracking permission may be requested within Google's consent flow. If you do not allow it, the advertising identifier (IDFA) is not given to the app or the ad SDK; ads may still be shown and the game works the same. You can change this in iOS Settings > Privacy & Security > Tracking.

Advertising ID on Android. You can reset or delete your advertising ID in your device's Settings > Google > Ads (on some devices Settings > Privacy > Ads).

Google Privacy Policy · How Google uses information from apps that use its services · Google Mobile Ads data disclosure (Android) · Google Mobile Ads data disclosure (iOS)

Skin packs

Most skins are unlocked by playing; three skin packs can be bought as in-app purchases. Payment is handled by Google Play or the App Store; your card and payment details never reach us. Your purchase record is kept in your store account; the app only stores on the device the purchase status reported by the store (product ID, transaction state). You can bring your packs back on the same store account with Restore Purchases.

Retention and deletion

Exact retention periods for score, league, ghost and challenge records on the server have not yet been set; these records may be kept until you ask for them to be deleted. There is no delete button in the app; you send a deletion request by email: data deletion request. Uninstalling the app deletes the data and the player ID on the device, but not the records on the server.

Exact retention periods for hosting logs and support correspondence have not been set. Deleting the records on the server does not mean these copies are deleted at the same time.

Recipients

Game data is processed on Cloudflare's infrastructure; Google is used for ads and Google Play or the App Store for purchases. Support emails arrive in a Gmail mailbox. Processing by these services may involve systems outside Türkiye. We do not sell your data.

Audience

Last Climber is not designed for children; ad requests do not tag it as child-directed.

Requests and changes

For information, correction or deletion of your data, write to canavcilar77@gmail.com. To avoid disclosing or deleting another player's data, we may ask you to verify that the nickname is yours. When data practices change, this page is updated.