Privacy Policy

Effective September 30, 2026

In short: Blink Strike does not collect, share or sell any data about you. It has no accounts, no ads, no analytics and no tracking, and it never connects to the internet.

Who we are

Blink Strike is an iPhone game made by Alisher Serikbayev (“we”, “us”). This policy explains what happens to information when you play it.

What we collect

Nothing. Blink Strike does not send any information to us or to anyone else. We have no servers, and the game contains no third-party code for advertising, analytics, crash reporting or social features.

What stays on your iPhone

To work, the game saves a few things on your own device:

Your settings: sound, music, haptics and language.
Your best run: the highest stage and the highest score you have reached.
Whether you have finished the first-play tutorial.

Your best run is also kept in your iPhone’s keychain so that it survives reinstalling the game. If you have turned on iCloud Keychain, Apple may sync that small record (two numbers) to your other devices. That sync is run by Apple under Apple’s Privacy Policy; we never see it.

None of this is personal information, and none of it leaves your devices through us. Deleting the game removes your settings; the best-run record in the keychain can remain until you erase it with your device’s settings or keychain tools.

Permissions

Blink Strike does not ask for access to your location, contacts, photos, camera, microphone or any other personal data. It plays sound only when you turn sound or music on, and it mixes with audio from other apps.

Children

Because the game collects no data from anyone, it collects no data from children.

Apple

When you download the game, Apple handles the purchase and download under its own terms and privacy policy. Apple may share anonymous app usage and crash statistics with developers only if you allow it in your iPhone’s settings (Settings → Privacy & Security → Analytics & Improvements).

Changes

If a future version of Blink Strike changes what is described here, we will update this page and its effective date before that version is released.

Contact

Questions about this policy? See the Support page.