Privacy Policy
Effective November 10, 2026
This policy explains how Customer Luv handles personal data. We built our apps to respect shoppers — no advertising trackers, no tracking pixels, no link-rewriting — and this policy reflects that.
1. Who we are & what this covers
Customer Luv ("Customer Luv", "we", "us") is a family of Shopify applications — Surveys, Luv Reply, Luv Cart, Pop Up & Quiz, Earnaroo, Upsell, Luv Variant Images, Quiz, Subs, and Tracking — operated by Life Vitamin Co. LLC. This policy applies to our websites (customerluv.app) and our apps (together, the "Services"). Capitalized terms not defined here have the meaning given in our Terms of Service.
2. Our two roles: controller and processor
For personal data about our merchant users (account, billing, and support information), we act as a data controller. For personal data about a merchant's shoppers that we process when a merchant uses the Services (for example, survey answers, contact-form messages, and order references), the merchant is the controller and we act as a processor / service provider — processing that data only on the merchant's documented instructions and under our Data Processing Addendum.
3. Personal data we collect
- Merchant account data: your name, business name, email, shop domain, and the authentication identifiers Shopify provides at install.
- Store configuration: settings, question sets, targeting rules, templates, and any integration keys you choose to add.
- Shopper data (processed for the merchant): depending on the app — survey responses with the associated order reference and order email; contact-form submissions (name, email, message); cart and checkout interactions; subscription and shipment details; reward-code claims; and game wins (Earnaroo, below). We do not require, and we ask merchants not to collect, special-category (sensitive) data.
- Usage & technical data: log data, IP address, device and browser type, timestamps, and diagnostic events used to operate, secure, and improve the Services.
We do not use third-party advertising trackers, tracking pixels, or link-rewriting redirects in buyer-facing communications — a deliberate design choice.
4. Where the data comes from
Directly from you; automatically from your use of the Services; and from Shopify and the integrations you connect (such as Klaviyo or Google Analytics) at your instruction.
Amazon. When a merchant connects their Amazon seller account in Luv Tracking, we read that merchant's Amazon Multi-Channel Fulfillment orders and package tracking through Amazon's Selling Partner API, read-only. We keep only what tracking needs: tracking and package numbers, delivery status, scan descriptions with city, region and country, timestamps and Amazon's estimated arrival. We do not receive or store buyer names, addresses or contact details from Amazon. This data is used only to show that merchant's customers their delivery status, is never sold or shared with other merchants, is deleted 90 days after delivery, and is erased at once when the merchant disconnects Amazon or uninstalls the app. The merchant's Amazon access token is stored encrypted.
Earnaroo. With the merchant’s permission, Earnaroo reads the store’s products and creates discount codes. When a shopper wins a game and asks for their code, it keeps what the merchant’s form asks for: the email address and, if the merchant asks, the first name, phone number and answers to the merchant’s own questions, with whether the shopper agreed to marketing email. It also keeps the score, which product facts they knew and missed, the code issued, the page they played on, and a one-way hash of their IP address (used only to limit how many codes one connection can claim). The same applies on a game’s own page at app.customerluv.app/g/. It sends these details to the merchant’s Klaviyo only when the merchant connects Klaviyo, and adds a shopper to a Klaviyo list only when they agreed. In the shopper’s browser, the storefront script keeps small records in local and session storage (keys starting clvplay:, not cookies): whether they closed the game or hid its corner teaser, and the code they won with its end time, so the game doesn’t keep reappearing; the month it last counted this browser as a store visitor, so each browser is counted once a month for the merchant’s plan; and, for a code that comes with a free gift, the gift it added to the cart. To add that gift, it checks up to three discount codes on the shopper’s cart with Earnaroo, which only answers whether a code is one of its gift codes and keeps nothing. A merchant who connects Claude or ChatGPT to Earnaroo lets that assistant read the store’s winners, including their email addresses, when the merchant asks it to.
Luv Cart. With the merchant’s permission, Luv Cart reads the store’s orders, customers, products, discounts and theme. For orders placed through its cart drawer it keeps the order number and date, the currency, the order total, the upsell, gift and discount amounts, the items ordered (product, title, quantity and price), the Shopify customer ID and a random cart session ID. It does not store customers’ names, email addresses, phone numbers or addresses: the customer list (Insights › Customers) asks Shopify for names and emails each time the merchant opens it and does not keep them. To suggest products bought together, it reads the store’s last 60 days of orders and keeps only product-pair counts, with no customer details. The drawer reports shopping events (opened, upsell added, gift added, reward reached, checkout) under the random session ID, never with a name, an email or a typed discount code. When the merchant turns on Klaviyo, Added to Cart events go from the shopper’s browser to the merchant’s Klaviyo account through the store’s own Klaviyo script; with Next pick on, Luv Cart sends the ordering customer’s email address and a product suggestion to the merchant’s Klaviyo account and does not keep the email. The merchant’s Klaviyo private key is stored encrypted. A customer’s drawer orders are deleted under customers/redact, and all of a store’s Luv Cart data under shop/redact.
Luv Upsell. With the merchant’s permission, Luv Upsell reads the store’s orders, customers, products (including their prices and compare-at prices) and theme, manages one discount of its own, and adds a tag to the customer of each order that carried one of its offers (“Luv Upsell Purchased” unless the merchant changes it; the merchant can turn this off) and, when the merchant asks, saves a customer segment for that tag. When a merchant or their staff asks Ady, Luv Upsell’s AI helper, about prices or sales, it also reads product costs and, with the merchant’s permission to read reports, the store’s sales totals from Shopify’s reports (by product, variant or period, with no customer details); it looks them up signed in as the person asking, so Shopify applies that person’s permissions to the lookup, and what it reads is kept in that chat, which others who can open Luv Upsell on the store can also see (see AI helpers below). For each order it keeps the order number and date, the currency and the order total, so it can compare orders with and without an upsell; for orders that carried one of its offers it also keeps what was taken from them (product, title, quantity and price) and the Shopify customer ID, and for post-purchase offers which offer was shown and whether it was taken. It does not store customers’ names, email addresses, phone numbers or addresses: the customer list (Insights › Customers) asks Shopify for names, emails, lifetime value and order counts each time the merchant opens it, and which customer placed each order that saw an offer, and does not keep them. To suggest products bought together, it reads the store’s last 60 days of orders and keeps only product-pair counts, with no customer details. Its storefront offers report views, adds and declines under a random session ID, never with a name or an email. For shoppers who allow analytics in the store’s cookie banner, it also notes what each cart and checkout was shown and did with its offers, under a one-way hash of the cart’s or checkout’s own ID (never the ID itself, and never a name, email or address), so the merchant’s Insights › Orders, and Ady, can say what an order saw; those notes are kept for at most 60 days, or 14 days when no order follows. Insights › Orders asks Shopify for each customer’s name when the merchant opens it and does not keep it. For each customer it tags, Luv Upsell keeps the Shopify customer ID and the tag, so it tags each customer once. When the merchant connects Klaviyo, Luv Upsell sends the ordering customer’s email address with each accepted offer, and with each declined post-purchase offer, to the merchant’s Klaviyo account, plus a product suggestion when Next pick is on; it does not keep the email. Adds and declines from its storefront offers can also reach the merchant’s Klaviyo account from the shopper’s browser through the store’s own Klaviyo script. The merchant’s Klaviyo private key is stored encrypted. A customer’s Luv Upsell records, including what their orders saw, are deleted under customers/redact, and all of a store’s Luv Upsell data under shop/redact.
Luv Variant Images. With the merchant’s permission, Luv Variant Images reads the store’s products (titles, options, variants and images, with their file names and alt text) and the published theme’s settings file, and writes its own setup to the store’s products and shop and, when the merchant chooses, each variant’s main image. When the merchant does it in the app, it also adds photos to a product (uploaded to the store’s own Shopify files, or picked from them), changes a photo’s file name, alt text or place in the gallery, or takes a photo the merchant just added back off the product; it never deletes a photo. For each product the merchant sets up or that the app looks at to find candidates, it keeps the product’s ID, title, handle and main image address, the setup (which images show for which option values) and its status, plus the store’s settings. It does not read or store anything about shoppers or customers: its storefront code runs in the shopper’s browser, reads the setup from the product page itself and sends nothing anywhere. All of a store’s Luv Variant Images data is deleted under shop/redact.
AI helpers. Some apps include an AI helper that a merchant chooses to talk to inside the app (Ady in Surveys, Pop Up & Quiz, Luv Upsell, Luv Variant Images, Luv Tracking and Luv Cart; Roo in Earnaroo). When a merchant uses one, we send Anthropic, our AI provider, what the helper needs to answer: the merchant's messages, that app's own settings (for example question sets or popups), summary results such as answer counts and response rates, the store's public product and website text when the merchant asks the helper to read the store, in Luv Tracking, order numbers with shipment statuses and carrier scans, in Luv Cart, the drawer’s settings with summary results such as orders, revenue, upsell revenue and gifts given, in Luv Upsell, its funnels and design with summary results such as views, take rate, upsell revenue and the products bought together, the products’ prices, compare-at prices, costs and margins, and the store’s sales totals from Shopify’s reports (by product, variant or period, with no customer details), and, in Luv Variant Images, product titles, option values, image file names and alt text, and each product’s setup, plus the one product photo the merchant asks Ady to describe when they click Use Ady, with the product’s title and the value the photo is for, so Ady can say whether the photo shows that product. Our helper tools do not send shoppers' names, email addresses, phone numbers, street addresses or written answers; we ask merchants not to paste shopper details into a chat. Anthropic processes this data only to provide the service to us and, under its commercial terms, does not use it to train its models. Chats are kept with the store's data so the merchant can come back to them, and are deleted under shop/redact when the store uninstalls the app. Nothing a helper suggests changes what shoppers see until the merchant clicks to confirm it.
5. How we use data, and our legal bases
We use personal data to provide and operate the Services (performance of contract); to provide support and maintain security and prevent fraud or abuse, and to improve the Services (legitimate interests); to send service and transactional messages (contract / legitimate interests); to comply with law (legal obligation); and, where required, with your consent (which you may withdraw). We do not sell personal data, do not "share" it for cross-context behavioral advertising, and do not use shopper data for our own advertising or across different merchants.
6. Sub-processors
We use vetted providers to run the Services, including Cloudflare (hosting, storage, and security), Resend (transactional email delivery for the platform sender), Anthropic (the AI model behind our in-app AI helpers, only when a merchant uses one), and Shopify (the commerce platform). When a merchant enables an integration (for example, Klaviyo or Google Analytics), data is transmitted to that provider at the merchant's instruction and under that provider's terms. A current list of sub-processors is available on request at hi@customerluv.app.
7. When we disclose data
We disclose personal data only to sub-processors under contract; to a merchant (for their own store's data); to comply with law or valid legal process; to protect rights, safety, and security; and in connection with a merger, acquisition, or asset sale, with notice.
8. International transfers
Data may be processed in the United States and other countries. Where we transfer personal data out of the EEA, the UK, or Switzerland, we rely on appropriate safeguards such as the Standard Contractual Clauses.
9. Retention and deletion
We keep personal data only as long as needed to provide the Services and for legitimate business or legal purposes, then delete or anonymize it. We honor Shopify's mandatory privacy webhooks: customers/data_request (we record the request and send the store the data we hold about that shopper), customers/redact (we delete that shopper's data), and shop/redact (once a store has removed every Customer Luv app, we delete all of its data within 30 days. While any of our apps is still installed, the store's data is kept, so removing one app doesn't erase data the others use. Two things go when their own app is removed: that app's AI helper chats and memory, and all of Earnaroo's data). Merchants can export or request deletion of their data at any time.
10. Security
Data is encrypted in transit (TLS) and at rest. Access is shop-scoped and gated by Shopify session-token authentication, so every request is restricted to the installing store. We apply least-privilege access, abuse caps on outbound email, and safeguards for platform secrets. No method of transmission or storage is perfectly secure, but we work hard to protect your data and to notify affected parties of incidents as required by law.
11. Your rights
Depending on where you live, you may have rights to access, correct, delete, port, restrict, or object to processing, and to withdraw consent. EEA and UK residents may also complain to a supervisory authority. To exercise a right, email hi@customerluv.app. If you are a shopper, contact the store you purchased from (the controller) and we will assist them.
12. California residents (CCPA / CPRA)
In the prior 12 months we collected the categories of personal information described above for the business purposes stated. We do not sell or share personal information as those terms are defined by the CPRA, and we do not use sensitive personal information for purposes that would trigger a right to limit. California residents may exercise rights to know, delete, correct, and to non-discrimination by emailing hi@customerluv.app.
13. Shoppers
If you completed a survey, sent a contact-form message, played a game, or otherwise interacted with a store using our Services, that store is the controller of your data. Our surveys and forms are optional and every survey question is skippable. Contact the store, or us, to access or delete your information.
14. Cookies
Our marketing site uses only essential cookies needed for security and basic functionality; our admin uses the cookies and session tokens required to authenticate you to Shopify. On stores that use Earnaroo, its storefront script keeps the small browser-storage records described above (no cookies). We do not use advertising or cross-site tracking cookies.
15. Children
The Services are intended for businesses and are not directed to children under 16 (or the age defined by local law). We do not knowingly collect their personal data.
16. Changes
We may update this policy. We will update the "Effective" date and, for material changes, provide additional notice. Continued use of the Services after a change means you accept the updated policy.
17. Contact
Life Vitamin Co. LLC · hi@customerluv.app