Findwise Privacy Policy

Last updated November 12, 2026 · Version privacy-2026-11-12-v0.30

This policy explains what Findwise LLC ("Findwise," "we," "us") collects when you use getfindwise.com, scan a store, open or buy a report, confirm your email address or find a report you bought, create an account or sign in, ask for a free report through one of our forms on Facebook or Instagram, or write to us, what we do with it, and the choices you have. We have kept it short and plain on purpose: it describes what the product actually does.

Questions or requests: privacy@getfindwise.com.

1. Who this is for

Findwise is a business tool. It checks how well an online store's public pages answer the questions shoppers and AI shopping assistants ask. It is not meant for children, and it is not used to make decisions about individual people.

2. What we collect

When you use the site

  • The store address you submit for a scan. For membership we also keep the site your account tracks, your trial and subscription status, assessment history, weekly-email preference, delivery records, and when you last used your account.
  • First-party membership activity: account and report visits, comparisons opened, trial and subscription changes, monitoring pauses and resumptions, and assessment outcomes. These records use your internal account identifier to understand return use, whether later assessments confirm a fix, and the cost and reliability of the service. They are not advertising permission; refusing advertising measurement does not authorize sending this activity to an advertising provider.
  • If you choose Light or Dark, a functional cookie remembers that appearance preference in this browser for up to one year. Until you choose, the site follows your device's appearance setting without saving a preference. We use this preference only to display the site as you chose, not for analytics or advertising.
  • If you request a preview, report or product-availability notification: the email address you provide, what you requested, your marketing choice, and records of those communications. We use this information to provide the requested information and access to your reports, and keep the request as a lead record. Marketing is optional: we use your address for product updates only if you separately agree, and marketing consent is never required to open a preview.
  • If you ask us to find a report you bought: the email address you enter. We email that address a one-time code, within limits on how often we send them, whether or not a report was bought with it, so the page never shows anyone which addresses bought. We do not store the address itself: we keep only a one-way, salted code made from it, the same kind a paid order keeps, so that once you type the code back we can show you the reports bought with that address. We keep the one-time code only as a one-way code, with when it was sent and whether and when it was used, and we keep a count of how many codes we have sent recently to that address, under the same one-way code, and to its email domain. It is not a lead record and is never used for marketing. While the code is valid, one cookie ties it to the browser that asked for it; it expires after a few minutes, cannot be read by page scripts, and does not contain your email address.
  • If you choose to confirm your email address before you pay: the address you enter. We email it a one-time code, under the same limits and kept the same way as above. Once you type the code back, we give the address to Stripe to fill in on its payment page. We do not keep the address ourselves; your order keeps only the one-way code of the address Stripe reports when you pay, as for any order.
  • If you create an account or sign in: the email address you enter. We email it a one-time code, under the same limits and kept the same way as above, and once you type the code back you are signed in. Unlike finding a report or confirming your email before you pay, an account keeps your email address itself, so that we can write to it about your account: we keep the address you confirmed, the same one-way code made from it, when the account was created, and which versions of our Terms and this policy you accepted. For each sign-in we keep when it started, when it was last used and when it ends. One cookie, __Host-fw_login, keeps you signed in for up to 30 days; it cannot be read by page scripts and does not contain your email address. Orders you start while signed in record your account, and we give your account's address to Stripe to fill in on its payment page. The first time you sign in, paid orders bought with the same address since 2 October 2026 are matched to your account by the one-way code. Whoever controls the email address controls the account, and so does whoever controls a Google account added to it. When a new sign-in happens while another is active, or Google sign-in is added to or removed from your account, we email the account's address a short notice with no link. You can see the Google sign-in on your account page and remove it after confirming with a code. It is not a lead record and is never used for marketing.
  • If you sign in with Google: Google gives us an identifier for your Google account, the email address it holds for you, and whether Google says it has confirmed that address; we keep these with your account, with when you first and last signed in that way. We do not ask Google for your name, your profile or anything else in your Google account. When Google cannot vouch for the address, we ask you to confirm it with a one-time code before we add the Google sign-in to an account. While you sign in, one cookie ties the attempt to your browser for a few minutes; it cannot be read by page scripts and does not contain your email address. We never receive your Google password, and we keep no access to your Google account.
  • If you write to us or buy something: your name, email address, phone number if you give one, company, your messages, and what you bought. Card payments are handled by our payment provider, Stripe; we never see or store your card number.

