Webracle

Privacy Policy

Last Updated: September 29, 2026

At Webracle, we take your privacy seriously. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our AI shopping assistant service.

1. Information We Collect

1.1 Information You Provide

  • Account Information: Email address, name, and password when you create an account
  • Store Information: When you connect your e-commerce store (Shopify, etc.), we collect store URL, product catalog, and order data necessary to provide our service
  • Payment Information: Billing details processed securely through our payment processor (we do not store full credit card numbers)
  • Communications: Information you provide when you contact our support team

1.2 Information Automatically Collected

  • Conversation Data: Customer conversations with your AI assistant for service improvement and analytics
  • Usage Data: How you interact with our service, including features used and time spent
  • Technical Data: IP address, browser type, device information, and operating system
  • Analytics: We use privacy-focused analytics (Plausible.io) that doesn't use cookies or track personal data

2. How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve our AI shopping assistant service
  • Process your transactions and send related information
  • Send you technical notices, updates, and support messages
  • Respond to your comments, questions, and customer service requests
  • Monitor and analyze usage patterns to improve our service
  • Detect, prevent, and address technical issues and fraudulent activity
  • Comply with legal obligations

3. How We Share Your Information

We may share your information with:

3.1 Service Providers

  • AI Model Providers: When you connect your AI model, conversation data is sent to your chosen AI provider (OpenAI, Anthropic, etc.) to generate responses.
  • Payment Processors: Stripe or similar services for billing
  • Analytics Services: Plausible.io for privacy-focused analytics
  • Infrastructure Providers: Cloud hosting services for data storage and processing

3.2 Legal Requirements

We may disclose your information if required by law, legal process, or government request, or to:

  • Comply with legal obligations
  • Protect and defend our rights or property
  • Prevent fraud or other illegal activity
  • Protect the safety of our users or the public

3.3 Business Transfers

If we are involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change.

4. Data Security

We implement appropriate technical and organizational security measures to protect your information, including:

  • Encryption of data in transit (HTTPS/TLS)
  • Encryption of sensitive data at rest
  • Regular security audits and updates
  • Access controls and authentication requirements
  • Secure data centers with physical security measures

However, no method of transmission over the internet or electronic storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

5. Data Retention

We retain your information for as long as your account is active or as needed to provide our services. Specifically:

  • Account Data: Retained until you delete your account, then deleted within 90 days
  • Conversation Data: Retained for service improvement and analytics, deleted 90 days after account deletion
  • Billing Data: Retained for 7 years for legal and tax compliance purposes
  • Backup Data: May persist in backups for up to 90 days after deletion

6. Your Rights (GDPR & CCPA)

