Research privacy policy

Effective October 7, 2026

This policy covers 0xAlex Research, a private local research tool operated by Alex. The Google Ads integration is being configured. The handling practices below apply when it is enabled.

Data accessed and purpose

The tool uses Google OAuth authorization and a Google Ads customer ID to request keyword suggestions and aggregate historical metrics, such as monthly search estimates, advertising competition, and bid ranges. Requests include research keywords and selected geographic and language settings.

These results support private market research and evaluation of potential search advertising opportunities. They do not identify individual searchers. The workflow does not request Gmail messages, contacts, individual search histories, or individual advertising customer records.

Authorization and storage

Google handles sign-in; the tool does not receive or store your Google password. OAuth credentials and tokens used to access the authorized account are kept in local configuration files, outside the public website and source repository. Saved keyword responses and research notes are kept in local research files or a local database.

Although the Google Ads OAuth permission can allow account changes, this research workflow only reads data and does not create or modify advertising campaigns.

Sharing and AI analysis

Credentials, OAuth tokens, and Google account identifiers are not published or supplied to AI models. Google receives the requests necessary to provide its API service. Aggregate keyword results and research notes may be analyzed using local or third-party AI tools, with account identifiers and credentials excluded. Where third-party tools are used, their data handling terms also apply.

Google user data is not sold, used for advertising targeting, or used to train or improve general-purpose AI models. The application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

Authorization tokens are retained locally while the integration is in use. Saved aggregate research results are retained until the operator deletes them. Disconnecting the account stops future access but does not automatically erase saved results.

Access can be revoked through Google Account connections. Local credentials, tokens, and saved research data can be deleted by the operator. For questions or a deletion request, contact 0xnull.dev@gmail.com.

Public information pages

These pages do not ask visitors to connect a Google account or submit research queries. The website hosting provider may process normal request information, such as IP addresses and browser details, to serve and secure the pages.

Changes

This page will be updated if the integration's purpose or data handling changes. The effective date above will reflect those updates.