Keyword Expansion Tool
Data and privacy

Privacy policy

Last updated: October 8, 2026

This policy applies to Keyword Expansion Tool at ads.au88.fyi, an independently operated keyword research project. Contact the operator at lindsaystamperi477@gmail.com.

Current status: this is an informational website. The Google Ads API integration is being configured. This website currently has no Google sign-in, keyword submission form or API-backed research feature. The integration practices below are requirements for that planned functionality, not a claim that account data is already being collected.

1. Information handled by this website

These public pages do not set application cookies, use browser storage, run analytics scripts or collect form submissions. The hosting and network providers may process normal connection information, such as IP address, requested URL, browser information and timestamps, to deliver and secure the site.

If you contact the operator by email, your email address, message and information you choose to include are used to respond to your request. Do not send passwords, access tokens or payment details by email.

2. Planned Google account connection

When the integration becomes available, an authorized user will be asked to connect their Google Ads account through Google OAuth before account access occurs. The tool will not ask for or store your Google password.

The Google Ads authorization scope can permit broader account management than keyword research. The planned tool will use access only for account identification and keyword planning requests. It will not create ads, change campaigns or bids, or alter billing.

3. Planned information accessed and its purpose

The planned integration does not need access to Gmail messages, Drive files, contacts or unrelated Google account data.

4. Use and sharing

Research inputs and the required account identifiers will be sent to Google to fulfill the user’s keyword planning request. Results will be provided to the authorized operator and included in exports the operator chooses to create.

Google user data will not be sold, used for targeted advertising, transferred to data brokers or used to train general-purpose AI models. Access will be limited to the authorized operator and service providers strictly necessary to operate, secure or troubleshoot the requested functionality, or where disclosure is legally required.

Keyword Expansion Tool’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 where applicable.

5. Storage, security and retention

Before account access is enabled, authorization credentials must be stored in a protected credential store outside the public website and source repository. Credentials must not be embedded in pages, exported research or diagnostic logs. Google API requests must use HTTPS.

The planned research workflow will store selected results and exports in the operator’s controlled workspace until the operator deletes them. Connection credentials will be retained only while the connection is needed. Operator-controlled credentials, cached account data and support correspondence will be deleted within 30 days of a valid deletion request, except where retention is required by law. Copies already exported to a user-controlled location must be deleted by that user.

Hosting or email providers may separately retain service and security records under their own policies. This site does not set their retention periods.

6. Your choices

You can request information about the data held by the operator, correction, disconnection or deletion by emailing lindsaystamperi477@gmail.com. The operator may need to confirm your authority over the relevant account before handling a request.

Once a Google connection exists, you can also revoke it in your Google Account connections settings. Revocation prevents further authorized access; it does not automatically delete exports already created.

7. Changes to this policy

This page will be updated when the integration becomes available or its data handling changes. The tool must request any necessary additional consent before accessing data for a new purpose. The date at the top identifies the latest revision.