Privacy Policy

Only people given an account by an administrator. There is no public sign-up. If you do not have an account, the tool holds no data about you.

For each account we store only what is needed to sign you in:

• Your name, as entered by the administrator who created the account.
• Your email address, used as your sign-in identifier.
• A cryptographic hash of your password, held by Firebase Authentication. We never see or store the password itself.
• Account creation time and last sign-in time.

We do not use analytics, advertising trackers, or third-party profiling on this tool.

To protect accounts against password guessing, failed sign-in attempts are counted against your email address and against the originating IP address. These counters expire automatically after 15 minutes and are not used for any other purpose.

One cookie is set: a session cookie that keeps you signed in. It ishttpOnly(unreadable by page scripts), restricted to this site, and expires after 14 days. There are no advertising or analytics cookies.

The sign-in form is protected by Google reCAPTCHA v2, which collects device and interaction signals to distinguish people from automated scripts. That processing is governed by Google's Privacy Policy and Terms of Service. It is used solely to protect the sign-in form.

The tool collects publicly available information about mobile games from the Apple App Store and Google Play — chart rankings, store listings, ratings counts, prices and release dates — plus publicly listed advertising creatives from the Meta Ad Library. This is information about published apps and companies, not about individual people.

Accounts are held in Firebase Authentication and market data in Google BigQuery, both within the Davanci Google Cloud project. Access is limited to the team.

Account data is kept until the account is deleted by an administrator, at which point it is removed from Firebase Authentication and access ends immediately. To have your account removed, ask an administrator.

For any question about this policy or your account, contact the team administrator who issued your credentials.