Directory Market Research
Legal

Privacy Policy

How Directory Market Research accesses, uses, stores, and protects data.

Effective date: October 2, 2026

1. Overview

Directory Market Research (“the application”) is a desktop command-line tool operated by Kenzie Campbell. It helps authorized users research directory-site niches by retrieving keyword ideas and historical keyword metrics through the Google Ads API.

The application runs locally on the user's computer. It is not a hosted service, and there is no application-operated backend server that receives Google user data.

2. Information the application accesses

When a user authorizes the application with Google OAuth, the application may process:

  • an OAuth access token and refresh token needed to authenticate Google Ads API requests;
  • the Google Ads customer ID and, when applicable, manager account ID configured by the user;
  • keyword seed phrases entered by the user;
  • keyword ideas returned by Google Ads;
  • available average monthly searches, competition, competition index, top-of-page bid ranges, and monthly historical search volumes; and
  • technical API error information needed to explain failed requests.

The application requests the Google Ads API scope (https://www.googleapis.com/auth/adwords). Although Google defines this scope broadly, this application uses it only to request keyword ideas and associated historical metrics. It does not create, modify, or delete campaigns, ads, billing information, or other Google Ads resources.

3. How information is used

Google user data is used only to:

  • authenticate requests initiated by the authorized user;
  • retrieve keyword research data from KeywordPlanIdeaService;
  • save and deduplicate research results in the user's local SQLite database;
  • calculate niche summaries and comparisons; and
  • create CSV exports requested by the user.

The application does not use Google user data for advertising, user profiling, credit decisions, or sale to third parties.

4. Storage and retention

OAuth credentials are stored in a local .env file on the user's device. Research results are stored in data/research.sqlite3, and requested exports are stored in the local exports directory. These files are not uploaded to an application-operated server.

Data remains on the user's device until the user deletes it. Users control retention and can remove individual exports, the SQLite database, OAuth credentials, or the entire application directory at any time.

5. Sharing and disclosure

The application sends OAuth credentials, the configured Ads customer ID, keyword seeds, and required request parameters directly to Google only as necessary to use the Google Ads API. Google processes that information under the applicable Google terms and privacy policy.

The application does not sell, rent, or transfer Google user data to data brokers, advertising networks, or other third parties. Data may be disclosed only if required by applicable law or necessary to protect against fraud, abuse, or security threats.

6. Google API Services User Data Policy

Directory Market Research's use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Security

The application is designed to keep credentials and research data local. Its Git configuration excludes the .env file, SQLite database files, and CSV exports from version control. Users are responsible for securing their device, keeping local files out of shared repositories and backups where appropriate, and protecting access to their Google account.

No method of electronic storage is completely secure. If a user believes a token has been exposed, they should revoke the application's Google Account access and remove the token from their local environment.

8. Revoking access and deleting data

A user can revoke the application's access at any time from the Google Account third-party connections page. Revocation prevents the stored refresh token from obtaining new access tokens.

To delete locally stored application data, remove the relevant files:

  • .env for OAuth and API credentials;
  • data/research.sqlite3 for research records; and
  • files under exports/ for CSV exports.

Because the application does not operate a data server or user account system, no separate server-side deletion request is required.

9. Cookies, analytics, and children

This informational website does not intentionally set cookies and does not include advertising or analytics scripts. The application is a professional research tool and is not directed to children under 13.

10. Changes to this policy

This policy may be updated when the application's data practices or legal obligations change. The effective date at the top of this page will be updated when material changes are made.

11. Contact

Questions or concerns about this privacy policy or the application's handling of Google user data can be sent to:

Kenzie Campbell
kenzie@route19.com