YEAH! LOCAL TOOLS

Privacy policy

Effective date: October 4, 2026

This policy covers Google data used by YEAH! Local Tools, including our local keyword-research app and authorized Google Ads workflows.

Data we access and how we use it

With the signed-in user’s permission, our tools access Google Ads account identifiers, account names, account settings such as reporting currency, keyword-planning results, and advertising data needed for an authorized workflow. Advertising workflows may access campaign settings and performance reports and make changes when authorized. Local Keyword Finder reads keyword ideas and estimated search, competition, and cost metrics; it does not create or change campaigns.

We use this data for local keyword research, advertising analysis, reporting, and account management requested by an authorized user. We do not use Google user data to train generalized artificial-intelligence or machine-learning models.

Storage

Local Keyword Finder stores its renewed Google sign-in token in a private configuration file on the user’s Mac. It temporarily caches research results in memory. Saved lists, recent searches, and the selected research-account ID are stored in that browser. CSV exports are saved wherever the user chooses to download them.

Other authorized workflows may create local reports or exports in YEAH! Local’s working files. Files in folders configured for cloud synchronization may be stored by that synchronization provider. Access is limited to people and services involved in the authorized work.

Sharing and protection

We do not sell Google user data or use it for advertising profiles. Data may be shared with the account owner, an authorized client or team member, or a service provider needed for the requested workflow. We disclose information when required by applicable law. Google authentication and API requests use HTTPS. Sign-in credentials for the local keyword app are kept outside its application source folder with owner-only file permissions.

YEAH! Local Tools’ 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 your choices

Research results cached in memory are cleared when the local app server stops. Browser lists and history remain until removed or the browser’s site data is cleared. Downloaded exports remain until deleted by the user. Other workflow reports are retained while needed for the authorized work or applicable recordkeeping obligations.

You can revoke the Google connection through Google Account permissions. Revoking access stops future authenticated requests but does not erase previously saved browser data or exported files. To request removal of YEAH! Local-held data, contact justinherring@yeah-local.com. We will address the request subject to applicable legal retention requirements.

Contact and changes

YEAH! Local operates these tools. Contact justinherring@yeah-local.com with privacy questions. We will update this page and its effective date when our practices change.