Skip to content

Keepbreaker for iPhone

Privacy policy

Last updated: October 30, 2026

Keepbreaker is developed by Anthony Laibe, the contact responsible for this app and website. This policy explains how the iPhone game and keepbreaker.laibe.cc use information and the choices available to you. Contact [email protected] about privacy. You do not need to create a Keepbreaker account to play against the built-in bots.

Progress saved on your device

The game saves your rating, match results, achievements, current match, sound preference, purchase entitlement cache and tutorial progress on your device. These records keep your progress between sessions. The game does not upload this local profile to a Keepbreaker account server. Device backups may include app data according to your Apple settings.

Purchases

Apple processes the optional, one-time Remove Ads purchase. Keepbreaker uses StoreKit to read the product price, verify transactions and check whether you own the purchase. The game does not receive your payment card details. Apple retains purchase records under its own policies. Use Restore purchase on the battle selection screen to restore an eligible purchase.

Game Center

If you sign in to Game Center, the game accesses your Game Center nickname and submits achievement progress and leaderboard scores to Apple. Leaderboards and achievements follow your Game Center privacy settings. The game also works while you are signed out. See Apple's privacy policy.

Advertising and consent

The free version uses Google AdMob for interstitial ads before matches. Google's SDK may process your IP address (including approximate location derived from it), device or app identifiers, diagnostic and performance data, ad impressions and interactions. These support ad delivery, measurement, analytics and fraud prevention. Google and participating advertising partners may process this information; the consent form identifies applicable partners and purposes.

Google's User Messaging Platform asks for privacy choices where required before ads are requested. When available, use Ad privacy choices on the battle selection screen to review or change those choices. Declining consent does not prevent you from playing. Depending on your choices and location, ads may be limited or unavailable. An advertising consent form is separate from Apple's permission for cross-app tracking.

The current game does not request access to Apple's advertising identifier through an App Tracking Transparency prompt. Buying Remove Ads stops future interstitial ads; it does not erase information already processed by an advertising provider. See Google's privacy policy and how Google uses information from apps that use its services.

Optional Jev AI battles

Jev AI battles use your own TypeSafe API key. If you add one, it is stored in your device's Keychain, is not included in backups that can be restored to another device, and is sent only to TypeSafe with each request. You can change or remove it in the game at any time.

When you choose a Jev AI battle, descriptions of the current battle are sent to TypeSafe to obtain the opponent's decisions. These include lane situations, troop types and counts, resources, tower health and time remaining. The request payload does not include your Game Center nickname, email, payment details or local match history. Like other online services, the receiving service can process connection information such as your IP address. Bot battles do not require this AI service. See TypeSafe for information about the service.

Your choices and retention

Local progress remains in the app's storage until it is removed. Deleting the app removes its local data from that device; it does not delete Apple purchase records, Game Center records, device backups or information held by advertising and AI providers. Those services apply their own retention policies and privacy controls.

Depending on your location, you may have rights to access, correct, delete or obtain a copy of personal information, object to or restrict processing, withdraw consent and complain to your data protection authority. Contact the developer through the support page for questions or requests concerning Keepbreaker. For data held by Apple or Google, their privacy pages also provide account controls and request channels.

The website

keepbreaker.laibe.cc is served by the developer and delivered through Cloudflare, which processes connection information such as IP addresses to deliver and protect the site. See Cloudflare's privacy policy.

Each request is logged with the IP address, the time, the address requested and the browser, to run the site and diagnose problems. These logs are kept until newer requests push them out, and are not backed up.

Visits are counted with Umami, which the developer runs, so no third party receives this data. It sets no cookies and stores no IP addresses. For each page view it records the page address, the referring page, the browser, operating system, device type, screen size and language, how fast the page loaded, and the country, region and city derived from the IP address. Clicks on the App Store button are counted as downloads. Page views are grouped into visits by an identifier derived from the IP address and browser that changes every month. laibe.cc and the sites of the developer's apps share one count, so a visit that moves between them counts once.

The website loads no fonts or scripts from other services and shows no advertising.

Purposes, legal bases and service providers

Game progress and purchase verification support the service you request. Advertising consent is requested where required, and can be withdrawn through the available privacy controls. Website operation, troubleshooting and attack prevention serve the legitimate interest of maintaining a secure and reliable service, and visit counts the legitimate interest of knowing how the site is used. If you email support, your address and message are used to answer your request and handle necessary follow-up.

Apple, Google, TypeSafe and Cloudflare may process information outside your country under their applicable privacy terms and transfer safeguards. Their policies explain their roles, retention periods and available privacy controls. Contact the developer if you need help identifying the provider responsible for a particular request.

Changes

This page will be updated when the game's data practices change. The date above identifies the current version.