Effective date: 20 October 2026.
Who provides the Pilot
DASHBOARDLY INC provides Dashboardly AI Pilot. This notice explains the Pilot connector's data handling and related Dashboardly account processing. It supplements Dashboardly's general privacy policy. For privacy questions or requests, contact hello@dashboardly.io.
What the Pilot does
The Pilot offers two read-only workflows: comparing modeled offer economics from numbers you provide, and preparing supplied video or product-page evidence for a draft conversion review. It does not make financial transactions, change your store, send messages, purchase advertising or change budgets. Modeled results describe your assumptions and are not a verified statement of actual store profit.
Information sent through the connector
When you call a tool, the AI service you use sends Dashboardly the tool arguments. These may include prices, quantities, discounts, fees, shipping, product costs and scenarios, or text such as creative transcripts, product descriptions, page observations, links and your selected review scope. Dashboardly returns calculated results or structured supplied-evidence material to that service for its response to you.
The current workflows do not fetch a supplied page or video URL, automatically retrieve store financial records, or receive your entire conversation history or unrelated files. Text you include in a tool argument is still sent to Dashboardly. Provide only information needed for the task; use synthetic or de-identified examples when possible, and do not include passwords, access tokens or unnecessary personal information.
Connection and service information
Dashboardly processes account identifiers, the selected merchant and shop, permissions, OAuth client and authorization records, and connection tokens to authenticate requests and limit access. Connection tools return the context and shops permitted by your grant. This does not authorize access to other merchants or shops.
We also process service-usage and security information, including the account/client involved, tool name, outcome, time, duration and response size. Hosting and network systems may process IP addresses and request metadata such as routes and query strings. The Pilot audit path does not include tool arguments or results in its usage record; that does not mean every infrastructure or support system has zero retention.
How we use information
We use this information to provide the requested tools, authenticate connections, enforce permissions, maintain service reliability, investigate abuse and respond to support or privacy requests. The current calculation and evidence-preparation handlers do not invoke another model or save their domain inputs and outputs in a separate application table. If you share a tool result with support, it becomes part of that support interaction.
Dashboardly account and communication services
Using a Dashboardly account can also involve ordinary account, contact, activity, subscription and shop-setup information. These related services are distinct from the contents of a Pilot tool call. Customer.io supports account/lifecycle communication and engagement processing, and Attio supports CRM and related account/contact records. Relevant routes can include email addresses, account attributes, activity events and email-engagement information.
The inspected Pilot tool and connector credential-validation paths do not directly export tool arguments or results to Customer.io or Attio. Ordinary Dashboardly sign-in and other account/lifecycle routes can still process related personal information. This is not a promise that every manual support action, integration or historical record excludes Pilot-related context.
Service providers and your AI service
DigitalOcean provides the primary hosting and managed database infrastructure for this Pilot. The inspected primary host and database are in New York, United States; this identifies those systems, not every recipient, log, backup or other copy. We do not promise that all processing stays in that region.
The AI service you choose also processes your conversation, tool requests and returned results under the terms and privacy controls applicable to your account with that service. Disconnecting Dashboardly does not delete conversations or files held by your AI service. Its role and retention terms should be reviewed separately from Dashboardly's service-provider arrangements.
Storage and retention
Authentication records have different lifetimes. The configured lifetimes are one hour for access tokens, one minute for authorization codes, ten minutes for authorization interactions, thirty days for sessions, and ninety days for refresh tokens and grants. These lifetimes do not establish expiry of every client-registration credential, database record, log or backup.
Some client-registration credentials and durable usage/connection records require separate review or deletion. Revoking a grant does not by itself erase all of those records or copies. Infrastructure logs and backups have their own handling and recovery processes.
Dashboardly has approved retention targets of thirty days for usage, seven days for routine raw IP addresses, fourteen days for ordinary logs and ninety days for minimal security metadata. Inactive client registrations are to be reviewed after ninety days, with protection for active grants across all merchants. Approved deletion targets are up to thirty days for primary records and sixty days for relevant copies after an applicable deletion request. These are implementation targets: production enforcement and deletion across all relevant copies have not yet been accepted. They must not be read as current deletion guarantees or achieved maximum storage periods.
Your controls and requests
Choose only the shops and permissions needed when connecting. You can disconnect the connector and revoke Dashboardly connection access using the available account controls. Disconnecting stops that authorization; it is not an instruction to erase every account, usage, backup or AI-service record.
Contact hello@dashboardly.io to request access, correction or deletion, or to ask about applicable privacy rights. We may need to verify the request and distinguish your own account information from information belonging to another merchant. Any legal retention requirements or limits to deletion will be explained for the request. Manage conversation history and other data retained by your AI service through that service's controls.
Changes and contact
We will identify the effective date of material updates and make the current notice available with the connector documentation. Questions: hello@dashboardly.io.