This notice describes Google account connections used by Bodell Baseboard, identified on the consent screen as Bodell Systems Integrations. Bodell Systems operates the service. Each customer organization controls who may connect and use its business resources. This is a multi-tenant service; Viking Tree & Stump is the first pilot customer. The Privacy Policy also covers the connected service, including Jobber and RingCentral.
1. Google information we access
An authorized organization administrator chooses which Google features to connect and which resources to select. The service receives the Google account identifier, granted permissions, OAuth access and refresh tokens, connection status, and selected account or resource identifiers. It does not receive your Google password.
- Google Analytics: authorized account, property and stream metadata, timezone and currency, aggregate reports such as sessions, engaged sessions, key events and reported revenue, and supported key-event and audience configuration.
- Google Ads and Local Services Ads: selected account metadata, advertising performance, and available lead and conversation information. Lead information can include contact details and inquiry content when supplied by the selected source.
- Search Console: authorized sites, sitemap submissions and search-performance information, including queries, pages, clicks and impressions.
- Business Profile: authorized business accounts, locations, reviews and business replies, posts, and supported business information or photos for the selected feature.
- Tag Manager: authorized accounts, containers, workspaces, tags, triggers, variables and versions for the selected feature.
Availability depends on Google's API requirements, granted permissions, account roles and the features enabled for your organization. Gmail, Drive, Calendar, Tasks and Docs/Sheets content permissions are not requested by this marketing connection flow.
2. Requested Google permissions and their uses
The application's requested permission set contains the twelve scopes below, including retained read permissions. Your actual grant may contain fewer permissions. A requested scope is not evidence of Google approval, a live feature or permission to act on every resource.
openid- Identify the Google account granting access and bind its connection to the correct organization. This does not grant access to Gmail or other account content.
https://www.googleapis.com/auth/analytics.readonly- Discover authorized Analytics accounts and properties and read aggregate performance reports.
https://www.googleapis.com/auth/analytics.edit- Create and edit supported GA4 key events and audiences when enabled. Google limits editable fields: event names and core audience membership definitions cannot be freely changed.
https://www.googleapis.com/auth/webmasters.readonly- Read authorized Search Console sites, search performance and sitemap information.
https://www.googleapis.com/auth/webmasters- Submit and remove sitemap submissions for an authorized Search Console property. This does not edit website files or guarantee indexing.
https://www.googleapis.com/auth/tagmanager.readonly- Read authorized Tag Manager accounts, containers, workspaces, tags, triggers and variables.
https://www.googleapis.com/auth/tagmanager.edit.containers- Create and edit supported tags, triggers and variables within an authorized workspace.
https://www.googleapis.com/auth/tagmanager.edit.containerversions- Create a container version from the reviewed workspace changes, a separate step before publication.
https://www.googleapis.com/auth/tagmanager.publish- Publish an authorized container version only after explicit confirmation of that version and its changes.
https://www.googleapis.com/auth/business.manage- Read authorized Business Profile data and, when enabled and approved, create or delete business review replies, create/edit/delete posts, and update supported hours, description, contact or photo information. Removing a reply does not remove the customer review.
https://www.googleapis.com/auth/adwords- Read Google Ads and Local Services Ads account, performance and available lead data; support approved conversion uploads, lead feedback and supported campaign status or budget changes when enabled.
https://www.googleapis.com/auth/datamanager- Deliver authorized conversion or event data through Google Data Manager for configured measurement workflows, subject to separate consent, account binding and delivery controls.
3. Uses, approved changes and availability
Google data is used to discover resources you can access, import selected reports, display business performance, and support configured lead attribution, and carry out supported changes that an authorized customer approves through an enabled management feature. The service also uses connection and operational information to refresh authorization, enforce organization permissions, resume interrupted imports, prevent duplicate records, diagnose errors and maintain security records. Scheduled imports can run while you are signed out until the connection is disabled or authorization ends.
New management features are staged and remain off until accepted and enabled for the organization. Before activation, they must enforce owner/admin permission by default, organization and resource binding, approval controls, retry safety, clear errors and an audit record of the actor, action, approved before/after values and provider result. Public-facing changes require a preview and confirmation. Tag Manager publication requires explicit confirmation of the selected version.
Before editing is enabled, authorization upgrades must preserve existing granted read access and show “Reconnect to enable editing” when additional permissions are needed. Granting a broad scope alone does not enable writes. Reports identify their source and coverage; aggregate metrics or an accepted conversion upload do not prove that a particular person caused a sale.
4. Access, sharing and Limited Use
Reports are available to authorized users of the connected organization. Google processes authorization and API requests. Auth0 supports dashboard authentication and organization membership. Cloudflare provides edge delivery and security. Operational systems process the data needed to run and protect the service.
When an authorized user requests a saved Google marketing report through the connected reporting tool in an AI host such as ChatGPT or Codex, the requested report is returned to that host. The host's processing is governed by the user's account settings and that provider's terms. Connecting Google for dashboard reporting does not itself send every source record to an AI host.
Conversion delivery, provider management actions and reviewed Jobber writeback are separate features with their own permissions, configuration and approval controls. Connecting Google does not itself initiate those actions, send messages or place calls.
Bodell Systems Integrations' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. These limits apply to Google-derived data shared with an AI host as well as data used within Baseboard; a host's terms do not replace these commitments.
5. Storage and retention
Connection credentials and cached Google source data are encrypted at rest. Server-side organization and environment checks restrict access. Access tokens and refresh tokens remain on the server and are not returned in ordinary dashboard or reporting-tool responses.
The Google reporting cache is currently configured to expire 29 days after retrieval. Routine syncs may refresh a local copy and its expiry. Scheduled cleanup removes expired cache data even when provider authorization is unavailable. This local cache period does not delete the original information in your Google account.
Connection records, operational and security records, durable attribution evidence, matching decisions, deduplication receipts, and delivery or correction ledgers have separate lifecycles. They are not all subject to the reporting-cache expiry, and the current service has no universal automatic deletion deadline for these records or their backups. Disconnecting does not automatically erase historical business or audit records.
6. Disconnecting and privacy requests
An authorized administrator can disconnect a Google connection in Baseboard. The service stops local use of that connection and requests provider revocation; failed revocation can remain pending for retry. You can also revoke the app from your Google Account. Provider revocation can affect other features authorized for that Google account. Disconnection does not undo completed changes, remove published content or reverse advertising effects; any correction requires a separately authorized supported operation.
Send questions and requests concerning access, correction or deletion to integrations@bodellsystems.com. Identify your organization and the affected connection without sending passwords or tokens. Request handling requires verification of your authority and coordination with the organization responsible for the business records. This notice does not promise immediate or selective deletion from every audit record or backup.
7. Contact and changes
Bodell Systems is the service operator. The existing privacy contact is integrations@bodellsystems.com. The Google consent screen also provides the configured developer support address. The effective date above identifies this notice; changes to data access or use require an updated disclosure.