How Zeopilot handles account, website, evidence and connected-service data.
Your content is not a marketing product
We do not sell customer workspace content or share it with third parties for their marketing. Your website goals, private source content and mission evidence are used to provide, secure and support the Zeopilot features you choose.
This does not mean that no service provider processes data. Hosting, email, payment and AI providers may process the minimum information required for the relevant service, subject to the disclosures below and applicable agreements. Public website content remains public; access to private workspace data is controlled separately.
Information we process
Zeopilot processes account information, workspace and team information, website URLs and configuration, connected-provider metadata, business outcome definitions, monitoring results, governed change records, evidence, reports, support communications, and security/audit events needed to provide the service.
Provider secrets and credentials are handled separately from ordinary application data and are designed to be encrypted or tokenized where supported. Zeopilot is designed to minimize collection of customer end-user personal information unless it is necessary to verify an agreed website outcome.
Free public website analysis
The free website analysis reads a limited set of publicly available website signals to produce an outside-in brief. It is read-only and does not connect to private systems or make changes to the submitted website.
To improve Zeopilot, we may retain privacy-minimized derived patterns from scans—such as finding categories, platform/business classification, response timing and aggregate technical signals. The learning dataset is designed not to retain raw page content, the raw submitted URL, visitor identity or IP address, and these derived scan observations are automatically expired after one year.
How information is used
We use information to authenticate users, operate Business Uptime, prepare and verify governed changes, deliver reports and alerts, secure the service, prevent abuse, troubleshoot incidents, provide support, and improve reliability and product quality.
Zeopilot is designed to keep business claims, evidence and inferred conclusions distinct. Customer data is not treated as permission to make unrestricted production changes.
Connected services & classified backend data
When you connect a provider, Zeopilot receives only the access granted through that provider and the scopes shown in the product or provider authorization screen. Connections are intended to be scoped, visible and revocable. Disconnecting a connection removes Zeopilot's local execution authority and locally stored credential material according to the product's credential lifecycle.
Secure Sync is designed to use read-only OAuth scopes, application passwords or API tokens rather than storing ordinary website-admin passwords. Provider credentials are encrypted separately with authenticated encryption. Raw synchronized backend datasets are encrypted at rest and classified within the customer tenant. Reports and Director grounding use aggregate summaries and derived insights by default; raw customer-level source records are not sent to the AI Director unless a separately governed workflow explicitly requires that data and the customer has authorized it.
Google user data we access and use
When you connect Google Analytics, Zeopilot uses the analytics.readonly permission to list the properties available to your account and read reporting data for the GA4 property you select. This includes active-user and page-view counts, page and device breakdowns, and historical visitor trends.
When you connect Google Search Console, Zeopilot uses the webmasters.readonly permission to list your available sites and read search-performance information for the site you select, including page URLs, clicks, impressions, click-through rates and average search position.
When you connect Google Ads, Zeopilot requests the adwords permission to discover accounts you can access and read the advertiser account you select. We read account and manager identifiers, account names, currency, timezone, test-account status, and aggregate impressions, clicks, ad spend, reported conversions and conversion value for the last 30 complete account-local days. Google offers no read-only Ads scope: its consent screen describes broader account management access, but this Zeopilot integration only lists accounts and reads reports. It does not create or edit ads, campaigns, bids or budgets. Account totals may include several websites and are not verified payments or profit.
We use this Google user data to provide the connected reports in Live Intelligence and relevant website-activity explanations. We store connection identifiers, your selected property, site or Ads account, authorization metadata and encrypted OAuth credentials to maintain the connection. These reporting integrations do not request permission to edit or delete your Google Analytics or Search Console data.
Who receives Google user data
Your workspace: Google reporting data and derived summaries are available to authenticated members of your Zeopilot workspace who have access to the reporting features. Workspace owners control who joins their workspace.
Infrastructure providers: Zeopilot processes Google user data on infrastructure supplied by service providers acting on our behalf, including Contabo for application and database hosting. This processing supports hosting, storage, security and operation of the connected reporting features.
Google: authorization requests, access and refresh tokens, selected property, site or Ads account identifiers, and report-query parameters are sent to the relevant Google authorization and reporting services to authenticate the connection and retrieve the reports you request.
AI processing: Zeopilot uses OpenAI for AI features. When you use an AI feature, your question and the relevant application context may be sent to OpenAI to generate the requested response. If you include Google reporting information in that question or context, OpenAI receives that information for this purpose. The current Live Intelligence GA4 and Search Console report requests, Google Ads account reports and their rule-based suggested next steps, and the Director's direct GA4 traffic response are processed by Zeopilot without sending those API report responses to OpenAI. Zeopilot does not include Google OAuth credentials in its AI prompts.
Support, security and legal disclosures: authorized Zeopilot personnel or service providers may access specific Google user data with your agreement to provide support, when necessary to investigate a security issue or abuse, or when required by applicable law. Where legally required, data may be disclosed to the relevant authority. Any transfer as part of a merger, acquisition or asset sale requires your explicit prior consent where Google's Limited Use requirements apply.
We do not sell Google user data or transfer it to advertising platforms, data brokers or information resellers. We do not use or transfer it for targeted advertising, creditworthiness or lending decisions, or training generalized AI or machine-learning models. Transfers are limited to the purposes described above and Google's applicable requirements.
Google data protection, retention and your controls
Zeopilot uses HTTPS for requests to Google's services, encrypts stored OAuth credentials, and checks workspace and website ownership before retrieving connected reports. Reporting snapshots may be temporarily cached to support the dashboard; connection records and relevant security or audit records are retained as needed to operate, secure and support the service.
You can disconnect a Google connection in Connections. Disconnecting stops new authorized report retrieval through that connection and deletes its locally stored OAuth credential record. It does not delete data in your Google account, and provider-side revocation is separate. You can also remove Zeopilot's access through your Google Account's third-party connections controls. Google revocation applies to all grants for that user in the same Google Cloud project, so removing Google Ads access there may also disconnect your Zeopilot Analytics and Search Console connections. Zeopilot's local Ads disconnect does not perform that project-wide revocation.
Previously retained connection metadata, audit records and copies in backups are handled through the applicable retention and offboarding process; disconnecting is not an immediate erasure of every historical record. Contact Zeopilot through in-product support to request deletion of retained Google-related data or workspace closure. Records needed for security, legal compliance or recovery may be retained as described in this policy.
Zeopilot follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs. These restrictions also apply to data aggregated or derived from Google API data.
Retention, export and deletion
Workspace owners can use product controls to export supported workspace data and to initiate governed workspace closure. Security, legal and recovery records may be retained for a limited period where necessary to protect customers, prevent fraud, comply with law, resolve disputes or complete a requested offboarding process.
Retention settings may vary by plan, configuration, law and customer agreement.
Security and isolation
Zeopilot uses tenant isolation, least-privilege controls, MFA for privileged workflows, audit trails, encrypted backup practices, approval binding and kill switches as part of its security model. No system can guarantee absolute security; customers should also maintain appropriate security for their own websites and connected providers.
Your choices
You can review and revoke provider connections, manage team access, configure monitoring and governance settings, export supported data and request workspace closure through the product. Additional rights may apply depending on your location and customer agreement.
Contact
Privacy questions can be submitted through Zeopilot's in-product support channel or the legal contact method provided in your customer agreement or order form.