When you ask for a free report on Facebook or Instagram

  • If you fill in one of our forms on Facebook or Instagram: your name, email address and website, and your answer to the form's consent checkbox, with when you sent it and which version of the form's wording you saw. Meta, which runs the form, passes us what you entered, together with which of our pages, forms and ads it came from. We keep it as a lead record and use it to make the free report on the store you named, with the same free scan our site runs, and to send you that report, as you asked. A person on our team writes and sends that email. Its link opens your report without asking for your email again for 30 days from when we prepare the link; after that, the report asks for an email again. Filling in the form sends you nothing automatically and does not sign you up for product updates or any other email.
  • We take the store only from your answer to the website question, never from your email address. If you do not tick the consent box, we scan nothing and send you nothing, and discard your name, email and website answer. If you give no website or one we cannot scan, we scan nothing, and a person on our team may write to you once to ask which store you meant. If the scan cannot make a report on the store you named, a person on our team may write to tell you.

When we scan a store

A scan reads a limited number of a store's public web pages, the way a search engine does, following the rules in our crawl policy at getfindwise.com/bot. We keep what is needed to build the report: page addresses, public page content and markup, product and policy details, and technical facts such as status codes and robots.txt rules. We never log in, add to cart, check out, or get around a block.

Public pages sometimes contain personal details a business chose to publish, such as a founder's name or a reviewer's first name. We use them only as part of the store's report and, where a business publishes a contact address, to offer it a report about its own store; we never build profiles of people.

We also scan stores we choose ourselves, to improve our checks and to offer store owners a report.

