AppWatcher

Privacy Policy

Effective 26 October 2026

This policy explains what information PlayScope, AppWatcher's Google Play research tool at appwatcher.net, collects, how it is used, and the choices you have. PlayScope is currently used only by the AppWatcher team.

1. Public Google Play data

PlayScope reads public Google Play pages: app names, descriptions, icons, screenshots, install ranges, ratings, review counts, prices, release and update dates, developer names and their public contact details, chart positions and search results. It also keeps a small sample of recent public reviews (review text, rating and date) without reviewer names or photos. This information is already public on Google Play and is used to track apps and markets over time.

2. Google user data (Google Ads API)

PlayScope connects to the Google Ads API with Google sign-in (OAuth) using the scope https://www.googleapis.com/auth/adwords, and only for AppWatcher's own Google Ads account.

Data accessed

Through this access PlayScope reads keyword planning data only: average monthly Google search volumes, monthly search trends, advertiser competition and typical cost per click for the keywords we research. It does not read campaigns, ads, billing details, contacts, emails or any other information in the Google account.

How we use it

The keyword figures are shown in PlayScope's keyword research pages so our team can see how often a term is searched. We do not create, change or remove campaigns, ads, budgets, billing or users in any Google Ads account.

Sharing

We do not sell, rent, transfer or share Google user data with anyone. We do not use it for advertising, and we do not use it to develop, improve or train AI or machine-learning models.

Storage and protection

We store the keyword figures Google returns, with the keyword, country and date, in PlayScope's database on our server. The sign-in credential (a refresh token) is kept in a settings file on the server that only the server administrator can read; it is never placed in source code or backups. The server is reached only through encrypted connections (HTTPS), and the site is protected by team sign-in with one-time codes and Cloudflare Access.

Retention and deletion

Keyword figures are kept as part of our keyword history. The refresh token is kept only while PlayScope uses the Google Ads API and is deleted from the server when we stop. You can revoke access at any time at myaccount.google.com/permissions, and you can ask us to delete any stored data by emailing [email protected]; we will delete it within 30 days.

PlayScope's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

3. Team accounts

Team members sign in with a username, a password (stored only as a secure hash) and a one-time code from an authenticator app. Access to the site is also protected by Cloudflare Access, which checks the team member's email address. We keep a log of sign-ins and important actions (such as exports) for security. The site uses one sign-in cookie, needed to keep you signed in; it uses no advertising or tracking cookies.

4. Where data is stored and who can see it

Data is stored on a server in Germany (Hetzner) and in encrypted backups (Backblaze B2). Traffic passes through Cloudflare. Alert emails are sent through Gmail. These providers process data only to run the service. Only the AppWatcher team can see the data in PlayScope.

5. How long we keep data

Daily app records are kept as a long-term history of the market. Keyword search volumes are kept with the date they were collected. Team accounts and their logs are kept while the account is active. You can ask us to delete information about you at any time (see Contact).

6. Your choices

7. Children

PlayScope is a business tool and is not directed at children under 16.

8. Changes

If this policy changes, we will update this page and its effective date.

9. Contact

AppWatcher, appwatcher.net. Email: [email protected]