SEO Keyword Collector Privacy Policy

1. About the app

SEO Keyword Collector is a personal, non-commercial desktop application built by an independent developer. Its only purpose is SEO keyword research: it retrieves historical search volume for keywords that the user enters, for a selected country, region, city and language, and saves the results as reports on the user's computer.

The app runs on the user's own computer. There is no SEO Keyword Collector server, online account or cloud storage. The app is not a Google product and is not affiliated with or endorsed by Google LLC.

2. Google user data the app accesses

The app accesses Google user data only after the user signs in with Google and gives consent on the Google OAuth consent screen. The app requests one OAuth scope:

https://www.googleapis.com/auth/adwords — Google Ads API. This is the only OAuth scope that the Google Ads API offers, and it is required to use the Keyword Planner service.

With this permission, the app accesses only the following data:

The app does not request any other Google scopes. It does not access Gmail, Google Drive, Google Contacts, Google Calendar, Google Analytics, Search Console or YouTube data. It does not read your name, email address or profile photo. It does not read or change your campaigns, ads, keywords in campaigns, budgets, billing or payment information.

The user also provides the app with keyword lists, project names, locations and languages. This information is entered by the user and is used only to build the Keyword Planner requests described below.

3. How the app uses Google user data

The app uses Google user data only to provide its keyword research features to the user:

1. The user loads a list of keywords and selects a project, location and language.
2. The user selects one of their Google Ads accounts (customer ID).
3. The app sends a request to the Google Ads API Keyword Planner service and receives historical keyword metrics.
4. The app shows the metrics to the user, saves them on the user's computer and can export them to a CSV file.

The app only sends read requests: it lists the accessible Google Ads accounts and requests keyword historical metrics. It never creates, edits, pauses or deletes campaigns, ads, keywords, budgets or any other settings, and it never spends money on the user's behalf.

The app does not use Google user data:

• for advertising, ad targeting, retargeting or marketing messages;
• to build user profiles, or to determine credit-worthiness or for lending purposes;
• to develop, improve or train artificial intelligence or machine-learning models, including generalized AI models;
• to generate, edit or distribute images, video or audio, including AI-generated non-consensual intimate imagery (AI NCII);
• for any purpose other than the keyword research features described in this policy.

4. Google API Services User Data Policy and Limited Use

SEO Keyword Collector's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The app also complies with the Google APIs Terms of Service and the Google Ads API Terms and Conditions.

5. How the app stores and protects data

All data is stored only on the user's own computer:

• keyword lists, Google Ads customer IDs and keyword metrics are saved in a local database file and in CSV files that the user exports;
• the OAuth refresh token is saved in a local configuration file on the user's computer.

No data is uploaded to any SEO Keyword Collector server, because the app has no server. The developer does not receive or keep copies of any user's Google user data.

All communication between the app and Google uses encrypted HTTPS (TLS) connections. Local files are protected by the user's operating system account. OAuth tokens are never shown on this website, never published, and never sent to anyone except Google.

6. How the app shares data

The app does not sell, rent, share or transfer Google user data to any third party, including advertising networks, data brokers or AI companies.

The only data that leaves the user's computer is the content of the API requests that the app sends to Google: the selected Google Ads customer ID, the keywords, the location and the language. This data is sent directly to Google over HTTPS so that Google can return the keyword statistics.

CSV reports exported by the user stay under the user's control. If the user decides to share a report with someone, that is the user's own choice.

7. Data retention and deletion

Data is kept on the user's computer until the user deletes it. The developer keeps no copies, so there is no data to delete on any server.

To delete data:

• delete a project in the app, or delete the local database file and CSV reports from the computer;
• delete the local configuration file that contains the OAuth token;
• revoke the app's access to your Google account at any time at myaccount.google.com/connections (Google Account → Security → Third-party apps & services). After access is revoked, the app can no longer access any Google Ads data.

If you need help deleting data, contact the developer as described in section 10.

8. This website

This website only provides information about the app. It has no sign-in, no forms, no cookies, no analytics and no tracking scripts, and it never asks for Google credentials. The website is hosted on GitHub Pages. GitHub may record technical information such as IP addresses in server logs for security purposes, as described in the GitHub General Privacy Statement.

9. Changes to this policy

If the way the app accesses, uses, stores or shares Google user data changes, this page will be updated before the change takes effect, and the “Last updated” date above will change. If a change requires new permissions, the app will ask for the user's consent again through the Google OAuth consent screen.

10. Contact

For questions about this Privacy Policy or requests about your data, use the developer support email shown on the SEO Keyword Collector Google OAuth consent screen, or open a request on the project's GitHub Issues page. GitHub Issues are public, so never post passwords, tokens or other private information there.