Privacy Policy

At a glance

This policy describes how the current version of Lapa handles data. If our practices change, we will update this page and its date.

Who is responsible

SoftChaosStudio, the developer of Lapa, is responsible for the processing described here (the controller). You can reach us at lapadevs885@gmail.com.

Data stored on your device

The game uses browser local storage on the web and device preferences on native platforms for settings and game state. This can include language and sound settings, tutorial status, scores and records, campaign progress, coins and cosmetics, notification preferences, nickname and queued leaderboard submissions, purchase entitlements, consent state kept by the advertising SDK, and cloud-sync metadata. These values support the game, restore local progress and avoid repeating actions. They remain on the device unless a specific feature sends them elsewhere or the operating system backs them up.

Daily leaderboard (Supabase)

If leaderboard service is configured and available, the game signs you in anonymously with Supabase Auth. It creates a profile with a generated or chosen nickname. For a daily score it sends the UTC day, score, number of broken items, best chain, round duration, client version and nickname. Supabase stores an account identifier, profile nickname and score rows; request-limiting records are also kept. The leaderboard is readable by game users. Your nickname and score appear in public leaderboard results.

The game queues a daily score locally while offline and may submit it on a later launch. The queue is removed when the server gives a final answer. A profile can be deleted in Settings → Privacy → Delete profile; see Delete your account and data.

Ads and consent (Google AdMob and UMP)

Native app builds can request rewarded and interstitial ads through Google AdMob. Ads are only requested after the consent flow permits them. Google’s User Messaging Platform (UMP) presents a consent form where required; the game exposes Privacy choices in Settings when Google reports that the choice is required. iOS also asks for tracking permission through Apple’s system prompt. Browser builds do not show AdMob ads; their rewarded-ad flow is a short in-game stand-in.

AdMob and the mobile operating system may process advertising identifiers, device and app information, approximate location or network information, and ad interaction data to provide, measure and prevent abuse of ads. The exact fields depend on the platform, consent, region, SDK and Google configuration; Google’s Android SDK data disclosure lists IP address, product interactions, diagnostics, and device or account identifiers, including advertising and app-set IDs, used for advertising, analytics and fraud prevention. On Android, use Settings → Privacy → Ads to reset or delete the advertising ID and limit personalization. On iPhone or iPad, review or change Lapa’s tracking permission in Settings → Privacy & Security → Tracking. Menus can vary by operating-system version. Google’s advertising information is linked below. Changing the device ID does not remove other device or account data.

Legal basis: where consent is required, consent (GDPR Article 6(1)(a)); for fraud prevention and operating the service, our legitimate interests (Article 6(1)(f)).

Play Games cloud save and purchases

On Android, if Google Play Games is available and signed in, the game can read and write a cloud snapshot containing game progress such as coins, owned and worn cosmetics, campaign stars and scores, records, tutorial completion, daily wheel state and nickname-related data. Google Play Games processes account and saved-game data under Google’s terms and privacy policy. This is separate from Supabase. The game’s current delete-profile action does not remove this saved game; see the deletion page.

On Android, purchases such as coin packs and the one-time Remove ads entitlement are handled through Google Play Billing. The app receives purchase information needed to grant or restore the product and stores entitlements locally, together with a record of delivered coin packs so a pack is never paid twice. Payment details are handled by Google Play; the game never receives your payment card details.

Local notifications, diagnostics and other services

Optional reminders are scheduled locally on your device; the game does not send their content to a notification server. Lapa uses no product analytics or crash-reporting services. On Android the app may read the current time from our leaderboard server or google.com, so changing the phone’s clock does not change the day, and may read the oldest supported app version from Supabase. No personal information is sent with these requests.

Purposes, legal bases and recipients

Run and save the game locally: providing the game you use (Article 6(1)(b)) and our legitimate interest in providing the requested feature (Article 6(1)(f)).
Create and display the optional daily leaderboard: the feature you choose to use and our legitimate interest in running a fair leaderboard (Article 6(1)(b) and (f)).
Show ads: your consent where it is required (Article 6(1)(a)); elsewhere our legitimate interest in funding a free game (Article 6(1)(f)).
Complete purchases and restore entitlements: steps necessary to provide a purchase you initiate; Google Play acts as the store and processes payment.
Schedule reminders: local device function controlled by your notification settings; no reminder schedule is sent to a game server.
Recipients verified in the code include Supabase for the optional leaderboard and configuration, Google for AdMob, UMP, Play Games, Play Billing and Android time requests, and Apple for iOS tracking permission and operating-system functions.

Retention and international transfers

Local data stays on your device until you clear the app’s data or uninstall it; operating-system backups follow your device settings. The leaderboard profile and scores are kept as long as your anonymous profile exists and are deleted when you delete the profile in Settings or ask us by email. Request logs used against abuse hold only the last minute of requests. Data held by Google and Apple is kept under their own terms.

Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, withdraw consent, and receive portable data. You may also complain to your local data protection authority. Write to lapadevs885@gmail.com; we may need to verify your request. You can delete the leaderboard profile from within the app; the Play Games cloud save is deleted in Google Play Games.

Children

Store ratings and feedback

If you choose Write to us in the game, it opens your email app with a prefilled message that includes the app version and a device model and operating-system string derived from your device. The email is sent only if you choose to send it. The game can request an in-app review from Google Play or Apple and stores review-prompt history locally; on Android that history may also be part of the Play Games cloud save. The game does not receive the text of a store review.

Lapa is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has submitted information to the leaderboard, contact us and we will delete it.

Contact and changes

For privacy questions or to exercise a right, write to lapadevs885@gmail.com. If this policy changes, we will update this page and its date; significant changes will also be mentioned in the game or its store listing.