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 required by Google's Merchant API for Ovaideu's current account, product-readiness, feed-diagnostic and ecommerce-reporting reads. Google classifies this scope as read/write; Ovaideu's current Merchant Center features are read-only, and connected-account permissions further limit access.

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 when you connect or reconnect all Google services, or choose the Calendar booking or Google Meet connection. Connecting an individual Google service requests its own scopes and identity access. These Calendar permissions are used to check availability and create, update, or cancel Ovaideu booking events and Google Meet links.

Optional Data Manager permission

The optional Google Data Manager connection requests https://www.googleapis.com/auth/datamanager for supported first-party conversion and customer-data measurement operations on destinations you are individually authorized to use. It is separate from the existing Connect all Google services request; the default Google scope bundle is unchanged.

This optional permission is prepared for activation and is not represented as publicly approved or as completed conversion delivery. When the feature is enabled, its consent request will show the additional permission before authorization. Google account consent does not replace visitor consent or the current destination permissions required for an upload. Existing grants are retained through incremental authorization; this notice does not submit OAuth verification, grant new access or remove an existing scope.

Conversion and server-side measurement in development

Google Ads conversion uploads and Google Data Manager ingestion are in development; payload validation, a queued event or a request identifier is not completed delivery or attribution. When enabled, these workflows use the assigned Ads conversion destination, eligible first-party event name, time, value and currency, consent state, supported click identifiers and normalized hashed customer information needed for the requested measurement.

Provider sign-in does not supply visitor consent. Required ad-user-data and other applicable consent must be recorded before a permitted upload. GA4 server events use the configured property or stream and permitted event and session information. Additional data uses require disclosure and any required consent before activation; this notice does not add OAuth scopes or announce provider approval.

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

Human access to Google data subject to Limited Use is confined to its permitted exceptions: specific affirmative user agreement, necessary security purposes, legal compliance or permitted aggregated internal operations. General Terms acceptance is not unrestricted permission to read Google data. Operator access is limited and audit logged.

Revocation, deletion, and retention

Use the available Ovaideu disconnect workflow or revoke access in your Google Account. Check the result: a local removal or pending provider request is not confirmation that Google revoked the authorization. After confirmed revocation, that authorization no longer permits future API access.

Request export, correction or deletion through support@ovaideu.com. A record removed from Ovaideu is not automatically erased from Google, including conversion events already delivered. Supported provider deletion or suppression requires the applicable authorized workflow. Necessary audit, billing, legal or backup retention remains subject to applicable rights and provider limits.