Who operates this service
Daxko AI Digital Intelligence is a Daxko reporting application for teams and clients. Application support is available at rahul.verma@daxko.com. Privacy-rights requests may be sent to Daxko’s Legal Department at legal@daxko.com. Daxko’s published corporate notice identifies Daxko LLC, 600 University Park Place, Suite 500, Birmingham, Alabama 35209.
Information we access and collect
Account and session information: your authenticated Manus account identifier, name, email address, sign-in activity, and opaque application-session identifiers. Your Manus sign-in and your Google data authorization are separate steps. We do not receive your Google password.
Connected Google information: Google Analytics property identifiers and labels; Google Ads customer identifiers, account labels, currency, timezone and applicable manager identifiers; Search Console site identifiers and access information; aggregate metrics and selected report dimensions for the accounts and dates you choose. Depending on the report, dimensions can include pages, search queries, campaigns, keywords, search terms, devices, countries, channels and conversion-action names.
Authorization information: Google access tokens, refresh tokens, expiry timestamps and granted scopes. These allow account discovery, report retrieval and proactive credential checks. Provider credentials are encrypted before storage and are not exposed to the browser or sent to the AI provider.
Other connected sources: when you connect Microsoft Clarity, we store the API token, project label and aggregate observation snapshots, and can collect daily snapshots. Meta Ads is shown as coming soon and is not currently a released connection.
Reports and assistance: your chosen date ranges, report definitions, source results, generated summaries, chat questions and answers, and usage records. Operational records include report/connection identifiers, timestamps, status, error categories and support references. Infrastructure providers may also process request metadata needed to operate and secure the website.
Google permissions and their purpose
Google Analytics uses analytics.readonly to discover accessible properties and retrieve their analytics reports. Search Console uses webmasters.readonly to discover accessible sites and retrieve search-performance results. Each is requested when you explicitly select that source; choosing GA4 does not automatically choose Search Console.
Google Ads uses the adwords scope because Google’s Ads API uses that scope for account discovery and reporting. The scope is broader than read-only, but this application only performs account discovery and reporting queries: it does not create or edit campaigns, change budgets, place advertisements, or manage billing.
You choose the specific property or customer account after Google authorization. Reports are scoped to that selected account. You can refuse a requested scope, disconnect a connection, or revoke access in your Google Account; the affected integration will then be unavailable.
How we use the information
We use connected data to discover accounts you can access, validate your selection, collect and save your requested reports, compare supported periods, export results and display coverage. Proactive Google access checks refresh credentials approximately daily per workspace so connection problems can be shown before a report run. Clarity snapshot collection is a separate daily feature.
If you enable AI processing, we also use selected report evidence to produce visible summaries and answer your report questions. We use operational information to secure the service, diagnose failures, enforce usage limits and respond to support requests. We do not use connected Google data to build advertising audiences, target advertisements, sell data, perform surveillance or assess creditworthiness.
AI processing and your choice
AI processing is off until you affirmatively enable it for your workspace. Reports, account connections and exports remain available without enabling AI. You can disable future AI processing in the workspace’s AI privacy control. Disabling it does not erase existing saved summaries or chats; use the deletion controls described below.
When enabled, report summaries can be generated automatically for completed reports. We send minimized aggregate metrics, date ranges, coverage, currency/timezone information and bounded numeric table evidence to Anthropic’s commercial API. Report chat can additionally send selected report dimensions or labels, your question and relevant prior chat context. Treat free-text questions as information shared with Anthropic; do not enter passwords, credentials, sensitive personal records or information you are not authorized to share.
The application does not send provider access tokens, refresh tokens or raw credential records to Anthropic. We do not submit connected Google data for general-purpose model training or send model-training feedback. Anthropic states that commercial API inputs and outputs are not used for model training by default, and that standard API inputs and outputs are deleted within 30 days, subject to its contractual, legal and abuse-prevention exceptions. No zero-data-retention agreement is represented by this notice.
Disabling AI stops new AI requests authorized after that change. A request already sent to Anthropic may finish, and disabling AI cannot recall data already processed by a provider.
Google API Services Limited Use
Daxko AI Digital Intelligence’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. These protections apply to raw Google data and data aggregated, anonymized or derived from it.
Google-derived information is used only to provide the prominent, user-facing reporting and, with your consent, AI-assistance features described here. We do not use it for advertising, generalized AI model training, resale, surveillance or lending decisions. Any materially different use requires an updated disclosure and renewed consent before that use begins.
Storage, security and retention
Connections and saved report data are stored in the application’s managed database. Provider credentials are encrypted at the application layer using a dedicated production key. Browser sessions use opaque tokens; only their hashes are stored server-side. Access checks and administrative grants restrict workspace and operator actions. HTTPS protects supported production connections. No internet service can guarantee absolute security.
Saved reports, report definitions, summaries and chat remain until you delete them or request account/workspace deletion. Connected credentials remain until the connection is removed or the account is deleted. There is no automatic expiry promise for saved reports.
Operational-event cleanup targets three days for routine scheduler events and 90 days for diagnostics. Cleanup runs in bounded batches when the scheduled maintenance callback succeeds; outages or a backlog can delay removal. Separate administrative audit, consent and usage records are not covered by that event-cleanup schedule and may be retained for security, request handling and operational accountability. Hosting-provider records and backups follow those providers’ policies; immediate backup erasure is not promised.
Access, export, revocation and deletion
Disconnect an account in Connections to remove its stored application connection and credentials; disconnecting a Clarity connection also removes its stored observation snapshots. Previously saved reports are separate records and are not deleted by disconnecting. Google’s grant is separate from the application connection: revoke it in your Google Account if you want to remove Google-side authorization too.
Download available CSV/PDF report exports from report detail. Clear a report conversation to delete the stored chat for that report; quota/usage records remain. Delete a completed, partial or failed saved report to remove its report row, source results, summary and chat. Reports that are queued or running must finish before the report-deletion control can be used. Operational history remains under its separate retention rules.
For whole-account/workspace deletion, access or correction requests, email the support contact or legal@daxko.com from the account address and identify the application. We may verify your identity and authority before acting. Some records may remain where necessary for legal, security or operational accountability purposes. Your rights and any response deadlines depend on applicable law and Daxko’s corporate notice; this page does not invent a new guaranteed deletion deadline.
Children and policy changes
This is a business reporting service, not a service directed to children under 13. Do not provide children’s sensitive records through reports or chat. Contact Daxko’s Legal Department if you believe such information was submitted improperly.
The date above identifies this notice’s version. Material changes to Google-data use or AI transfer will be disclosed before the changed use, with renewed consent where required. Daxko’s corporate privacy notice provides additional rights and contact information.