YOOPixel
PricingAbout
ARLog inContact
  1. Home
  2. /Privacy
PrivacyYOOPixel

Privacy PolicyClear rules for your data

This policy explains how YOOPixel collects, uses, and protects personal data across our website, products, AI tools, and storefront assistants.

Last updated13 July 2026

Read the policy ↓

Contents

  1. 1. Who we are
  2. 2. Information we collect
  3. 3. How we use information
  4. 4. Storefront assistants and connectors
  5. 5. Artificial intelligence and subprocessors
  6. 6. When we share data
  7. 7. Retention
  8. 8. Your rights
  9. 9. Cookies and similar technologies
  10. 10. Security
  11. 11. International transfers
  12. 12. Children
  13. 13. Changes to this policy

1. Who we are

YOOPixel provides software products, SaaS platforms, and professional services. For privacy requests, contact privacy@yoopixel.com or use our contact page. Where a merchant installs our storefront assistant on Magento or WooCommerce, the merchant is ordinarily the controller of shopper data on that store. YOOPixel processes chat and connector data as a service provider in line with the merchant’s configuration and this policy.

2. Information we collect

We collect only what is needed to operate, secure, and improve our services.

  • Account and organisation details: name, email address, company, role, billing information, and authentication identifiers when you register or join a client console.
  • Project and discovery data: messages sent to YOO, discovery session content, project-analysis answers, uploaded context, and generated reports.
  • Storefront assistant (shoppers): chat messages, the short conversation history supplied with each request, language, page URL and title, visible page text used for context, a browser session identifier, optional country signals, and product or navigation events (such as opening the assistant, product recommendations, add to cart, coupons, checkout assistance, and assisted orders).
  • Storefront assistant (optional customer profile): if the merchant enables customer prefill, the assistant may receive first name, last name, email, phone, and shipping address from the logged-in store session. If prefill is disabled, we typically receive only a signed-in indicator and first name, or less.
  • Merchant store connection: store URL, encrypted store API credentials after a successful connection, hashed connector tokens, webhook secrets, branding and tool settings, and aggregated storefront analytics associated with the connected store.
  • Technical and usage data: IP address, browser and device information, pages viewed, referral URLs, and approximate location derived from IP address or CDN country headers.
  • Communications: support tickets, booking requests, emails, and feedback.
  • Payments: processed by our payment provider (for example Stripe). We do not store full card numbers on YOOPixel servers, and the storefront chat never collects card data.

3. How we use information

  • Provide, operate, and secure our website, console, licensing platform, hosting services, AI analysis features, and storefront assistants.
  • Operate storefront chat: answer product and page questions, recommend catalogue items, suggest cart, coupon, or checkout actions that run in the shopper’s browser on the merchant’s store, and—where Support tools are enabled—look up order status through the store API using details the shopper provides in chat.
  • Measure AI usage and attribute assisted commerce events to sessions for merchant analytics in the console.
  • Produce discovery and project-analysis reports you request, including optional web research.
  • Process payments, manage credits and subscriptions, and send transactional notices.
  • Respond to support, booking, and sales enquiries.
  • Improve reliability, prevent abuse, enforce rate limits, and detect fraud.
  • Send product updates or marketing only with consent or where permitted by law.

4. Storefront assistants and connectors

Merchants connect a store using a one-time connection token. Credentials are stored in encrypted form. API secrets must not be exposed in public storefront HTML. Disconnecting or revoking a connection removes connection secrets and disables the embed. Cart, coupon, and checkout actions execute on the merchant’s storefront in the shopper’s browser. Contact fields used for checkout assistance require explicit consent in the widget before prefill. We do not retain full chat transcripts by default; each request includes the recent history needed to respond. Session analytics may retain counters, country, and—where provided—email or order identifiers for attribution. Historical analytics may remain after disconnect until deleted following a merchant or data-subject request.

5. Artificial intelligence and subprocessors

