Privacy Policy

In short: our games can be played without an account. Game progress is stored on your device. We use Google services for advertising, consent, analytics, crash reporting, remote configuration, and in-app purchases. Those services may collect device, usage, advertising, and diagnostic data as described below. Some games offer an optional one-time purchase to remove ads; Google Play handles the payment.

This Privacy Policy explains how Omri Bar-Oz ("we," "us," or "our") handles information in mobile games that link to this policy. It currently applies to Crazy Blocks, Crazy Steps, and Crazy Sort and will apply to future games only when their store listing or in-game privacy screen links here. If a game uses materially different data practices, we will update this policy or provide a game-specific notice.

1. Who is responsible

Omri Bar-Oz is the developer and data controller for the games covered by this policy. For privacy questions or requests, contact omribaroz60@gmail.com.

2. Information stored on your device

Our games may store progress, high scores, settings, tutorial state, daily-challenge state, ad frequency information, reward state, purchase ownership, and consent-related state locally on your device. We do not receive this local game data unless a specific item is included in an analytics or crash event described below. Local data remains until you clear the app's storage or uninstall the app, subject to any backup or restore feature provided by your device or app store.

Our games do not currently offer user accounts, cloud saves, chat, or collection of names, email addresses, contacts, photos, precise location, or user-created content.

Purchases. Crazy Steps and Crazy Sort offer an optional one-time Remove Ads purchase through Google Play. Google Play processes the payment under its own terms; we never receive your payment card or billing details. The game learns from Google Play whether you own the purchase, keeps that answer on your device so ads stay off while offline, and can restore it on a new install through Google Play. Crazy Blocks does not offer purchases.

3. Information collected by Google services

Depending on your region, consent choices, device settings, and the game version, we use the following services provided by Google LLC and its affiliates:

• Google Mobile Ads (AdMob) and User Messaging Platform (UMP): to request and display rewarded, interstitial, and banner ads; manage privacy choices; measure ads; limit invalid activity; and prevent fraud. The SDK may collect or share IP address (which can indicate general location), app launches, taps, ad and video interactions, SDK and app performance diagnostics, Android advertising ID, app set ID, and other device or account identifiers where available. UMP stores and communicates consent choices. Ads may be personalized where you consent and applicable law permits; otherwise Google may show non-personalized or limited ads.
• Google Play Billing: to sell, confirm, and restore the optional Remove Ads purchase. Google Play receives the purchase and your Google account's billing information; the game receives only the product and whether it is owned, pending, or refunded.
• Google Analytics for Firebase: to understand game use and improve balance, reliability, and presentation. This can include pseudonymous app-instance or installation identifiers; device and app information; general location derived from IP address; session and engagement information; and game events such as starting a game, placing pieces or sorting items, clearing lines or levels, score, run duration, choosing an upgrade, using a booster, ad outcomes, whether a purchase was started and its result (never payment details), settings changes, and daily-challenge outcomes. We do not intentionally send raw board layouts, exact touch coordinates, free-form text, or your name or email address.
• Firebase Crashlytics: to find and fix crashes, application-not-responding events, and nonfatal errors. Reports may include stack traces, relevant app state and logs, app version, device model, operating system, memory and storage information, timestamps, installation and session identifiers, and limited developer-defined categories such as the current screen or error category. Analytics events immediately before a crash may be included as breadcrumbs. We do not set a name, email address, or other direct user ID in Crashlytics.
• Firebase Remote Config: to safely select game configuration, such as daily-challenge content, without requiring an app update. It may collect country and language codes, time zone, platform and OS version, app and package identifiers, SDK version, Firebase installation identifier, first-open time, and relevant Analytics properties. Remote Config does not make gameplay dependent on an online connection; baked-in defaults remain available offline.

4. How we use information

We use information to operate and improve the games, provide and measure ads, apply consent choices, understand aggregate gameplay and feature use, diagnose crashes and errors, prevent fraud and abuse, maintain security, and comply with legal obligations. Where applicable, our legal bases include your consent, our legitimate interests in operating and improving the games, performance of the service you request, and compliance with law. You can play the core offline game even when optional analytics or personalized advertising is unavailable.

5. When information is shared

Information is transmitted to Google as our analytics, crash-reporting, remote-configuration, consent, advertising, and in-app purchase provider. For advertising, Google may share information with or allow processing by ad technology providers identified in the consent message shown in the game. These providers process information under their own terms and privacy policies. We may also disclose information when required by law, to protect users or our rights, or in connection with a business transfer.

We do not sell personal information for money. Personalized advertising and the disclosure of identifiers to advertising providers may be considered a "sale," "sharing," or targeted advertising under some privacy laws. Where required, you can opt out through the in-game Settings → Privacy choices control and through Android's advertising privacy controls.

6. Your choices and rights

• Open the game's Settings screen to review or change available privacy choices and to reopen Google's consent form.
• Use Android settings to reset or delete your advertising ID and manage ad privacy choices.
• Clear the game's storage or uninstall it to remove locally stored game data from the device, subject to device backups.
• Contact us to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent where your law provides those rights. We may need enough information to identify the relevant app installation or provider record, and some pseudonymous records may not be reasonably linkable to you.

Withdrawing consent does not affect processing that was lawful before withdrawal. You may also have the right to complain to your local data-protection authority.

7. Retention and deletion

Local game data remains as described in Section 2. We retain Analytics event-level data for no longer than 14 months under our configured retention settings; aggregated, de-identified reports may remain longer. Firebase Crashlytics generally retains crash reports and associated installation identifiers for 90 days before removal begins. Advertising and consent records are retained by Google under its applicable terms, settings, and legal obligations. We may retain limited information longer when reasonably necessary for security, fraud prevention, legal compliance, or to establish or defend legal claims.

We review the data we control and delete or de-identify it when it is no longer needed for the purposes above. For a deletion request, email us with the game name and any information you can safely provide to help locate the record. Do not send sensitive personal information.

8. Security and international processing

We minimize the information our games send, restrict telemetry to defined fields, use provider access controls, and rely on encrypted HTTPS/TLS transmission supported by Google SDKs. No system is completely secure. Google and its subprocessors may process information in countries other than yours, subject to applicable contractual and legal transfer safeguards.

9. Children

Our games are intended for adults aged 18 and older and are not directed to children. Anyone under 18 should not use a covered game. We do not knowingly collect personal information directly from children. Store content ratings can vary by country and are separate from this intended-audience restriction. If you believe a child provided personal information through a covered game, contact us so we can investigate and take appropriate action.

10. This policy website

This page is hosted by GitHub Pages. We do not place advertising, analytics scripts, contact forms, or cookies on this page. GitHub may process technical request information such as IP address and browser details to deliver and secure the site under the GitHub General Privacy Statement.

11. Third-party information

For more detail about provider practices, see Google's Privacy Policy, How Google uses information from apps that use its services, Firebase privacy and security information, and Google Mobile Ads data disclosure.

12. Changes to this policy

We may update this policy when a game, provider, law, or data practice changes. We will post the revised policy here and update the date above. Material changes will receive additional notice in the game or store listing when required.