Automatically

  • Basic technical data such as IP address, browser, pages viewed, and the page that sent you, used to run and protect the site and to stop abuse.
  • When you start a scan on our site and it is stored as a new scan: a one-way, salted code made from your IP address, when one is available, kept as the record that you accepted our terms. The record holds the code, not your address, and we do not use the code to find out who you are. If the same store was scanned recently, you are shown that earlier scan instead, and we keep no new record of your acceptance. A paid order keeps the same kind of code, when one is available, made from the buyer's email address when Stripe provides one. When the order was started while signed in, or is later matched to an account, it also records that account.
  • One essential cookie when you open a scan or private preview: fw_checkout_intent. It holds a random code for up to 36 minutes so repeated purchase clicks can return to the same checkout. It also prevents repeat counts when a private preview reloads. It cannot be read by page scripts, contains no email address, and is not sent to advertising services.
  • One cookie when you open a scan report. It records that that one report was unlocked, expires after 30 days, cannot be read by page scripts, and does not contain your email address.
  • First-party analytics cookies on public and private customer pages: fw_browser holds a random browser code for up to 180 days; fw_session holds a random session code for 30 minutes without a visit; and fw_campaign remembers for the same 30 minutes which of our emails or ads brought you here, as a code that is the same for everyone who followed that link. Each visit restarts these periods. When valid Google Analytics identifiers already exist, we keep that identity; otherwise we create random codes. These cookies contain no email, store identifier, private URL or report token. They let a visit that began at one of our emails or ads, or a direct private-preview visit, be counted in the same journey as the scan, checkout and payment that follow, including when the visitor later opens a public page. They are analytics cookies, are not sent to Meta, and operate independently of advertising permission. When you start a new scan, we also keep the approved campaign code with the scan for as long as the scan is kept, even if you decline marketing cookies. This code is the same for everyone who followed that campaign; it identifies no individual ad click and is never sent to Meta.
  • Analytics from Google. Eligible public pages may set first-party Google Analytics and Google Tag Manager cookies. Our servers may also send events through the Measurement Protocol with pseudonymous client and session identifiers when a scan is accepted, completes with a usable report or fails; when an email address is accepted at a preview or notify form; when a valid free report or current outreach preview is first opened; when checkout begins; and when a purchase settles. They may include only an approved campaign source, medium and name that is the same for everyone who followed the same email batch or ad, where your first visit came from (described below, and only while we keep that record), general scan outcome and timing categories, the kind of form or report, and what was bought; a checkout event may include the price and currency, and a purchase may also include the order value, currency and an order reference. After you allow Google advertising, they may also include the bounded Google campaign and ad codes described below. When checkout begins, we may also store the same client and session identifiers, that approved campaign code and where your first visit came from with the Stripe checkout session so the purchase can be measured when it settles. For scan completion or failure and the first free or outreach-preview open, we use a delivery record keyed by a one-way code made from the event, scan, and pseudonymous client and session identifiers, and send that same code with the event. This helps avoid repeat sends during one visit. If Google's response is missing or the delivery record cannot be finalized, we may retry up to twice, so Google can receive a duplicate. They never include your name or email address, the store URL or domain, the report link, or raw error details. Public page views use the public page path, pseudonymous client and session identifiers and approved campaign codes shared by a whole campaign, with query strings, fragments and referrers removed. Google Tag Manager does not load on /internal, /checkout, /billing, or on /scan, /report or /purchase pages that identify a scan, a report or an order, or on our sign-in, verification and account pages.
  • Session recording and heatmaps from Microsoft Clarity, under the same choice as Meta advertising measurement: in a known United States state outside California it is on unless you opt out; in California, in a United States visit whose state we cannot determine, and everywhere outside the United States it is off unless you allow it; a Global Privacy Control signal turns it off everywhere. On our public pages and the pages that show a free scan, Clarity records how the page is used: what the page shows, including a scanned store's address and results; clicks, taps, scrolling and mouse movement; the page address, including any campaign tags in it, and the page that sent you; screen size, performance and script errors; and general browser, device and network details, from which it estimates an approximate location. It never receives what you type into a form field or pick from a list. It does not run on report links, checkout, purchase or billing pages, or our internal pages, or on our sign-in, verification and account pages, and card details are typed only on Stripe's own pages, which it cannot see. We do not give Clarity a Findwise user identifier or ask it to match you to a customer. Clarity sets pseudonymous cookies that link the pages of a visit and your return visits for up to a year. Microsoft receives this data as an independent business, not on our behalf, and may use it for its own purposes, including improving its products and Microsoft Advertising, as the Microsoft Privacy Statement describes: https://privacy.microsoft.com/en-us/privacystatement. Microsoft keeps ordinary playback data for 30 days; click and heatmap data, favorited recordings and a small retained sample can be kept for up to nine months.
  • Google advertising measurement, only if you allow marketing cookies and do not send Global Privacy Control. When you arrive from an approved Google ad, Google and Findwise may keep Google's click identifier, the fixed campaign code, numeric ad-group and creative codes, one of the eight search phrases configured for this campaign, and closed match-type, device and network codes so an opened free report can be attributed to that ad. Findwise accepts only those bounded values from the page address and keeps them in a first-party HttpOnly cookie for up to 30 minutes. If that visit creates a new scan, Findwise also keeps an opaque, signed, scan-specific proof for up to 30 minutes; visitors shown a cached or deduplicated scan do not receive it. After you allow measurement, the browser may send Google one reconstructed public landing address containing only Google's click identifier, together with the bounded campaign and ad codes described above and pseudonymous client and session identifiers. The server later sends the allowed ad codes, but not that click identifier, with the qualified report-open event only when the signed fresh-scan proof and your current saved permission both verify. Our server checks your current saved permission before sending the qualified event. These values are not put in a report link, email address, store address, customer-visible copy, Stripe record or Meta event. Refusing or withdrawing permission prevents future sends and clears Findwise's advertising cookie; it cannot remove an event already received.
  • One cookie if you answer the cookie choices banner or your browser sends Global Privacy Control on our public and private customer pages: fw_ad_consent. It holds your allow/refuse answer or records a Global Privacy Control refusal, including while that refusal is waiting for our server to save it, and expires after 180 days. It changes nothing about Google Analytics, which runs either way. When you accept where we ask first, a second cookie, fw_consent_scope, records for the same 180 days that your answer covered session recording, so an answer given before session recording was part of this choice never turns it on; refusing deletes it.
  • A separate essential cookie, fw_ad_consent_ref, when you answer the banner or Global Privacy Control needs to save a refusal, and from the first visit in a known United States state outside California, so that an opt-out has somewhere to be recorded. It holds a random code that our servers use to check your current advertising permission, expires after 180 days, and cannot be read by page scripts. Our database stores the code, whether you allowed or refused advertising measurement or sent Global Privacy Control, and when that choice was made and expires. The code is not sent to Google, Meta or Stripe as a measurement identity; it can accompany checkout metadata at Stripe so we can check your current choice if payment confirms later. In the United States one more essential cookie remembers for up to 180 days the choice our server last read for your browser, so that choice holds even if your browser removes other cookies sooner; it holds only that choice.
  • Advertising measurement from Meta. In a known United States state outside California, it is on unless you opt out. In California, in a United States visit whose state we cannot determine, and everywhere outside the United States, we ask first and it is off unless you allow it. A Global Privacy Control signal turns it off everywhere. Once it is on, our servers can establish the random _fbp matching cookie on private customer pages without loading Google or Meta scripts there. A Pixel on eligible public pages receives a fixed public-page address, your browser details and network address, and a random Meta browser code in the first-party _fbp cookie, which lasts up to 90 days. It receives no private-page address or referrer. Our servers can also send successful account creation and sign-in, store enrollment, trial start, customer-requested assessment start and completion, eligible report views, subscription checkout, paid subscription activation and confirmed payment events, as well as accepted and completed scan, accepted lead, eligible free or outreach-preview view, checkout and confirmed purchase events, with that Meta browser code, your browser user agent, a fixed public homepage address and a one-way event reference. Checkout, paid subscription and purchase events can include the product type, price and currency. A no-card trial is not a purchase. We may associate the permitted Meta browser code, browser user agent and advertising-permission reference with your account for up to 30 days to measure a later completed assessment or subscription payment. Each delayed send still checks the current choice for that reference. Signing in with an identity provider never grants advertising permission, and we do not use the identity provider’s account identifier or email address for advertising measurement. They never include your email address, name, store URL or domain, private report link, raw order code or payment details. A check of your current choice precedes every server send: a refusal or opt-out, Global Privacy Control or a choice we cannot read prevents it, and where we ask first so does having no current permission. Rejecting or opting out disables Meta in that browser immediately. We mark the withdrawal pending while our server saves it, retry temporary failures automatically, and show it as saved only after acknowledgment. Once saved, it applies to future server sends, including delayed payments; it cannot remove an event Meta already received.
  • Where your first visit came from, in all of the United States unless you opt out, and everywhere else only if you allow advertising measurement: one cookie remembers which ad, email or tagged link brought your browser here the first time we could record it, whether that was an ad click, the page it landed on and when, so we can tell which of our ads and emails lead to scans and purchases. It lasts 90 days from that visit. It never holds your email address, your name, a store or a private page's address, and it is never sent to Meta. Opting out, refusing or a Global Privacy Control signal deletes it. When that visit starts a new scan, its campaign codes, which are the same for everyone who followed the same ad or email, are kept with the scan for as long as the scan is kept.