Certain features send prompts and related context to vetted AI and web-research providers solely to generate the responses or reports you request. Storefront chat may include the visitor’s message, recent turns, page or product context, limited profile fields when configured, and catalogue or order summaries returned from the merchant’s store. We do not list vendor names in this policy because our stack may change; a current list is available on request at privacy@yoopixel.com. We do not use private project content or storefront chat content to train public foundation models. Providers process data under their own terms and may retain limited logs for security and abuse prevention. AI outputs may be incomplete or inaccurate—verify material decisions independently. Product recommendations depend on the merchant’s catalogue and store APIs.

6. When we share data

We do not sell personal information. We share data only with:

  • Infrastructure and tooling providers (hosting, email, analytics, and error monitoring) under appropriate contractual protections where required.
  • AI and research providers, solely to deliver features you or the merchant have enabled.
  • Payment processors, to complete transactions.
  • The merchant’s commerce platform (Magento or WooCommerce), when the assistant or connector calls APIs the merchant has authorised.
  • Professional advisers, where necessary to protect our rights or comply with law.
  • Competent authorities, where legally required or to prevent harm, fraud, or abuse.

7. Retention

Account and billing records are retained for the life of the organisation relationship and as required for tax and legal obligations. Discovery sessions and reports follow your plan and console settings; specific reports may be deleted where the product allows. Storefront session analytics are capped and rotated in the ordinary course of operations. Merchants—and shoppers via the merchant or privacy@yoopixel.com—may request deletion of identifiable storefront records. Security and server logs are retained on an operational schedule. We continue to strengthen automated retention and deletion controls as the product matures; material changes will be reflected in this policy.

8. Your rights

Depending on your location, you may have rights to access, correct, delete, restrict, or export personal data, and to object to certain processing. Contact privacy@yoopixel.com to exercise these rights. Shoppers should also contact the merchant whose store they used. We will respond within a reasonable period. You may also complain to your local data-protection authority.

9. Cookies and similar technologies

On yoopixel.com we use essential cookies for authentication, session security, and language preferences. The storefront assistant may store a session identifier in localStorage and/or short-lived cookies, and may keep a checkout draft in sessionStorage to continue a conversation. Optional analytics or marketing cookies on our marketing site, if used, will be disclosed through browser settings or a consent mechanism where required. You may clear site data in your browser; disabling essential cookies may limit console functionality.

10. Security

We apply industry-standard safeguards, including TLS in transit, access controls, least-privilege administration, encrypted connector credentials, and monitoring. Storefront embeds are designed so Magento and WooCommerce API secrets are not printed into public HTML. We continue to harden credential storage, connector security, and compliance documentation over time. No method of transmission or storage is perfectly secure; please use strong passwords and protect account credentials.

11. International transfers

YOOPixel operates with team members and infrastructure in more than one region. Where personal data is processed outside your country, we rely on appropriate safeguards—such as standard contractual clauses or equivalent mechanisms—where required.

12. Children

Our services are intended for businesses and professionals. Storefront assistants may appear on merchant shops open to the public. We do not knowingly collect personal data from children under 16 for YOOPixel accounts. Merchants remain responsible for the age-appropriateness of their own stores.

13. Changes to this policy

We may update this policy from time to time, including when new product capabilities materially change how personal data is handled. The “Last updated” date above reflects the current version. Material changes will be posted on this page. Continued use after an update constitutes acceptance where permitted by law.

See also ↓

See also

Questions about privacy? We respond within one business day.

Contact us →Terms of Service
Questions about privacy? We respond within one business day.
YOOPixel

A software company building SaaS platforms and products for agencies and businesses that need a real technical partner.

Platform

ProductsSolutionsPricing

Services

Project Strategy & DiscoveryDigital Product EngineeringBusiness Platforms & OperationsCustom AI & Intelligent SystemsIntegrations, APIs & DataAll services →

YOOPixel Hub

Log inService management and pricing — coming soon

Company

AboutContact

© 2026 YOOPixel

PrivacyTerms