Legal
Privacy Policy
Last updated 2 November 2026
This policy explains what personal data Findlane collects, why, how long we keep it, and your rights. Findlane is a hosted product search service for online stores, operated by Mucho ehf. in Iceland ("Findlane", "we", "us").
Who is responsible
- For accounts and this website, we are the controller: the data of people who create an account, use the dashboard, or visit findlane.dev.
- For our customers' content and their shoppers' searches and events, the customer (the store) is the controller, and we process that data on the store's behalf, as its processor, under our Terms of Use. If you searched or shopped at a store that uses Findlane, contact the store about that data.
You can reach us about privacy at privacy@findlane.dev.
What we collect
When you create an account and use the dashboard
- Your name, email address, and password. We store only a secure hash of the password.
- Workspace information: workspace names, members and their roles, invitations you send (including the invitee's email address), and API keys, which we store only as hashes.
- Sign-in sessions: the IP address and browser (user agent) each session signed in from, to keep your account secure.
- Email we send you: confirming your address, resetting your password, invitations, notices about your workspaces, and a weekly report on each workspace's searches, which you can turn off. We don't send marketing email.
- Shared reports: a workspace's owners can share a read-only report of its searches at a secret link, and have it emailed on Mondays to people outside the workspace. We keep those email addresses, and email each one when it's added, until it unsubscribes, an owner removes it, or the report is deleted. The report lists searches made at least 3 times, never who made them.
When you buy a plan
- Our reseller Polar sells paid plans, as the merchant of record. It collects your payment details, billing name and address, and any tax ID under its own privacy policy. We receive your plan, its billing period and status, and the name and email address you bought with. We never see full card numbers. To bill overage, we send Polar the number of extra searches and records a workspace used.
When a store installs Findlane for Shopify
- From Shopify, about the store: its name, its myshopify.com address and main domain, its currency, whether it's a development store, and its email address. The email becomes the Findlane account that owns the store's workspace, or the workspace is added to an existing account with that email.
- A token to read the store's products, which we store encrypted. If the store turns on Bought together, the token can also read its orders, and we keep which products were in each order, as described under "When a store sends events" below. The app has no access to customers' names, email addresses, phone numbers, or addresses.
- The app's checkout pixel, which Shopify runs only when the shopper allows analytics, sends each completed checkout and each product added to the cart as events: the products, quantities, prices, currency, and the order's ID, which we keep only as a hash. With the store's visitor IDs on, it adds the IDs the store's search box keeps in the shopper's browser.
- The store's active products: title, handle, description (up to 1,000 characters), vendor, product type, tags, prices, whether they're in stock, and the address of the main image. They become the store's index, which is customer content as described below.
- Stores that buy a plan in the app pay Shopify, under Shopify's own terms and privacy policy. We receive the subscription's plan, status, and renewal date, and send Shopify the overage charges.
- When a store uninstalls the app, search stops on its storefront at once, and the orders read from Shopify are deleted. Shopify asks us to delete the store's data 48 hours later, and we then delete its workspace, index, and records. The Findlane account stays until you ask us to delete it. When Shopify asks us to delete a customer's data, we delete that customer's orders.
When a store installs Findlane for WooCommerce
- Nothing is sent before the store's owner connects it to a Findlane account. Connecting makes a key limited to the store's index, which the plugin keeps in WordPress.
- The store's address, the versions of the plugin, WordPress, WooCommerce and PHP, and the plugin's checks, sent daily.
- The store's published products: name, address, image, prices, stock, SKUs, brand, categories, tags, attributes, description (up to 1,000 characters), rating, sales and date added. Findlane reads them from the plugin with a secret, and they become the store's index, which is customer content as described below.
- Searches from the store's search box and results page, with the shopper's IP address and browser, as under "When shoppers search a store that uses Findlane" below.
- If the owner chose paid orders: each order's ID, products, quantities, prices, currency and time, never the customer's details, kept as described under "When a store sends events" below.
- When the store disconnects or deletes the plugin, its key is revoked and Findlane stops reading the store. The workspace, index and records stay with the Findlane account until its owner deletes them.
When customers use the service
- The content customers upload to their indexes, such as product catalogs. We process it only to provide the service to them.
- A product feed's address, and the username and password it needs, if any, which we store encrypted. We fetch the feed only to fill its index, and keep a copy of the file only while a run reads it, or, when a run is held, until a later run replaces it, and never longer than a week.
- What's written to an index: when, by which API key, feed or app, and how many records it added, changed or removed, kept for up to 90 days to show the customer what came in. For a write we refused, also the reason and one record's ID, until newer refusals replace them.
- To suggest search settings, the names of an index's fields and a few of their values are read by an AI model that runs on our cloud hosting provider's network. We keep its answers with the index.
- With the recommendations add-on, the text of an index's products (such as titles, categories, descriptions, and prices) is read by AI models on the same network to build each product's lists. We keep the lists, and the products' vectors, with the index. No shopper data is used.
When you connect an AI app
You can connect AI apps, such as Claude, ChatGPT, Cursor, or your own agent, to Findlane's MCP server, so they can manage your workspaces for you.
- The app registers itself with us: its name, the addresses we send you back to after you sign in, and any website or logo it gives. We show its name when you connect it, on the keys it creates, and under Connected apps.
- When you connect it, you sign in and choose the workspaces it can reach. We keep that choice (the app, your account, and the workspaces) until you disconnect the app under Connected apps on a workspace's API keys page. The workspace's owners can see the apps its members connected.
- The app gets access tokens that last an hour and refresh tokens that last 30 days. We store only hashes of them.
- The app acts as you, with your role in each workspace, so it can read and change what you can in the dashboard. Each change it makes is written to our technical logs: the tool, your account, the app's name, the workspace, and the tool's inputs, with lists and objects given only as counts. Searches it runs to check its work aren't counted in search analytics.
- We receive only the tool calls the app sends, never your conversation with it. What a tool returns, such as your records, settings, or search analytics, goes to the app and to the company that runs it, under that company's own terms and privacy policy.
When shoppers search a store that uses Findlane
- The search request: the query, filters, sort, and page, along with the network information every website receives, including the IP address.
- For the search analytics a store sees in its dashboard, we keep: the query's words (lowercased, up to eight), the names of filtered and faceted fields (their values only as below), the sort, the number of results, the response time, and the country and network location that answered the request.
- For searches made from a shopper's browser, we also keep the approximate location our hosting provider derives from the IP address (region and city, with coordinates rounded to about 10 km), the device type (mobile, tablet, or desktop), the browser's preferred language, and the address of the site the search came from. When such a search finds nothing, we also keep the values of its filters, such as a category or a color, so the store can see which filters left shoppers with nothing. When a search shows one of the store's banners, we count it for that banner, with the query's words, the filters and the site. Search analytics don't include IP addresses or user agents.
- To say why searches found nothing, the words of queries searched at least 3 times that found nothing (as kept for analytics above) are read by an AI model that runs on our cloud hosting provider's network, with a few of the index's product names, category names and queries that found results. We keep its answers with the index. They never include anything else about the shopper.
- The store's dashboard lists its latest searches with the time rounded to the minute. It names a town only after at least 100 searches in 30 days came from it, and shows the region otherwise.
- To show a store which visitors take the most results in a day, a sign that someone may be copying its catalog, each search made from a browser also keeps a hash of the shopper's network address and the index. It's made with a random value that changes every day and is deleted after the next day, so it can't be traced back to the address, and a shopper gets a new hash each day and at each store. With it we keep how many results the search returned and how far it paged, which fields it asked for, the name of the network it came from (such as an internet provider), the browser's name and main version but not its full user agent, and a fingerprint of how the browser set up its secure connection, which tells browsers from scripts.
- IP addresses are used briefly to limit how many searches and events one visitor can make, and are discarded within minutes.
When a store sends events
- Stores can tell us what shoppers do with their products: views, clicks, add-to-carts, and orders, sent from their pages or their servers, or read from a Shopify store that allows it. Findlane's own search box, React components, and Shopify app send clicks on results, recommendations and banners, and the Shopify app sends product page views; the Shopify app only when the shopper allows analytics. For each event we keep its type, the product, the query's words or the recommendation list it came from, its position, quantities, prices and currency, and the country, device type, and site it came from. For a click on a search result, we also keep the search's filter values, and whether the search page was opened from an ad (and the ad network), an email, or another site's link, never the ad's click ID or campaign; with visitor IDs on, the store's page remembers this for the visit. Events don't include IP addresses, user agents, cookies, or order IDs.
- If a store turns on visitor IDs, its events also carry two random IDs: one for the shopper's browser, which the store's page keeps in the browser's storage and replaces after 13 months, and one for the visit, which ends after 30 minutes without events. A store's server may send its own anonymous IDs instead, never an email address or a phone number. They link one shopper's events on that store. We keep only a keyed hash of each ID, different for each store, so a shopper's events at two stores can't be linked, and they don't identify the shopper by name. The store decides whether to send them and is responsible for any consent they need; Findlane's Shopify app sends them only while the shopper allows analytics. When a store asks us to forget an ID, for example because the shopper asked it to, we delete the events sent with it within a week.
- For orders, to show which products are bought together, we keep which products were in each order, when it was placed, and a hash of its order ID, so an order counts once and can be cancelled. We keep no customer details or amounts with them.
- If a store counts orders sent from shoppers' browsers, each such order keeps, for two days, a hash of the shopper's network address and browser. It's made with a random value that changes every day and is then deleted, so it can't be traced back to the address. It lets us count at most three orders a day from one visitor.
When you visit findlane.dev
- The website sets no cookies and uses no advertising trackers. As with any website, our hosting provider processes your IP address to deliver pages and protect the service.
- We count page views with Yaap. For each page you open, it records the page's path, the website that linked to it (the site, not the full address), any campaign labels in the link, your browser, operating system and device type, and an approximate location (country, region, and city) derived from your IP address. Yaap doesn't keep IP addresses or user agents.
- Yaap also keeps a random visitor ID in your browser's local storage for 180 days, and a session ID that ends when you close the tab or after 30 minutes without activity. They let us count unique visitors, how long they stay, and the path they take through the site. Yaap stores the IDs only in hashed form, and they don't identify you by name.
- You can opt out at any time with Opt out in the notice, or Privacy choices at the bottom of every page. Yaap then deletes the IDs from your browser and counts your page views without them, so it can't tell whether two page views came from the same person.
When you book a call
- You can book a call with us through our scheduling provider, Cal.com. It collects your name and email address, your store's website, what you use for search today, how many products you have, any note you add, and the email addresses of guests you invite, and puts the call in our calendar. The call runs on Cal.com's video service.
- We use these details only to prepare for the call and follow up on it.
Cookies and local storage
- The dashboard at app.findlane.dev uses cookies only to keep you signed in. They're essential to the service, so we don't ask for consent to them.
- The dashboard remembers which workspace you last opened in your browser's local storage.
- findlane.dev, the docs, and the playground set no cookies. They keep Yaap's visitor and session IDs in your browser's storage unless you opt out, and remember your choice there (see above).
Why we use it
- To provide the service you signed up for (performance of a contract): accounts, workspaces, indexes, the API, and email about your account.
- To keep the service secure and working (our legitimate interest in running a safe, reliable service): session IP addresses, rate limits, abuse prevention, technical logs, and uptime checks.
- To show stores their search analytics and improve the service (legitimate interest, and on the store's behalf for shoppers' searches).
- To see how many people visit findlane.dev, which pages they read, and where they came from (legitimate interest, which you can object to by opting out): the page views and IDs counted by Yaap.
- To answer you when you write to us or book a call (legitimate interest in answering you, or steps you ask for before a contract).
- To comply with the law (legal obligation).
We don't sell personal data, and we don't use it for advertising.
Who we share it with
We use service providers to host and run Findlane on our behalf, under contracts that require them to protect the data and use it only for us:
- cloud hosting, networking, and security, including the network that serves our website and API around the world, and the AI models that suggest search settings, say why searches found nothing, and build recommendations;
- database hosting;
- email delivery;
- page view statistics for findlane.dev, by Yaap;
- scheduling and video calls, by Cal.com;
- payments and invoices, by our reseller Polar;
- Shopify, for stores that use our Shopify app: the store's plan and overage charges, when it pays through Shopify.
Members of a workspace can see its members, invitations, indexes, and analytics. Its owners can also create API keys that read an index's analytics, such as to show them in the store's own admin: the same totals and lists the dashboard shows, which never name a shopper. We disclose data to authorities only when the law requires it.
International transfers
Some of our providers are based in the United States or operate worldwide. When personal data is processed outside the European Economic Area, we rely on the EU–US Data Privacy Framework for certified providers, or on the European Commission's Standard Contractual Clauses.
How long we keep it
- Account and workspace data: while your account exists, and deleted within 30 days after you ask us to delete your account.
- Sign-in sessions: they expire after 7 days without use.
- Rate-limit records: minutes.
- Search analytics: three months. The daily hashes of visitors' addresses are kept as long, and can't be traced back once that day's random value is deleted, after the next day.
- Events: 13 months, then deleted within a week. The events of a deleted index, and of IDs a store asks us to forget, are deleted within a week.
- Orders kept for products bought together: 400 days, or until the store deletes the index. Orders read from Shopify: also until the store stops sharing them or uninstalls the app. The hash on orders from browsers: two days.
- Technical logs: up to 7 days.
- Connections to AI apps: until you disconnect the app. Access tokens expire after an hour, and refresh tokens after 30 days.
- Call bookings: while we're talking about your move, and deleted when you ask us to.
- Customer content: until the customer deletes it or its account, and then within 30 days.
- A Shopify store's workspace and products: until Shopify asks us to delete them, 48 hours after the app is uninstalled.
Deleted data can remain in backups for a limited time before the backups are replaced.
Your rights
You can ask us to give you a copy of your personal data, correct it, delete it, restrict or object to how we use it, or give it to you in a portable format. Email privacy@findlane.dev, and we'll answer within a month. There's no charge.
If you think we've handled your data wrongly, you can complain to the Icelandic Data Protection Authority (Persónuvernd) or to the data protection authority where you live or work.
Security
We protect data with encryption in transit (HTTPS), encryption at rest by our providers, hashed passwords and API keys, and access limited to the people who run the service. To report a security issue, email privacy@findlane.dev.
Children
Findlane is a service for businesses: you must be at least 18 to create an account, and we don't knowingly collect personal data from children. Searches made on a store that uses Findlane are the store's responsibility, as described above.
Changes
We'll post changes to this policy on this page and update the date at the top. For significant changes, we'll also email account holders before they apply.
Contact
Mucho ehf. (kennitala 460722-0550), Hábæ 2, 851 Hella, Iceland: privacy@findlane.dev