Privacy Policy

Privacy Policy

Last updated August 31, 2026.

Project 251 (https://pro251.com) is a sole proprietorship operated by Brad Jones, based in Knoxville, Tennessee. This policy explains what information pro251.com collects, why, and how it's handled — including a specific section on data accessed through Google APIs, since Project 251 operates an internal tool that connects to Google Ads accounts under its Google Ads manager account.

Questions about this policy or your data can be sent to brad@pro251.com.

Information collected through this site

The contact form at /contact collects your name, email address, phone number, business name, industry, current website (if any), the services you're interested in, and any message you write. This is used only to respond to your inquiry — to follow up about the work you're asking about. It is not sold, and it is not shared with any third party for marketing or advertising purposes.

pro251.com does not run any analytics, advertising, or tracking scripts. No cookies are set for tracking purposes, and no visitor behavior is collected or shared with any third-party analytics or ad platform. If that changes in the future, this policy will be updated to say so before it happens.

Hosting

This site is hosted on infrastructure provided by DigitalOcean. No visitor data collected through this site is processed by DigitalOcean beyond standard web server request logs (IP address, requested URL, timestamp) used for basic operation and security.

Google user data

Project 251 operates Ringleader, an internal software tool built and used by Project 251 to manage Google Ads accounts under Project 251's Google Ads manager account. Ringleader is not a product or service offered to customers — it has a single user (Brad Jones, operating as Project 251) and is not sold, licensed, or made available to anyone outside Project 251. Because Ringleader connects to Google Ads (and, read-only, to Google Analytics and Search Console), this section explains exactly what it accesses and how that data is handled.

What is accessed

Ringleader reads Google Ads campaign performance, account structure, and keyword-planning data, and makes structural changes to campaigns, ad groups, ads, and keywords. This covers Project 251's own Google Ads account and a small number of client accounts Project 251 manages directly, all linked under Project 251's Google Ads manager account. Separately and read-only, it can read Google Analytics traffic data and Google Search Console search-performance data for properties Project 251 owns.

How access is authenticated

Google Ads access uses OAuth2 authorization granted directly by Brad Jones as the Project 251 account owner through Google's standard consent screen. That authorization produces a refresh token, which Ringleader stores and uses to obtain short-lived access tokens — the same mechanism any Google Ads API application uses, without granting Ringleader an ongoing, independent identity of its own. Google Analytics and Search Console access uses a separate mechanism: a Google Cloud service account that Project 251 has added directly to those specific properties. In both cases, this describes how Project 251 manages its own accounts — nothing about a website visitor's own Google account is ever involved in either flow.

Purpose and use

This data is used solely to manage the advertising and marketing accounts described above — to review performance, plan keywords, and make changes to campaigns, ad groups, ads, and keywords. It is not used to serve ads to anyone, it is not sold, and it is not used for any purpose beyond operating those accounts.

Storage, retention, and AI processing

Credentials — the OAuth refresh token and the service account key — are encrypted at rest and stored only in Ringleader's own private database, never in this website's codebase or database. They are never exposed to any AI model or third party. Credentials are retained only for as long as the relevant Google connection stays active; disconnecting it removes the stored credentials immediately and completely.

Ringleader itself is operated with the assistance of a third-party AI model provider (Anthropic's Claude). To read campaign performance, plan keywords, and make the structural changes described above, the account data being acted on — but never the credentials themselves — is processed by that model provider as part of performing the requested action. This is the account-management functionality the data was obtained for, and no more.

Ringleader keeps an internal audit log of structural changes it makes to Google Ads accounts (what changed, when, and why) for Project 251's own accountability. That audit log is retained indefinitely as an internal business record, is never sold, and is never shared outside Project 251.

Limited Use compliance

Ringleader's use of Google Ads, Google Analytics, and Google Search Console data complies with Google's API Services User Data Policy, including the Limited Use requirements. Data obtained through these APIs is used only to provide the account-management functionality described above, including the AI-assisted processing described in the section above, which is necessary to provide that functionality. It is not transferred to any other third party, is not used for serving advertisements, and is not sold to data brokers or anyone else.

Changes to this policy

If this policy changes, the updated version will be posted here with a new "last updated" date. Material changes to how Google user data is handled will be reflected here before they take effect.

Contact

Questions about this policy, or requests about your data, can be sent to brad@pro251.com.