3. How we use it

  • To run scans, build and deliver reports, and take payment. For membership, to schedule recurring assessments, preserve your history and report access, administer the trial and subscription, and send weekly assessment emails only when you choose them. We also send service notices about an upcoming inactivity pause.
  • To reply when you write to us.
  • To remember and apply the appearance you choose.
  • To deliver the previews, reports, access links and availability notifications you request, and to respond to your messages. We send product updates only when you agree to marketing email.
  • To confirm you control the email address you give us, to fill it in on Stripe's payment page when you confirm it before paying, and to show you the reports bought with that address.
  • To keep your account secure, to let you sign in with Google, to show you your own purchases, and to tell you about new sign-ins.
  • To contact a business about a report on its own public store, and to honour any request not to be contacted again.
  • To understand which pages work, to measure which of our emails and ads lead to scans and purchases, to measure cost and quality, and to improve our checks. We use first-party membership activity to measure returning use and subscription conversion; background scans and email-open pixels do not count as returning use. Internal team-chat summaries contain aggregate membership statistics and coarse service events, not private report links or customer email addresses.
  • To keep the site secure and stop abuse.

Reports are produced by automated checks. An optional AI step tags what kind of site was scanned and what it sells; it does not write any of the report. A weekly email may also use AI to explain supplied assessment facts, with a template if generation is unavailable. Scores, changes and the next priority remain determined by code. These email explanations receive bounded report facts, not account addresses or private access links. AI processing runs on Cloudflare Workers AI, inside the same Cloudflare account that hosts Findwise. We do not send your information to any other AI provider, we do not let any provider train its models on it, and we do not use paid reports to train models.

