Privacy

Effective 16 October 2026. This policy describes how Ads Hub accesses, uses, stores, and shares data, including Google user data obtained through Google APIs.

Ads Hub is operated by Pranav Anam personally, not by an employer or another company. The public site is https://adshub.pranavanam.com. Contact pranavanam@gmail.com.

What Ads Hub is

Ads Hub is a governed MCP connector for Google Ads and Meta Ads. A person uses it to read and change ad accounts they administer: list accounts, read performance, conversions, and search terms, create paused search campaigns, add negative keywords, pause campaigns and ad groups, and request spend-increasing changes that another person must approve.

The current deployment does not call Google or Meta. The practices below are the rules for data once a Google Ads account is connected, and they are the rules the application follows if that connection is enabled.

Google API Services User Data Policy

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

Use of Google user data is limited to the practices disclosed in this policy. If that use changes, Ads Hub will update this policy and ask for consent again before using the data in the new way.

The adwords scope

The only Google OAuth scope Ads Hub requests is https://www.googleapis.com/auth/adwords. It is the Google Ads API scope. With it, and only after you connect an account, Ads Hub can access Google Ads data for the accounts you select, including:

Account identifiers and names needed to show which account is connected.
Campaign, ad group, keyword, and negative-keyword settings needed to create paused campaigns, add negatives, and pause entities.
Performance, conversion, and search-term reports needed to show results for a date range you request.
Budget and bid settings needed to apply a decrease you request, or an increase after a different person approves it.

Ads Hub does not request scopes for Gmail, Google Drive, Calendar, YouTube, or contacts. It does not request a developer token. Google retired developer tokens on 9 September 2026. Authorization is a Cloud-project OAuth client with the adwords scope.

Limited Use

Data obtained through the adwords scope, and data aggregated, anonymized, or derived from it, is Limited Use data. Ads Hub applies the Limited Use requirements as follows.

Ads Hub uses that data only to provide or improve the connector features that are prominent in the product: showing the connected account, reporting on it, and applying the governed changes you or an approver in your tenant requested.
Ads Hub does not transfer that data, except to provide those features with your consent, for security (for example investigating abuse), to comply with law, or as part of a merger, acquisition, or sale of assets after your explicit prior consent.
Humans do not read that data unless you affirmatively agree to a specific review, it is necessary for security, it is necessary to comply with law, or the data is aggregated and used for internal operations in line with applicable privacy law.
Ads Hub does not sell Google user data. Ads Hub does not transfer or sell it to advertising platforms, data brokers, or information resellers. Ads Hub does not use it to serve ads, including retargeting, personalized advertising, or interest-based advertising. Ads Hub does not use it to determine credit-worthiness or for lending.

Managing the Google Ads account you connected is the feature you asked for. It is not a transfer of your Google user data into someone else's advertising audience.

What is stored

After a connection exists, Ads Hub stores:

The Google Ads customer id and display name you connected, tied to your tenant.
OAuth access tokens and refresh tokens, encrypted with AES-256-GCM envelope encryption. The plaintext is not written to logs, audit records, or API responses. The application redacts token-shaped values before they reach logs or error reports.
A local record of campaigns, ad groups, and negatives Ads Hub created or changed, so the spend cap can be enforced without trusting the caller.
An append-only audit row for each action: who acted, which tenant, what changed, a request id, and the time. Audit rows are rejected if they contain token or secret fields.

Mock performance figures in this build are generated inside Ads Hub. They are not Google user data and they are not your account's spend.

Retention

OAuth tokens are kept only while that Google Ads account remains connected to the tenant. A refresh token is kept until you disconnect the account, revoke Ads Hub in your Google Account, or ask for deletion. Access tokens are short-lived and are replaced or discarded when they expire.

Account identifiers and the campaign ledger are kept for as long as the tenant uses Ads Hub, because the cap and the audit trail depend on them. Report data retrieved from Google, once live reads exist, is kept only as long as needed to answer the request and to record the action in the audit log. The audit log itself is kept as an operational record. It does not contain Google credentials.

Deletion

Email pranavanam@gmail.com to delete a connection. Use the Google account you connected, or the email on the tenant, and name the Ads Hub tenant or Google Ads customer id. Pranav Anam will delete the stored Google user data for that connection, including OAuth tokens and Google Ads data held for that account, within 30 days, and will confirm by email.

You can revoke Ads Hub at Google Account permissions at any time. Revocation stops future access. It does not by itself identify which Ads Hub tenant holds a copy, so deletion of stored data still goes through the email above.

A deleted connection is not restored from a backup in order to resume access. Host backups, where the database provider keeps them, expire on that provider's schedule and are not used as a live copy.

Sharing and processors

Ads Hub does not share Google user data with other tenants. Application logs and error reports are scrubbed of tokens. The application runs on Vercel. The database is Postgres, on Supabase or Neon when one of those is configured. Those providers host the service so the connector can run. They are not allowed to use Google user data for their own advertising. No other third party receives Google user data.

Meta Ads

Ads Hub is also intended to connect Meta ad accounts under the same tenant, role, approval, and audit rules. This build does not call Meta and does not collect Meta user data. Before a Meta connection is offered, this policy will describe the Meta data involved.

Security

Google user data is encrypted in transit and, for tokens, at rest. Tokens are bound to the tenant, account, and token row that stored them. Ads Hub is not directed at children, and it does not knowingly collect data from children under 13.

Changes

Material changes to this policy will be posted on this page with a new effective date. Continued use of a Google connection after a change that broadens use of Google user data will require consent to the updated policy first.

Contact

Pranav Anam, pranavanam@gmail.com.