Google API Services Disclosure

Limited use

Ovaideu accesses Google user data only to provide or improve user-facing Ovaideu features the user connects and uses, including account selection, campaign setup, reporting, diagnostics, conversion readiness, booking calendar sync, and authorized operations.

We do not sell Google user data, do not use it for Ovaideu's own advertising, do not use it for unrelated profiling, and do not transfer it except as needed to provide the connected feature, follow user instructions, operate trusted infrastructure, maintain security, or comply with law.

Submitted and optional Google scopes

Identity scopes openid, email, and profile identify the Google account that authorized a connection and display the connected email in the workspace.

Google Ads adwords is used for account selection, campaign, ad group, ad, keyword, asset, budget, recommendation, change history, conversion, and reporting workflows. Google Ads API does not provide narrower OAuth scopes for separate read and write campaign operations.

GA4 analytics.readonly and analytics.edit are used for property reporting, event/key-event readiness, audiences, custom definitions, and Admin API configuration workflows where the connected Google account has authority.

Merchant Center content is used for account and product readiness, Shopping, Performance Max, feed diagnostics, and ecommerce reporting.

Search Console webmasters is used for verified site selection, query/page/device/country reporting, sitemap and indexing readiness, and SEO diagnostics.

Tag Manager tagmanager.readonly, tagmanager.edit.containers, tagmanager.edit.containerversions, and tagmanager.publish are used for container inventory, tag/trigger/variable/version review, and authorized container/version/publish workflows.

Business Profile business.manage is used for connected location readiness, profile details, posts, reviews, media, and performance where the user's Google role allows it.

Calendar calendar.freebusy and calendar.events are requested only when the workspace enables booking calendar sync. They are used to check availability and create, update, or cancel Ovaideu booking events and Google Meet links.

How Google data is stored and protected

Google OAuth tokens and connected-resource metadata are stored only for the connected workspace and are protected with encrypted transport, server-side workspace boundaries, role permissions, masked credentials, audit logs, and revocation paths.

Google data may be cached or stored so dashboards, reports, diagnostics, audit history, booking records, conversion-readiness checks, support, and MCP/API tools can work reliably. One workspace cannot view or act on another workspace's Google resources.

AI and machine-learning training

Ovaideu does not use Google user data, Google Workspace data, Google Ads data, GA4 data, Search Console data, Tag Manager data, Business Profile data, Merchant Center data, or Calendar data to train, fine-tune, or develop generalized AI or machine-learning models.

When AI features are used, Google data is processed only to generate the user-facing answer, recommendation, report, diagnostic, or workflow the user requested for that workspace. Third-party AI providers are not permitted to use Google user data from Ovaideu to train their generalized models.

Human access

Humans do not read Google user data unless access is needed for user-requested support, security investigation, abuse prevention, legal compliance, or operating the service described here. Operator access is least-privilege and audit logged.

Revocation, deletion, and retention

Users can disconnect Google integrations in Ovaideu or revoke Ovaideu access from their Google Account. After revocation, Ovaideu stops future API access for that authorization.

Users can request export, correction, or deletion through support@ovaideu.com. Some audit, billing, security, abuse-prevention, legal, dispute, and backup records may be retained only where necessary and permitted.