Legal
How the Google integration works.
A plain-English explanation of the Google scopes, data use, approval controls and billing separation in MarketPilot OS.
1. Operator and customers
MarketPilotOS is approval-first marketing software operated by GK STUDIO LTD, company number 16048293. It is developed and operated internally for external businesses that use MarketPilotOS to plan and manage their own marketing.
2. Services and permissions
MarketPilot uses openid, userinfo.email and userinfo.profile for Google-backed MarketPilotOS sign-in. The separate provider connection requests webmasters.readonly for Search Console, analytics.readonly for Google Analytics 4 and adwords for Google Ads. A user may connect only the services they choose. For Google Ads, MarketPilot lists only accounts the user owns or is authorised to manage and the user chooses the customer account used by the workspace. Google provides no narrower OAuth scope for the supported Google Ads API functions.
3. Initial Google Ads scope
The intended initial Google Ads API use is Search only. It covers account discovery and selection, Google Keyword Ideas and historical metrics, Search campaign creation and management, and reporting. Search campaign structures include the campaign, budget settings, ad groups, keywords, negatives and responsive search ads. Display and Performance Max are not part of this initial scope.
4. Planning, creation and management
MarketPilot labels Google data separately from MarketPilot interpretation and lets the user review keywords, match types, groups, negatives, targeting, creative and budget. Google OAuth data access and Google Ads API Basic Access are approved. The controlled 24-operation validation and a real PAUSED provider-creation read-back passed. Eligible paid workspaces can create and manage approved Search campaigns within configured budget controls.
5. Approval and provider boundary
Campaign work remains review-first. Provider validation must pass before an immutable, single-use approval can be created. New provider campaigns are created PAUSED. Activation is a distinct, explicitly approved action that can start Google media spend. MarketPilot does not activate campaigns, increase budgets or start spend automatically.
6. Reporting
MarketPilot uses Google Ads reporting for the selected authorised account to show provider-returned campaign performance and account health. Provider metrics remain identified as Google data and are not fabricated or presented as guaranteed results.
7. Search Console access
The Search Console read-only permission is used to list verified properties and retrieve query, page, country, device, click, impression, CTR, average position, freshness and sitemap information for SEO reporting.
8. Google Analytics access
The Analytics read-only permission is used to list GA4 properties and report on Organic Search behaviour, including users, sessions, engaged sessions, engagement rate and key events. Timezone, currency and data-quality limitations remain visible.
9. Token and workspace protection
Why access is requested and the Google data used are described above for each customer function. Google OAuth tokens are exchanged server-side, stored with authenticated encryption and bound to one MarketPilot workspace. Direct Google integration credentials are never reused for MarketPilot sign-in. Google user data is not sold and is not used for unrelated advertising or to train generalised or personalised AI models. Access is checked again before discovery, reporting, selection or an approved action.
10. Google Maps
Google Maps is separate from OAuth. Address search and service-area maps use a separately restricted Google Maps Platform API key and do not add a user-data OAuth permission.
11. Disconnect, revoke and deletion
Users can disable one Google service locally or disconnect the complete Google connection. A complete disconnect clears selected resources and attempts provider token revocation. Users can also revoke MarketPilot in their Google Account and request deletion through the published data-deletion process.
12. Billing separation
A MarketPilot subscription is separate from Google Ads media spend. MarketPilot does not attach or manage Google Ads billing. Google Ads costs remain billed by Google through the customer's own authorised Google Ads account.
Questions about this page can be sent to support@marketpilotos.com. Business or ownership matters can be sent to founder@marketpilotos.com.