Google API Services — data use and compliance
This page describes, in English, how Marketing Workspace uses Google APIs (Google Ads API and Google Analytics APIs), what data we access, and the commitments we make about that data. It is intended both for our users and for Google reviewers.
About the tool
- Tool: Marketing Workspace — a multi-tenant web application available at https://marketing.roition.com.
- Developer: Roition, a Polish business-process automation agency — https://roition.com.
- Contact: kontakt@roition.com (monitored company address).
- Who uses it: both internal users (Roition employees and contractors managing marketing on behalf of clients) and external users (our clients — business owners and their marketing staff), each within their own isolated organization (tenant). A user only ever sees and manages Google accounts that were explicitly authorized within their own organization.
- What it does: users connect their own Google Ads and Google Analytics 4 accounts, receive AI-assisted performance analysis, and — for Google Ads — apply recommended optimizations that they individually review and approve in the panel. For clients whose authorized user opts in, read-only background monitoring turns sharp changes in results into alerts.
OAuth scopes we request
| Feature | Scope | Why we need it |
|---|---|---|
| Sign-in | openid, email, profile | Account creation and authentication only. Grants no access to advertising or analytics data. |
| Google Ads module | https://www.googleapis.com/auth/adwords | Reading campaign reporting data for analysis (and, only with per-client consent, read-only background monitoring), and applying only those changes that the user has explicitly approved in the panel. |
| GA4 module | analytics.readonly | Read-only reporting. The same read-only scope is used to list the user's GA4 accounts and properties during setup; we never modify GA4 configuration. |
We never ask for or store Google account passwords. Authorization uses Google OAuth 2.0; refresh tokens are encrypted at rest and scoped to the user's organization.
Scopes are requested incrementally and per module: a user who only uses the GA4 module is never asked for the Google Ads scope. When a second module is connected on the same Google account, we use incremental authorization, so the previously granted scope is preserved rather than replaced.
Sign-in, the Google Ads module and the GA4 module are served by a single OAuth client in a single Google Cloud project owned by Roition; the application refuses to start if it is configured with a client from any other project.
How we use the Google Ads API
The tool operates in four modes: analyze (read-only reporting), optimize (applying user-approved changes), create (creating a user-approved Search campaign draft) and monitor (read-only scheduled checks, only with per-client consent). The API surface is intentionally narrow: reporting reads plus a bounded set of management operations.
- User-initiated, with one consent-based exception. Every write and every analysis is triggered by an action of a signed-in user. The only scheduled activity is the read-only performance monitoring described below, and only for clients whose authorized user turned it on. There is no bulk export, background synchronization of whole accounts, or autonomous or scheduled optimization: no scheduled job can create or apply a change.
- Human-in-the-loop writes. The AI assistant proposes a change; the user sees the exact resource, field, current value and new value, and must explicitly approve each item before anything is sent to Google. Approved changes are applied, verified by reading them back, and recorded in a per-organization audit trail (who, what, when, before → after).
- Bounded changes. In existing campaigns only budgets, bids, status (pause/enable) and negative keywords can be changed. Budget and bid changes are capped per action. The tool favors pausing over deletion — the tool performs no delete/remove operations at all. Executed changes per organization are capped per day, proposals expire after 24 hours, and the live value is re-read immediately before execution (execution is withheld if it changed since the proposal). All supported changes are reversible by the account owner.
- Campaign creation (Search). On the user's request the assistant drafts a complete Search campaign (budget, bidding strategy, location and language, ad groups, keywords, responsive search ads, negative keywords). Code validates the draft against Google Ads rules and Google checks it with a validate-only request, which creates nothing. The user reviews every keyword, headline and description in the panel and approves the full draft; only then is the campaign created in one atomic
GoogleAdsService.Mutaterequest (all or nothing), enabled or paused as the user chose, read back and recorded in the audit trail. The number of campaign drafts per organization per day is capped in code. - Policy review status of created campaigns. For a campaign created through the tool, the user can click “Check Google review status” in the change log to see the approval status, review status and policy topics of its ads and assets (for Performance Max, its asset groups and asset group assets). This is a reporting read (
GoogleAdsService.Search, a few GAQL queries) performed only when the user clicks; nothing is read on a schedule and nothing is changed. Draft images are shown to the user as thumbnails before approval, so the user approves exactly the files that will be uploaded. - Background performance monitoring (opt-in per client, read-only). Off by default: in the client card a user with management rights chooses between “Monitor in the background” and “Only when I ask” (the default). Consent is recorded with timestamp and the consenting user in the client's history and can be withdrawn at any time; withdrawal stops scheduled reads for that client immediately, because the job reads the consent flag before every API call. Archiving the client, detaching the account or disconnecting the Google connection also stops monitoring. Every 4 hours the job performs one
GoogleAdsService.Searchquery per monitored account (daily totals of cost and conversions for the last 35 days:SELECT segments.date, metrics.cost_micros, metrics.conversions FROM customer). Rules evaluated in code compare the last 7 days with the previous 7 days (conversions shifted by 3 days for reporting delay) with a user-configurable threshold (default 10%) and minimum sample sizes. Results are shown as alerts in the panel and, only for users who opted in, sent by e-mail. Any follow-up change goes through the normal propose → approve flow. A global switch disables all scheduled reads. - Manager accounts. Accounts can be connected directly or through a manager account; only enabled, non-manager accounts are offered as selectable targets.
- Volume. Each analysis performs a small number of targeted reporting reads and each optimization applies a small number of user-approved operations; a created campaign is typically 20-150 operations in a single request. Monitoring adds 6 reads per monitored account per day. An operations budget per organization and per day is enforced in code; scheduled jobs are deferred when it is reached, and interactive requests take priority — well within our access-level limits.
How we use Google Analytics APIs
- read-only reporting queries executed when the user asks a question or generates a report,
- listing accessible accounts and properties during setup uses the same read-only scope,
- no write operations against GA4 configuration of any kind.
- the GA4 module's server-side tagging check fetches only the client's public web page (and the public Tag Manager container script it references), like any browser; it uses no Google API and no OAuth scope.
Limited Use disclosure
In particular, data obtained through Google APIs is:
- used only to provide the user-facing features described on this page (analysis, reports, user-approved optimizations, consent-based alerts),
- shown only to the user's own authorized organization — never sold, never transferred to third parties for advertising, market research, or creditworthiness purposes,
- never used for serving advertisements or building advertising profiles,
- never used to train generalized artificial-intelligence or machine-learning models. Data is passed to our AI providers (Anthropic; Google's Gemini API for assessing the relevance of search terms against the client's offer, answering general questions and reviewing the assistant's answers; OpenAI as a backup for general answers and that review; TypeSafe receives only the question text to recognise its type) solely to generate the specific response requested by the user, limited to what that response needs, under API terms and data processing agreements that prohibit training on that data,
- not read by humans at Roition, except with the user's explicit consent (e.g. a support request), for security/abuse investigation, or where required by law.
Data handling and security
- all traffic is encrypted in transit (HTTPS/TLS),
- OAuth refresh tokens are encrypted at rest and never exposed to the frontend or written to logs,
- every request is authorized against the user's organization membership; cross-tenant access is prevented at the API layer,
- role-based access within organizations (owner, admin, specialist with per-module access),
- every applied Google Ads change is logged with before/after values and the acting user; the client's history records every monitoring consent change,
- the codebase undergoes regular automated security scanning, and the service is continuously monitored and backed up.
Retention, revocation and deletion
- Tokens: stored until the user disconnects the account in the panel or revokes access at myaccount.google.com/permissions — in both cases access ends immediately and the stored token is deleted.
- Reports and chat history: kept for the organization while the account is active; deleted upon account deletion or on request. A conversation also keeps the Google Ads data fetched to answer it (query results for that conversation only), so follow-up questions do not re-query the account; this data is removed from all conversations as soon as the Google Ads account is detached from the client, the connection is disconnected or the client is archived.
- Monitoring alerts: stored in the organization's own database and visible only to that organization; deleted when the Google Ads account is detached, the connection is disconnected or the client is archived.
- Technical logs: retained for a limited period for security purposes, then deleted.
- Deletion requests: kontakt@roition.com.
Related documents
- Privacy policy (Polish; includes the Limited Use disclosure).
- Terms of service (Polish).
- Full user documentation (Polish).
