Google API disclosure
Which Google APIs {{brand}} uses, what data they return, how it is stored, and the Limited Use commitments we are bound by.
Last updated: 17 September 2026 · Effective: 17 September 2026
Which Google APIs we use
vedhasAI uses two Google services, and only when you choose to use them.
Sign in with Google. If you sign in with your Google account, Google sends us your name, email address, profile picture and Google account ID. We use them to create your vedhasAI account or match you to an existing one, and to keep sign-in secure. Nothing else is read from your Google account.
Google Ads API — early access. If you connect a Google Ads account, we read reporting data so the app can show what each campaign cost beside the leads and sales already in your CRM. Specifically:
- Google Ads customer (account) ID and name
- Campaign, ad group, ad and keyword names, IDs and statuses
- Daily metrics: cost, impressions, clicks, conversions and conversion value
The Google Ads API scope (https://www.googleapis.com/auth/adwords) is a sensitive scope, which is
why this application goes through Google's OAuth verification.
What we do not do
We do not create, edit or pause campaigns. We do not change budgets or bids. We do not read anything outside the scopes you grant. We do not write anything back to your Google Ads account today. If we ever add offline conversion upload, it will be off by default and will only run after you switch it on for your own account.
Limited Use
vedhasAI'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.
What those requirements mean here:
- Google user data is used only to provide or improve user-facing features that are prominent in vedhasAI: ads reporting, cost per lead and cost per sale, campaign comparison, and — if you turn it on in future — conversion sync.
- It is transferred to others only when necessary to provide those features (the sub-processors named in our Privacy Policy), to comply with law, or as part of a merger or acquisition, with notice to you.
- It is not used or transferred for serving advertisements, including retargeting, personalised or interest-based advertising.
- Humans do not read it, unless you give affirmative consent for specific data (for example when you attach it to a support ticket), it is necessary for security or abuse investigation, or the law requires it.
- It is not sold, not used to determine creditworthiness or for lending, and not used to build or train generalised AI or machine-learning models. Where an AI feature produces insights from your ads data, that processing exists only to produce that output for you.
Storage, security and access
OAuth tokens are encrypted at rest. Synced campaign names and metrics are stored in your workspace's own database, separate from other businesses. All traffic uses HTTPS/TLS. Access is limited to staff who need it to run or support the service, and every access is logged.
Retention
Tokens are deleted immediately when you disconnect. Synced Google Ads data is deleted within 30 days of disconnecting, or sooner if you ask.
How to revoke access and delete data
- In vedhasAI: Settings → Integrations → Google Ads → Disconnect.
- In your Google account: myaccount.google.com/permissions → find vedhasAI → Remove access.
- To delete data we already synced, follow How to delete your data or email privacy@vedhasai.com.
Step-by-step screens are in the help article on connecting Google Ads.
Contact
Questions about this disclosure: privacy@vedhasai.com. Security reports: security@vedhasai.com. Grievance Officer: TODO_NAME, grievance@vedhasai.com.