Privacy Policy

This policy covers the Hopora mobile game and the hopora.download website. It describes what the game and the site actually do — there is no account, no login and no server of ours that stores your play data.

Who we are

Hopora is developed and operated by Berkay Kaynar, an independent developer based in Türkiye, who is the data controller for the limited processing described here. Contact: berkay.kaynar65@gmail.com.

What the game stores on your device

Your score, banked sparks, unlocked couriers and outfits, sound and haptics settings, chosen language and the "Remove ads" purchase state are stored in local storage on your device. The game does not send these records to a server of its own and starts no analytics or cloud-save SDK. Uninstalling the game removes them.

What this website collects

The site sets no cookies, embeds no trackers and runs no analytics. Our web server keeps standard access logs (IP address, time, requested page, user agent) to operate the site securely; these logs are kept for at most 30 days and are not used to profile visitors. Pages are served from our own server — no third-party fonts, scripts or CDNs are loaded.

Advertising

The game uses the Google AdMob advertising SDK, with Unity Ads in the mediation chain. Ads appear in two places only: two optional rewarded ads on the result screen (revive and double reward), and an occasional interstitial between runs — at the earliest on every third restart, with at least 90 seconds between them.

While the ad SDK is running, the ad networks may process data such as your IP address, device and app information and your advertising identifier in order to select ads, cap their frequency and prevent fraud. That processing is governed by those networks' own policies: Google, Unity.

Players in the European Economic Area, the United Kingdom and Switzerland are shown Google's consent (UMP) form on first launch; without consent no personalised ads are requested. The legal basis for personalised advertising is your consent, which you can change at any time through "Privacy options" in the pause menu. On iOS, tracking permission is requested through the App Tracking Transparency dialog; declining leaves the whole game available.

After the one-time "Remove ads" purchase the ad SDK is never started, and the revive and double-reward features are granted without any ad.

Purchases

"Remove ads" is a one-time, non-consumable product sold through the App Store or Google Play. Payment is handled by the store; the game never sees or stores card or billing data. The entitlement is read from the store receipt and flagged locally, and "Restore purchase" re-enables it on a new device.

Permissions

The game does not access the camera, microphone, location or contacts. Internet permission is used for ad and store requests. On supported devices it uses haptic feedback, which can be turned off in the pause menu. The behaviour of the operating system's own backup service is governed by its settings.

Children

The game is suitable for general audiences and is not directed at children under 13. We do not knowingly collect personal data from children. Where ad consent applies, the ad SDK is configured to request non-personalised ads unless consent is given.

Your rights

Because we hold no account and no server copy of your play data, there is usually no personal data of yours for us to access, correct or delete — deleting it is as simple as uninstalling the game. For the ad identifiers processed by the ad networks, and for our server access logs, you can exercise your rights under the GDPR, the UK GDPR and the Turkish KVKK (access, rectification, erasure, restriction, objection, portability, and withdrawal of consent) by writing to berkay.kaynar65@gmail.com. You also have the right to lodge a complaint with your local supervisory authority — in Türkiye, the Personal Data Protection Authority (KVKK).

Requests concerning data held by Google or Unity are best addressed to them directly through the policies linked above; we will help you if a request reaches us instead.

Changes

We may update this policy. The date below always shows the current version; material changes will be summarised at the top of this page.

Last updated: 14 September 2026