Google API disclosure

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 / account connection. After you connect, we discover accessible direct or manager-linked ad accounts and read the campaigns of the account you select and test. We receive customer IDs, names, currencies and manager relationships, plus campaign IDs, names, statuses and channel types. Campaign responses are displayed on demand rather than cached by this module. Performance metrics, keyword reporting and CRM attribution are separate future reporting work.

Google requires the https://www.googleapis.com/auth/adwords scope. Google does not offer a read-only Google Ads OAuth scope; our application restricts this module to fixed read queries, with no campaign mutation endpoints.

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: account discovery and read-only campaign viewing. Future reporting features require separate implementation and disclosures.
• 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

Reporting credentials are encrypted at rest. Account metadata, consent and connection-test status are stored in shared application collections scoped to your business. HTTPS protects traffic. Access is restricted by workspace permissions. This module does not send reporting data to an AI model.

Retention and deletion

Disconnecting removes reporting credentials and stops reads. Saved account details remain until you choose Delete reporting data. That action also removes imported reporting records for this business and provider from the active service. Backup retention is described in the Privacy Policy.

1. Open Reporting / Settings / Google Ads.
2. Choose Disconnect, or Delete reporting data and type DELETE to remove saved reporting information too.
3. You can also revoke access in Google connected apps. We attempt grant revocation for OAuth disconnects; if that fails, remove access there. Manual credentials must be revoked at their source.

Independent CRM data is separate. See data deletion instructions to request its removal.

Contact

Questions about this disclosure: privacy@vedhasai.com. Security reports: security@vedhasai.com. Grievance Officer: TODO_NAME, grievance@vedhasai.com.