4. Who we share it with

We do not sell personal information for money. We share it with service providers that help us run Findwise, for the purposes described above, and with Microsoft for session recording as section 2 describes. These are the kinds of service, with examples; the examples are not a complete list:

  • Hosting, storage, security, site analytics and AI processing, for example Cloudflare.
  • Payments: Stripe handles checkout and keeps with it the analytics client and session identifiers, approved campaign code, where your first visit came from, advertising permission details and browser information needed to measure a payment when it confirms.
  • Email delivery, for the email we owe you, when email delivery is on.
  • Analytics and advertising measurement: Google for site analytics and, only after you allow it, Google advertising measurement; Meta as section 2 describes, including its forms on Facebook and Instagram and the answers it passes us.
  • Session recording and heatmaps: Microsoft Clarity, under the choice described in section 2. Microsoft receives this data as an independent business and may use it for its own purposes, including advertising.
  • Identity providers you choose to sign in with, for example Google: they learn that you chose to sign in to Findwise with your account with them, and they give us an account identifier and an email address.
  • The internal tools our team uses to work, for example business email and team chat, which can hold the messages you send us and our notes on your use of Findwise, such as your name, an email address you entered and the store you asked us to scan, and the report email our team writes and sends.

We also share information when the law requires it, to protect Findwise or others from fraud or abuse, or with a buyer if Findwise is ever sold. If we start sharing personal information with a new kind of recipient, we update this policy first.

Some US state laws treat advertising measurement with Google or Meta, and session recording with Microsoft Clarity, as "selling" or "sharing" personal information. Google advertising measurement runs only if you say yes. In a known United States state outside California, Meta and Clarity run after notice unless you opt out; in California, in a United States visit whose state we cannot determine, and everywhere outside the United States, they run only if you allow them. A Global Privacy Control signal counts as opting out or refusing.

5. Reports

Report links are long and unguessable, and report pages are kept out of search engines. We treat paid reports as private to the buyer. We do not publish a report about a named store, or use a customer's name or logo, without permission.