Depending on your location, you may have the following rights:

  • Access: Request a copy of your personal data
  • Rectification: Request correction of inaccurate data
  • Erasure: Request deletion of your data ("right to be forgotten")
  • Data Portability: Request your data in a machine-readable format
  • Restriction: Request limitation of processing your data
  • Objection: Object to processing of your data
  • Withdraw Consent: Withdraw consent at any time (doesn't affect prior processing)

To exercise these rights, contact us at contact@webracle.com. We will respond within 30 days.

7. Cookies and Tracking

We use minimal cookies and tracking technologies:

  • Essential Cookies: Required for authentication and service functionality
  • Analytics: Plausible.io for privacy-friendly analytics (no cookies, no personal data tracking)
  • Security: Cloudflare Turnstile for bot protection (replaces CAPTCHA)

We do not use advertising cookies or sell your data to third parties.

8. Children's Privacy

Our service is not intended for individuals under 18 years of age. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately, and we will delete it.

9. International Data Transfers

Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place, including:

  • Standard Contractual Clauses approved by the European Commission
  • EU-US Data Privacy Framework (where applicable)
  • Other legally-approved transfer mechanisms

10. Webracle Convert (storefront analytics)

Webracle Convert measures how visitors move through a merchant's online store, builds a behavior profile of each visitor from that activity, and shows them notices that it chooses automatically from that profile. It runs on the merchant's storefront through a script (WooCommerce, Magento) or a web pixel (Shopify). In this section the visitors of the store are "shoppers" and the store owner is the "merchant".

10.1 What Convert collects from shoppers

  • Pages and actions (all platforms): the full address of each page viewed (including any query string; on the WooCommerce order confirmation page the address contains the order key), product views, additions to the cart, the start of checkout, completed orders, and the time of each event
  • Interaction (WooCommerce and Magento only): scroll depth and the moments the pointer leaves the top of the window. For a click, the element's tag, identifier, class and the first 100 characters of its visible text, which may incidentally include personal data the page shows to that shopper. For a form field, only its name, never what is typed
  • Device and origin (WooCommerce and Magento only): language, device type, browser identification string (user agent) and the page the shopper came from. The script also sends the screen and window size, the time zone and the campaign parameters of the address, and the event store discards them on receipt
  • Purchases (all platforms): the order identifier, the currency and the order lines (product, quantity and price). The shopper's name, email, phone number and addresses are not stored
  • Identifiers and browser storage: a visitor identifier and session and tab identifiers generated at random in the browser and kept in its local and session storage; a session ends after 30 minutes without activity. On WooCommerce and Magento the store also keeps the visitor identifier in a first-party cookie named webracle_convert_vid, set by the store's own server and not readable by scripts, renewed at most once a day while the shopper keeps visiting and expiring 400 days after its last renewal, so that a returning shopper is recognized when the browser clears its local storage; the browser also keeps the identifiers of the last 50 orders completed in it, to avoid counting an order twice. On Shopify the browser keeps the identifier of the last notice Convert served to it, together with the visitor, session and tab identifiers. Convert does not identify shoppers from the characteristics of their device or browser
  • Behavior profile: from these events Convert derives, for each visitor, each session and each visit (a stretch of consecutive activity of one visitor), a running profile: the pages visited with a count per address, the number of product views, additions to the cart, clicks and form field focuses, whether checkout was started and whether the pointer left the top of the window, the average scroll depth, the time spent on pages, the hour of the day, the furthest step of the merchant's funnel reached, the device type and the user agent. The visitor profile is kept under the visitor identifier
  • Notices shown: Convert decides automatically whether to show a shopper a notice and which one. It applies the rules the merchant set (which events trigger a notice and how often it may appear) and, for notices the merchant lets Convert manage, a model that weighs the shopper's furthest funnel step in the current visit and overall, the device type and whether the shopper is new or returning, together with what each notice achieved in earlier visits. That model also chooses at random a minimum share of the time (5%) so that no notice is ignored for ever. If the merchant configures an experiment, each visitor is assigned once to a group, derived from the visitor identifier, and a group can be set to see no notices at all. For every decision Convert records the visitor, session and visit identifiers, a snapshot of the behavior profile, the notice chosen (or none), the notices considered and, once a notice is displayed, the time it was displayed

Convert's event store does not include IP addresses. The IP address of each request is used in memory to limit request rates and appears in the operational request log of the Convert service.

10.2 Consent

On Shopify, the platform's customer privacy settings decide when the Convert pixel runs: in regions where shoppers must consent to tracking, the pixel runs only after consent is given. On WooCommerce, when the store uses a consent tool compatible with the WP Consent API, Convert starts only after the shopper accepts both the statistics and the marketing categories; if the shopper later refuses either of them, Convert stops at once and deletes its identifiers from the browser, including the cookie described above. On Magento, when the store enables Magento's cookie restriction mode, Convert starts only after the shopper allows cookies; that mode offers shoppers no way to withdraw from the storefront. Where the store has no such mechanism (a WooCommerce store without a consent tool compatible with the WP Consent API, or a Magento store with cookie restriction mode off, including stores that use other consent tools), Convert runs whenever it is enabled for the store and does not read the shopper's choice. The merchant is responsible for obtaining any consent required from its shoppers, as set out in our Terms of Service.

10.3 Retention

Convert data is kept until a deletion is requested. It does not expire on its own, including after a subscription is cancelled.

10.4 Access and deletion

  • Shopify: when Shopify notifies us of a customer erasure request, Convert deletes all the data it holds for the visitors who placed those orders. When it notifies us of a shop erasure request, Convert deletes all the data of the project linked to that shop, unless the shop still has an active installation of our app, in which case we review the request manually. Deletions are applied asynchronously, so they can take some time to complete. Customer data requests are recorded, and Convert does not export data automatically
  • WooCommerce and Magento: these platforms send us no erasure or access notices. Convert can locate a shopper's data only through the identifier of an order that shopper placed, so the data of visitors who did not place an order cannot be located by shopper. Convert has no automated procedure to answer access requests. You can contact us at contact@webracle.com, stating the identifiers of the orders involved
  • Limits: a deletion for one shopper does not change the aggregated learning counters, which are kept per store, action and device type rather than per visitor and combine journeys as hashed samples. They are removed only when all the data of a shop is erased. A browser that keeps the script installed is measured again after a deletion

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by:

  • Posting the new policy on this page with a new "Last Updated" date
  • Sending you an email notification if the changes materially affect your rights

Your continued use of the service after changes become effective constitutes acceptance of the revised policy.

12. Contact Us

If you have questions about this Privacy Policy or our data practices, please contact us at contact@webracle.com.