This policy describes Bodell Baseboard and the business integrations operated by Bodell Systems for multiple customer organizations. Viking Tree & Stump is the first pilot customer. Each organization controls its connected resources and authorized users. This policy does not describe unrelated services that may have their own policies.
For Bodell Baseboard and Bodell Systems Integrations access to Google data, see the Google data privacy notice, effective October 4, 2026, including the complete Google permission list and Limited Use commitments.
1. Scope and responsible operator
Bodell Systems operates a platform for authorized read, write, reporting and administrative workflows through Baseboard and connected tools in an AI host such as ChatGPT or Codex. Connections include Jobber, RingCentral, Google Business Profile, Ads/Local Services Ads, Analytics, Search Console and Tag Manager. Available actions depend on the provider, granted permissions and features enabled for the organization. Bodell Systems operates the service; each customer remains responsible for its business records and the changes it authorizes.
2. Information the integration receives
Connected account and tenant information
After an authorized OAuth connection, the service receives the provider account identity, tenant name, authorized user or connection identifiers, granted scopes, connection status, and other metadata needed to bind requests to the correct business account.
OAuth and authentication information
The service receives OAuth access and refresh tokens from connected providers. It does not receive or store your provider passwords. The AI host may maintain its own authenticated connection record under its own privacy and security practices.
Jobber business records and tool requests
The service receives the operation requested by an authorized user, its permitted arguments, requested result fields, and the Jobber data returned or changed by that operation. Depending on the request, this can include customer and property details, requests, quotes, jobs, visits, invoices, payments, schedules, team records, time and expense information, custom fields, notes, attachments, and related business records available under the granted Jobber scopes.
Google and RingCentral information
Google reporting, account and management data are described in the Google data privacy notice. RingCentral connections can provide authorized account, extension, call and message information needed by an enabled workflow, including communication content where that workflow requires it. The data available depends on the connection's permissions and selected resources. SMS sending remains disabled pending the sender's decision, consent controls and required messaging registration.
Webhooks, operational data, and audit records
Connected providers may send webhook events needed to maintain operational state. The service also records timestamps, registered-operation names, query or mutation classification, authorization role, tenant binding, status, correlation and idempotency identifiers, error and recovery metadata, timing, queue and rate-limit information, and security events. Sensitive audit payloads are encrypted, and secrets are not returned through normal audit-inspection tools.
Infrastructure data
Hosting, edge, DNS, and AI providers may process network information such as IP addresses, request headers, timestamps, device or browser characteristics, and diagnostic logs as necessary to deliver and protect their services.
3. How information is used
Information is used to:
- execute supported reads and approved writes on the customer's behalf through an enabled provider feature;
- return requested results to the dashboard or, when requested, the connected AI host and authorized user;
- enforce tenant, role, operation, rate-limit, idempotency, and write-safety controls;
- process supported provider webhooks and maintain reliable operational state;
- authenticate requests, refresh OAuth access, and prevent unauthorized use;
- troubleshoot failures, recover permitted workflows, monitor service health, and maintain backups; and
- maintain audit records for security, accountability, and business operations.
New management features remain off until accepted and enabled for the organization. Before activation, they must enforce the customer's role and resource permissions, review and confirmation for public changes, duplicate/retry protections and clear errors. Write audit records must identify who approved the action, what changed, the approved before/after values and the provider result. Tag Manager publication requires explicit confirmation. An uncertain result must be reconciled before a potentially duplicate action is retried.
4. Authentication and token handling
Provider authorization uses OAuth and the permissions granted for the connection; connected tool access uses its own authentication controls. Access and refresh tokens are stored encrypted at rest; encryption keys are maintained separately from ordinary database records. Token refresh and rotation are handled by the service when the provider requires them. Tokens, client secrets, credentials, and private keys are not displayed in plugin manifests or normal operational responses.
An authorized administrator can revoke access through the provider or disconnect the integration using its available controls. For Google, Baseboard stops local connection use and requests revocation, with failed provider revocation pending retry. Revocation stops future access once it is processed, but business, audit, security, or backup records created before revocation may remain as described below. Disconnection does not undo changes already made in a provider account.
5. Storage, encryption, retention, and deletion
Production connection data, operational state, audit records, and permitted provider data are stored in controlled production systems. Sensitive tokens and sensitive audit data are encrypted at rest. The service maintains operational backups and restricts administrative interfaces and credentials to authorized operators.
The current service does not promise a single fixed deletion period for every category of record. Active connection data is kept while the integration is authorized and needed. Operational, audit, security, and backup records may be retained after disconnection when reasonably needed for troubleshooting, fraud prevention, accountability, continuity, or legal obligations. The implementation relies on controlled administrative deletion and infrastructure backup lifecycles rather than a guaranteed automatic deletion deadline. The Google reporting cache has its separately disclosed 29-day expiry; that expiry does not apply to every audit or business record.
To request access, correction, or deletion, contact integrations@bodellsystems.com. Bodell Systems will verify the request and coordinate with the authorized business account owner. Data may be retained where deletion would undermine security records, legal obligations, or the integrity of backups; backup copies are removed through the applicable provider lifecycle rather than immediate selective erasure.
6. Service providers and disclosures
The integration depends on and may disclose information to:
- Jobber, as the system of record and OAuth/API provider;
- Google and RingCentral, for their connected authorization, data and approved API operations;
- Auth0, for dashboard authentication and organization membership;
- OpenAI services such as ChatGPT or Codex, when the authorized user asks that host to invoke a tool and receive its result;
- Cloudflare, for edge delivery, security, and production infrastructure used by the MCP and legal site;
- Porkbun, for domain registration and DNS services; and
- other vendors or professional advisers only when reasonably necessary to operate, secure, support, or comply with law.
Bodell Systems may disclose information when required by law, to protect rights or safety, to investigate misuse, or as part of a business transaction subject to appropriate safeguards. Bodell Systems does not sell Jobber business data or personal information and does not use it for third-party targeted advertising. Google API data is additionally subject to the Limited Use commitments in the Google notice, including when an authorized user requests a report through an AI host.
7. Security
The service uses measures including encrypted token storage, registered-operation restrictions, tenant and role checks, rate limits, idempotency protections for writes, audit logging, backups, webhook controls, and an administrative write kill switch. No system can guarantee absolute security, uninterrupted availability, or that every attack will be prevented. Authorized users should avoid placing unnecessary sensitive information in tool requests and should report suspected misuse promptly.
8. Your choices
Authorized users may limit the records requested, decline proposed write operations, ask an administrator to disable writes, revoke OAuth access in the connected provider, or ask the account owner to disconnect the integration. Browser and network privacy controls offered by the user's AI host or infrastructure providers are governed by those providers.
9. Policy changes and contact
This policy may be updated as the service, providers, or legal requirements change. The effective date at the top identifies the current version. Material changes will be communicated through a reasonable channel appropriate to the authorized business users.
Questions or privacy requests may be sent to integrations@bodellsystems.com. The related service terms are available in the Terms of Service.