# Privacy policy How Datool handles account information, workspace content, and Shopify customer data. Version: 29 October 2026. ## Who is responsible [#who-is-responsible] Datool is operated by **Vinicius Pacheco Furtado, Rio de Janeiro, Brazil**. For privacy questions and requests, contact **[vini@vinipace.com](mailto:vini@vinipace.com)**. This policy covers Datool's hosted service, website, and our account and support activities. A business using Datool controls the customer information it submits and the instructions given to its agents. We process that workspace information to provide the business's service. We are responsible for our own account, billing, support, and service-security activities. A self-hosted installation is operated by its administrator. Installing Datool does not make us the operator of its database. Ask that administrator about its privacy practices, connected services, and hosting. Information you separately send to Datool support is covered by this policy. ## What we collect and why [#what-we-collect-and-why] | Information | Use | | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ | | Account name, email, organization, membership, authentication and billing references | Sign-in, account administration, subscriptions and support | | Prompts, model responses, traces, evaluations, datasets, uploaded knowledge and attachments submitted to a workspace | Run, observe, evaluate and improve that workspace's agents | | Conversations, contact details, channel identifiers and support requests | Maintain conversation history, identify an authorized customer, route support and perform configured actions | | Store configuration, products, prices and policies; customer and order information permitted by Shopify and the merchant | Answer product questions, verify order ownership and perform the merchant's enabled customer-service actions | | Connection credentials and permission grants | Authenticate to services the administrator connects | | Technical and security records, such as request information, errors and account/activity identifiers | Operate the service, investigate failures and prevent abuse | Information comes from users, workspace administrators, connected stores and channels, and use of the service. The enabled feature and its permissions determine what is processed. Do not submit payment-card credentials, passwords, or sensitive personal information unnecessary for the task. Store checkout and payment providers handle payment details; a chat is not a payment-card collection form. We use information to provide requested services, satisfy applicable legal obligations, and pursue legitimate interests in running and securing Datool, subject to applicable law and individual rights. Where consent is required, it must be obtained for the relevant feature. The merchant remains responsible for its customer notices, legal basis, consent choices and agent instructions. ## AI and connected services [#ai-and-connected-services] A configured model provider receives the context needed for a request, which may include conversation history, retrieved knowledge and tool results. Connected channels and action providers receive the information needed for their enabled functions. See [Service providers and subprocessors](/docs/subprocessors). **Datool does not sell customer personal data, use it for advertising, or use it to train Datool's own AI models.** A provider's own handling depends on the applicable account, product and terms; this statement is not a promise about every third-party model or service. Administrators should choose suitable providers and minimize the personal information sent to them. AI responses can be incorrect. Merchants should offer human support and must not use Datool as the sole basis for decisions with legal or similarly significant effects on individuals. ## Website analytics [#website-analytics] Datool Cloud uses Google Analytics only after you choose **Allow analytics**. It measures public page visits, completed account signups, checkout starts and paid checkouts. Analytics identifiers are pseudonymous; we do not send account emails, names, workspace content, conversations, authentication tokens or internal workspace URLs. Public page URLs exclude query strings and fragments. Paid checkout events include the selected plan, currency, amount and a hashed transaction identifier. A trial or canceled payment does not count as a purchase. Use **Analytics preferences** on any public page to change your choice. Declining does not affect sign-in, billing or product features. Blocking analytics or declining permission means those visits and conversions are not measured. Google processes analytics data under its [privacy policy](https://policies.google.com/privacy). ## Browser storage [#browser-storage] Authentication cookies keep account sessions signed in. The web chat uses browser storage and visitor credentials to associate a visitor with their conversations and preserve chat state, including an unfinished message. Shared devices can retain that state. Clearing browser storage may remove local access or drafts; it does not delete server-side conversation records. Merchant websites and connected services have their own cookie and storage practices. ## Sharing, location and safeguards [#sharing-location-and-safeguards] Access is limited by account roles and project permissions. Authorized operators may access information when needed for support, security, or service operation. We use hosting, logging, email, authentication and payment services as described in the [provider register](/docs/subprocessors). We may disclose information when required by law or necessary to address fraud or threats to the service. Datool is operated from Brazil, and providers may process information in other countries. We do not offer a blanket single-country residency guarantee. A provider's public contract alone does not establish that a particular transfer mechanism or account setting applies to your deployment. The hosted service uses HTTPS, access controls and application encryption for stored connection credentials. We do not represent that every stored record and backup is encrypted, or that Datool has a SOC 2 report. Contact us for the current scope and evidence of safeguards needed for your use case. ## Retention and your rights [#retention-and-your-rights] See [Retention and deletion](/docs/retention) for the current rules and their limits. Disconnecting an integration, uninstalling a Shopify app, or canceling a subscription is not the same as deleting stored workspace information. Depending on applicable law, you may request information, access, correction, export, restriction, objection or deletion, and withdraw consent where processing relies on it. Contact **[vini@vinipace.com](mailto:vini@vinipace.com)**. We may need to verify your identity and authority without collecting unnecessary information. If you are a merchant's customer, contact the merchant first; we assist it with information it controls. You may also contact the competent data-protection authority, including Brazil's ANPD where applicable. These rights and any lawful exceptions remain governed by applicable law. ## Updates and merchant agreements [#updates-and-merchant-agreements] An authorized administrator connecting a Shopify store must acknowledge this policy and the [retention schedule](/docs/retention). Datool records the store, administrator, accepted version and time. This acknowledgement does not replace the merchant's duty to provide customer notices, establish a lawful basis and obtain any customer consent required for its use of Datool. The version above identifies this policy. Material changes will be described in an updated policy; any notice or consent required by applicable law or a signed agreement still applies. Our [merchant data-processing agreement](/docs/data-processing) sets out the proposed processing terms for a written agreement with merchants.