Requested Google access
MarketingOS may request read-only access to Google Search Console. The first verification scope is intentionally narrow: no Google Analytics, Gmail, Drive, Ads management, write scopes or account mutation.
Read-only connector disclosure
MarketingOS uses Google API data only after a user explicitly connects a Google account for audit evidence.
MarketingOS may request read-only access to Google Search Console. The first verification scope is intentionally narrow: no Google Analytics, Gmail, Drive, Ads management, write scopes or account mutation.
MarketingOS may read verified sites, query and page performance, clicks, impressions, CTR, average position and related read-only Search Console evidence available through the API.
GA4 read-only reporting is planned after the first Search Console verification phase. It should not be requested until live Analytics reporting is implemented and visible in the demo flow.
The data is used to create SEO and GEO audit reports for the connected user or workspace, including source confidence, missing-data caveats, findings, action priorities and verification steps.
MarketingOS does not use Google APIs to edit Google account settings, publish content, manage ads, spend ad budget, send messages, delete user data or change Search Console or Analytics properties.
MarketingOS use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including Limited Use requirements. MarketingOS does not sell Google user data or transfer it to unrelated third parties.
Users can revoke access any time at https://myaccount.google.com/permissions.
MarketingOS is in private beta. The Google connectors are intentionally read-only, and the public policy/disclosure links below describe exactly what data can be accessed before broader self-serve release.