Privacy

What we collect

This is the whole list.

• A scan: the address you typed and the public data our scanner read from it. Every report lives at its own address that cannot be guessed: it opens for whoever has that link, and it is not listed in search engines or anywhere on the site.
• An account: your email, the businesses you added and how you proved each domain, and the wallet address you choose to publish. You sign in with a code we email you, or with a password if you choose to set one on Your account. The password is optional, and our sign-in provider, Supabase, stores it hashed: scrambled one way, so nobody, us included, can read it back.
• What you publish and sign: your list of what you sell, your licences and insurance, your paid links and your gift cards. For a signed document we keep its fingerprint and its name, never the document itself.
• The keys to the tools you connect: the keys and permissions your store, payment, booking and invoicing tools give us. They are sealed, used only for the job you connected them for, never shown back to anyone, you included, and deleted when you disconnect the tool.
• What your orders need: what was bought, what it cost, and the buyer's name, email, phone and delivery address when they gave them. For gift cards and passes, the holder's name and email if you typed them in. For phone notifications, the address your browser gives us to reach that phone. We use it to run your orders and your cards, and nothing else.
• Billing: the fact that you subscribed, your Stripe customer id and your plan. Your card number goes from your browser to Stripe and never touches our servers or our database.
• Product analytics: which pages loaded and which steps of the funnel happened, through PostHog. An approximate location (country, region and city) that PostHog works out from the network address of the request, which it then discards; no street address and no precise location. Outside Quebec, once you sign in, analytics links your visits to your account id, with the first campaign tag and page you arrived on; in Quebec, or when we cannot tell where you are, it does not. On the home page, reports and the Fix pages, we may record how a share of visits move through the page, with everything typed hidden. Not for visitors in Quebec, or when we cannot tell where you are.
• Where a visit came from: when you arrive through a link that carries one of our campaign tags (a letter, a postcard, a partner's code, an ad, a listing), the tag, the partner code, the page you landed on, the name of the site that sent you, and the time. It is kept in two cookies in your browser (see Cookies), copied onto a scan you run from that browser and, if you make an account, onto your account together with the anonymous id our analytics had already given your browser. If you pay, the same tags go with the payment to Stripe. We use it to learn which letters and partners bring people who stay. It holds no name, email or address.
• Your answers on our Fix pages: the six choices you tap about your business, the fixes and the list of what you sell that we prepare from your report and your website while you answer, and the email you leave so they reach you. A random key in a cookie ties them to this browser (see Cookies), and we store only a scrambled form of that key. If no account is made from them, they are deleted 90 days after they were started.
• Requests from machines and AI agents to our MCP server and our paid endpoints: the route, the status of our answer, the kind of client it says it is, the network it came from, the business it asked about, and a key made from the caller's address and browser that changes every day. The address itself is never stored, and once the day is over its key can no longer be recomputed. For a paid call, a fixed key made from the paying wallet's address, so a repeat buyer can be counted; the wallet address itself is not stored. The detail is kept 30 days; after that only daily counts remain.
• Businesses we write to: the business's public contact address, the letters we sent it, and any reply. Our team reads replies in Smartlead and gets an alert on Telegram that names the business and the kind of reply, with no text of the reply. A reply asking us to stop is recorded so that address gets no further letters.
• What you ask our site assistant: the questions you type in its chat window on our public pages, its answers, the page and report they were about, and a random conversation id that lasts as long as the page stays open. The assistant is automated software, not a person. To write each answer, your questions and the facts it answers from are sent to Google's Gemini model through Vercel's AI Gateway. If you ask it to pass a question to a person, the email address you type and your question are kept like anything you write to us. Conversations are deleted after 90 days.
• Anything you write to us.

What we never collect

• Card numbers. Stripe holds those. We hold an identifier that points at a customer record in Stripe.
• The private key to your payout wallet. We could not spend your money if we wanted to, which is the design.
• Anything behind a login on your own site. The scanner reads what an anonymous visitor reads and stops there.
• Advertising identifiers, third-party ad pixels, or anything sold to a data broker. We have none and we will not add one.

Where it lives and who else touches it

These processors, each doing one job. We keep no other copies.

• Supabase, hosting the database and the sign-in system.
• Vercel, hosting the website and its short-lived request logs, and its AI Gateway, which passes the site assistant's questions to Google.
• Google, whose Gemini model writes the site assistant's answers.
• Stripe, taking payments and holding the card details we never see.
• The CRM marketplace you install Orbylon from, if you do, which bills you and tells us when the app is installed, changed or removed, with the business name and website it holds for you, and, when you open the app there, the email address of the person using it, which we use only to send that person a sign-in link they ask for.
• Resend, sending the email we send you.
• PostHog, counting page loads and funnel steps.
• Sentry, receiving a report when something on the site breaks, without your address or cookies.
• Smartlead, sending our letters to businesses and holding their replies.
• Telegram, carrying alerts about those replies to our team's phone.