6. How long we keep things

  • Raw copies of scanned pages: up to 180 days for every scan, including free scans, paid rescans and scans we start ourselves.
  • Reports, scores and the evidence behind them: for as long as the report is offered, so it can still be opened and compared with a later scan.
  • Leads, purchases and messages: as long as they are useful to run the business, or longer where tax or accounting rules require it. A request from one of our forms on Facebook or Instagram is a lead, and is kept with the consent it records. When we close that request, we remove its personal answers and report and draft links from our lead record, keeping only the source identifiers, times and consent record needed to recognize repeat deliveries and explain what happened. Copies in the form provider, our team chat or sent email are handled separately when you ask us to delete them.
  • Records that an analytics event was sent to Google (the one-way code described in section 2, which scan and event it was about, when it was tried, whether it was delivered, how many attempts it took and any error): as long as they help avoid repeat sends, with the retries described in section 2.
  • Significant-event delivery records and their account-linked advertising association: up to 30 days. Delivery records use one-way event references and fixed activity labels; they do not contain email addresses, store addresses, private links or conversation text. We clear account-linked advertising information when the account is deleted. Operational messages to our team chat contain fixed milestone labels, the web address of the store the account added, service counts and payment amounts, without email addresses or account identifiers.
  • Current advertising permission: the choice expires after 180 days; we periodically remove expired permission records.
  • Records of Meta milestone delivery: one-way event references, the scan and event involved, attempt times and coarse outcomes; records older than 180 days are eligible for periodic removal. They hold no email or browser user agent.
  • Microsoft Clarity session playback, kept by Microsoft: 30 days. Click and heatmap data, favorited recordings and a small retained sample: up to nine months.
  • One-time codes for confirming your email address or finding a report you bought, and the counts that limit how often we send them: a code stops working minutes after we send it, and a regular clean-up deletes these records once they have expired.
  • The short records of a sign-in started with Google: they stop working minutes after the sign-in starts, and the same regular clean-up deletes them once they have expired.
  • Membership history, preferences and first-party activity: while your account is offered, to provide historical comparisons and measure returning use. Deleting the account ends monitoring and weekly emails and removes account-linked activity and report attachments, subject to payment record retention.
  • Accounts: until you ask us to delete them; deleting one signs it out everywhere and removes its email address and its Google sign-in, and your orders keep only a bare account number for our books.
  • Sign-ins: up to 30 days, then deleted by a regular clean-up.
  • Do-not-contact records: as long as needed to honour them.

7. Your choices

  • Enable or disable weekly assessment emails from your account or unsubscribe from an email. This does not end monitoring or your account.
  • Ask to see, correct or delete your information, or to stop marketing email: write to privacy@getfindwise.com. We may need to check it is really you.
  • Block or delete cookies in your browser. The report cookie, or signing in to your account, is needed to reopen a report on that device.
  • Choose at any time whether Meta advertising measurement, Microsoft Clarity session recording and their cookies, including the one that remembers where your first visit came from, run in your browser, with the link at the foot of public and private customer pages: Your privacy choices in the United States, Cookie choices everywhere else. In a known United States state outside California they are on unless you opt out. In California or a United States visit whose state we cannot determine, the cookie that remembers where your first visit came from is on unless you opt out, while Meta and Clarity are off until you allow them. Everywhere outside the United States they are off until you allow them. An opt-out lasts 180 days in that browser, and a Global Privacy Control signal from your browser counts as opting out. Opting out or refusing also ends a Clarity recording already running on that page and removes its cookies from our site; it cannot remove what Microsoft has already received.
  • Google advertising attribution is always off until you allow it. Refusing it or sending a Global Privacy Control signal keeps it off and deletes Findwise's Google advertising cookie.
  • You can also remove Findwise's access in your Google account settings.
  • Browsers' Do Not Track signals have no common standard, so we do not respond to them; we do honour Global Privacy Control as described above.
  • Store owners can ask us to limit or stop scanning their site, correct or remove a report, or not contact them again, at legal@getfindwise.com.

We will not treat you differently for using any of these choices.

8. Security

We use reasonable safeguards such as encrypted connections, access controls and rate limits. No system is perfectly secure. Findwise never asks for your store's passwords or admin access.

9. Outside the United States

Findwise is run from the United States, and information is processed there and wherever our service providers operate. If you need something specific for your country, write to us.

10. Changes

When what we do changes, we update this page first, change the date and version above, and, for a significant change, say so on the site. We will not start using information in a new way that this page does not describe.

11. Contact

Findwise LLC

Privacy requests: privacy@getfindwise.com

Store owners and legal notices: legal@getfindwise.com

Mailing address: Available upon request, or as listed in formal customer order documents.