Privacy Policy
Last updated November 15, 2026
The short version. Noluco helps online stores understand why shoppers leave without buying. It notices how shoppers browse a store (for example, how long the delivery section stayed open) and tells the store why they left. It never collects names, email addresses, phone numbers, postal addresses, payment details or anything a shopper types into the store's forms. If the store turns on Ana, its AI salesperson, shoppers can tap or type a question; typed questions are answered with most personal details removed first, and are not kept (section 3a). It follows the store's own cookie and privacy settings: where the store asks shoppers for consent, Noluco waits for it.
1. Who we are
Noluco is a product of 8-FigureFellowship Inc., a Wyoming corporation ("Noluco", "we", "us"). Contact: vuk@noluco.com.
Stores use Noluco in one of two ways: as a Shopify app, or, on other platforms (for example Magento or a custom store), through a tag the store adds in its own Google Tag Manager. We act in two roles:
- For shopper data, we are a processor (service provider) for the store that uses Noluco. The store decides to use Noluco, sets its own cookie and consent settings, and is responsible for telling its shoppers. Questions about a store's use of your data are best sent to that store.
- For merchant account data (the store's details and settings, the email addresses and Slack or Discord channels a store adds to receive its morning report and alerts, each email address only once its owner accepts, and for stores that subscribe directly, the plan and the billing contact's name and email), we are the controller. Reports are emailed through Resend. Every email has a stop link, and a store's list is deleted with its data.
2. When Noluco runs
Noluco follows the consent settings of the store you visit, the same way the store's other analytics and marketing tools do:
- Shopify stores use Shopify's Customer Privacy API. Where the store shows a cookie banner, Noluco waits for your choice and starts only if you allow analytics. Where the store's settings don't ask visitors for consent (Shopify's setting for some regions, such as many US states), Shopify reports analytics as allowed and Noluco runs.
- Other platforms: Noluco reads the store's own consent signal (its cookie banner, or Google Consent Mode) and stays off until that signal allows analytics.
- Using browsing data for advertising and email (section 4) additionally needs marketing permission and no "do not sell or share" opt-out (including Global Privacy Control where the store honors it).
3. What we collect about shoppers
- A random visitor number we create and store in a first-party cookie on the store's domain (with a copy in the browser's local storage for that domain, under the same consent, because some cookie managers delete cookies they don't recognize), and a visit number that expires after 30 minutes without activity.
- Only with marketing permission, identifiers other services already placed on the store: Meta's browser and click IDs (
_fbp, _fbc), Google Analytics' browser ID (_ga), Google's click ID (gclid), and Klaviyo's link code (_kx). These are random codes. We cannot turn them into a name or email. On a first visit we also note whether Meta's and Google's cookies appeared (yes or no), so the store can be told if its tracking stops.
- For logged-in shoppers on Shopify, the Shopify customer number (not the name or email).
- Browsing signals: which pages and products were viewed (the page address, with account, login, checkout and order pages reduced to their section name and anything that looks like an ID or code removed, and the product's public name), which sections were opened or read (price, shipping, returns, size chart, reviews, subscription) and for how long, size changes, whether an item was added to the cart and whether it was on sale, whether the discount-code box in the cart was clicked and, on Shopify, whether the cart turned down a code you entered during that visit (never the code or what was typed in it), whether a page was a sale page, where the visit came from as a category only (such as Meta, Google, email or direct, never the page it came from), and phone or computer.
- Checkout progress: which checkout steps were reached and when, whether the order was completed, and on Shopify the completed order's subtotal and currency (for the store's average order; never what was bought), whether a code, an automatic discount or a selling plan lowered its price and by how much and whether it used one of the discount codes the store gave Ana (counted, not kept with the visit; other codes are dropped), and on Shopify whether the discount-code box in checkout was clicked or a code was turned down (never what was typed in it). On Shopify this is reported by Shopify; on other platforms it is read from the store's own checkout and order confirmation pages. Never the content of any checkout field.
- Technical data: the browser's user agent and request times. Like any website, our servers receive your IP address with each request; we use it only to block abuse and don't store it in our database (our hosting provider keeps short-lived request logs).
We never collect: names, email addresses, phone numbers, postal addresses, payment details, anything typed into forms or search, screen recordings, mouse trails, or data from shoppers who declined where the store asks for consent. Labels on the page (such as "Delivery") are read in your browser to recognize sections; only the section type leaves your browser.
3a. Ana, the store's AI salesperson
Some stores turn on Ana, who offers help on a product page when a shopper seems unsure (for example after a long read of the delivery section) and answers from the facts, size charts and product claims the store approved. Ana is always shown as an AI. She runs only where the store's settings allow marketing for your visit, and only if the store has turned her on.
- In the cart, if the store turns it on: when your order is close to the store's free shipping, Ana may suggest a few pieces that get it there, using the store's own product recommendations and the size already in your cart; and if you click the discount box, she asks whether she can help and you can ask her a question. If you ask for a deal, she may offer one of the discount codes the store gave her (she never makes one up) and put it in your cart, where Shopify checks the store's rules for it. To offer a code at most once in the period the store chose, Noluco keeps a record that it offered one to your random visitor number (up to a year). On Shopify Plus stores, the same help can appear in checkout under the shipping methods: for that, the free-shipping amount or the code is saved with your cart (as a cart attribute the store can see on the order).
- Taps: which help was offered and which answer you tapped (codes such as "delivery" or "size"), as part of the browsing signals in section 3.
- Typed questions: before a typed question leaves your browser, and again on our server, most personal details are removed (names, email addresses, phone and card numbers, order numbers, postal addresses). What's left goes to our AI provider, Anthropic (section 5), together with the product's public details and the store's approved facts, and the answer comes back to you. On stores with a large catalogue, a few words from the question that can name a product (never the whole question) also go to the store's own product search on Shopify, to find what you asked about. Noluco does not store what you typed. Typing can be switched off by the store; taps always work.
- Memory, only if you ask Ana to remember you: what you agreed to keep (your height, weight and body shape if you shared them and chose to have them remembered, your fit preference, your usual size and the sizes she recommended), so she can suggest your size next time. It's stored encrypted in the EU, linked to the random visitor number (and your customer number on that store if you're logged in), used only by that store's Ana to suggest sizes, and never sent to advertising or email tools.
- On your device: a cookie that remembers which help this visit already had (
_nlc_help) and whether a suggestion was shown (_nlc_sug), both ending with the visit, and a local storage entry with which kinds of help you were offered and opened (_nlc_habits, kept a year), so Ana doesn't repeat herself; in the cart, session entries that remember whether her free-shipping suggestion or help was shown or closed, and whether you typed in the cart's discount-code box during this visit (never what you typed) (_nlc_cart_…), gone when you close the tab. All are deleted with the other Noluco cookies when you withdraw consent.
4. How we use it
- To work out why shoppers left without buying, and show the store a report.
- Only if the store connects them, and only with marketing permission: to send the reason, together with that service's own random code, to the store's Klaviyo, Meta or Google account, so the store can reach the shopper with an answer through those services. If a shopper who hesitated buys anyway, the store's services are told that too (the reason, the product and how many days later), so the store can group them, for example to send a size guide with a new product.
- If the store turns on Ana: to answer shoppers' questions, and to show the store how often Ana helped and whether those shoppers bought.
- To run, secure and improve Noluco.
We do not sell personal data. We do not use shopper data to train AI models. Where we use an automated model to classify browsing, it receives browsing signals only, never identifiers.
5. Who we share it with
- Service providers that run Noluco: Vercel (hosting, Frankfurt region), Supabase (database, Frankfurt), Upstash (abuse limits, EU region: request counts under a one-way scrambled form of the network address, deleted within two days), Shopify (platform, for Shopify stores), Stripe (payments, only for stores that subscribe directly on noluco.com: the store's billing contact and company details; card details go to Stripe and never reach Noluco), and Anthropic (the AI model behind Ana's typed answers and behind preparing the facts a store approves, in the United States: it receives typed questions with most personal details removed, the product's public details and the store's approved facts or public pages, never our visitor numbers or other identifiers; under its commercial terms it doesn't use them to train its models).
- Services the store connects, as described in section 4: the reason 30 minutes after the visit ends, never for shoppers known to have bought or who withdrew consent during the visit. If a shopper who hesitated buys (in that visit or later), the reason they hesitated on, the product and how many days later they bought, never what they bought or what they paid. For Klaviyo, Noluco also reads the store's own "Placed Order" records in Klaviyo (by Klaviyo's profile number, never names or emails) to find shoppers who bought later on another device, up to 13 months after the visit. Each service matches it to a person inside its own systems under its own privacy policy:
- Klaviyo: the reason, a short description of what happened (for example "read shipping info for 31 s"), the product (name, link, and image on Shopify), the browsing numbers (for example seconds spent on shipping, times opened, whether checkout was reached), the visit's reference number and Klaviyo's own code.
- Meta: the reason, the product ID, the page address, the same browsing numbers, Meta's own browser IDs, a one-way scrambled (hashed) version of our visitor number, and the browser's user agent.
- Google Analytics: the reason, the product ID, the same browsing numbers and Google Analytics' own browser ID.
- Authorities, if required by law.
6. Products that may involve health information
Some stores sell products, such as supplements, where browsing could reveal something about a person's health. Each store decides whether that applies to its products and is responsible for the notices and consents its laws require (for example Washington's My Health My Data Act) before connecting advertising or email tools. Noluco follows the store's settings and sends only what is described above. Meta and Google also apply their own restrictions to health-related data.
7. How long we keep it
- Raw browsing signals: 2 days.
- One record per visit with the reason worked out for it (used for reports and the store's audiences): 35 days; visits that looked at nothing in particular, 8 days.
- Daily report totals (counts per reason, product and device; nothing about individual shoppers): 13 months.
- Hourly totals per store for health alerts, with no shopper data: 8 days.
- Records of what was sent to connected accounts: each send 35 days, then only daily counts per account, 25 months.
- Live visit status (for "browsing now"): 2 days.
- Ana's memory (only if you asked her to remember you): a year after it was last updated, or sooner when you tap "Forget what I told you", withdraw marketing consent in a browser where she remembers you, or ask for deletion. Typed questions: not stored.
- When a Shopify store uninstalls Noluco, its connected API keys are deleted immediately and all of its data is deleted when Shopify sends the shop deletion request (about 48 hours later), except the store's billing record (plan, dates and status, no shopper data), which we keep as accounting law requires and to apply the one-free-trial-per-store rule. For stores on other platforms, all of their data is deleted within 30 days of the end of the agreement.
8. Your choices and rights
- Shoppers: decline or withdraw consent in the store's cookie banner and Noluco stops, deletes its cookies and their local copies on your device (on the next store page if the banner reloads the page), and sends nothing from that visit to the store's connected tools. To delete what Ana remembers, tap "Forget what I told you" in Ana. To have data deleted, ask the store: on Shopify, Shopify forwards the request to us; other stores send it to us directly. Because we don't know your name or email, the store is the one that can identify your data. See data deletion.
- Depending on where you live (for example the EU, UK, Serbia or California), you may have rights to access, delete or correct data, or to opt out of sharing for cross-context behavioral advertising. Noluco honors the choices the store's consent settings record, including Global Privacy Control where the store supports it.
- Merchants: email us for a copy of your account data or to delete it, or uninstall the app.
9. Security and transfers
Data is encrypted in transit, stored in the EU (Frankfurt), and connected API keys and Ana's memory are additionally encrypted at rest. Ana's typed questions are processed by Anthropic in the United States and not stored by us. Access is limited to people who need it to run Noluco. Where data moves between the EU and the US, we rely on the safeguards our service providers offer, such as standard contractual clauses.
10. Children
Noluco is a business tool for stores. It is not directed at children.
11. Changes
We will post changes here and update the date above. Material changes are announced to merchants in the app or by email.