Kwop › Privacy Policy

Privacy Policy

Last updated: October 4, 2026. This page explains what data Kwop collects about you, what it records on our customers’ websites, which services it relies on, and how to have data deleted.

Kwop (kwop.io) records visits to a website so the owner can watch them back like a video (session replay), and ties each visit to the revenue it brought. This policy has two parts. Part 1 is about you as a visitor of kwop.io or as a Kwop customer. Part 2 is about the data Kwop processes for customers on their own websites.

Part 1: visitors of kwop.io and Kwop customers

Your account

When you create an account, we store your name, your email address and your password. The password is hashed with scrypt and a random salt, so the password itself is never stored. We also keep the address of the site you add, your plan, your language and, if you add one, a profile picture. To understand our own sign-up funnel, we also note where you first came from (the flow_src cookie below), whether you signed up on a phone or a computer, and when you reached the test, plans, checkout and dashboard pages. At sign-up we send a 4-digit code to confirm your email; it expires after 15 minutes. You can change your name, email and password at any time in your settings.

Billing through Whop

Kwop plans are sold through Whop. You enter your payment details on Whop’s checkout, so Kwop never sees your card number. Whop receives the plan you pick, your Kwop account ID and, if a partner referred you, that partner’s Whop username, and tells us when a payment goes through or fails. We keep your plan, billing period, amounts paid and dates. Plans are listed on the pricing page.

Emails we send

We send emails through Resend, and only about your account and plan: the sign-up code, payment confirmations, renewal reminders, failed payments, a plan paused after an unpaid renewal, and the end of a cancelled plan.

Cookies and browser storage

Affiliates who sign in with Whop get a login cookie, flow_aff (90 days), plus short-lived sign-in cookies (flow_invite for 1 hour, flow_oauth_state and flow_oauth_v for 10 minutes). The public demo dashboard sets flow_demo_plan (30 days). Our own tracker (below) also keeps a random visitor ID and session ID in your browser’s local storage, under keys that start with flow_.

How we measure our own site

We run Kwop on kwop.io. Your visit to our pages is recorded the same way Kwop records visits on customer sites (Part 2): pages, clicks, scrolls, mouse moves and the page as a replay, with every typed field masked. If you type your email in our sign-up or log-in form, our tracker can tie it to your visits. While a tab is open, our pages also send a small “still here” signal (a random tab ID, the page path and whether the tab is visible), kept only in memory, so we can see how many people are on the site right now. We also count a few product events, such as an upgrade offer seen or clicked, a plan clicked or our video played, tied to your random visitor ID and, if you are logged in, to your account. Our pages load fonts from Google Fonts. We use no advertising pixels.

The Kwop chat

When you use the Kwop chat in the dashboard, your messages, any images you add and the site data needed to answer (which can include visitor emails and payments) are sent to the AI model provider that runs the chat: Anthropic (Claude), or Google (Gemini) when Claude is not set up. Chats and images are saved in your account so you can come back to them. You can delete any chat.

Test visits

When you paste a link to try Kwop, our automated browser visits that site 3 times and records those visits. These test visitors are not real people: the names and emails shown on them are generated.

Part 2: data Kwop processes on customers’ websites

Customers add one line of code, the Kwop tracker, to their website. For that data, the customer is the controller: they decide to record their site and what to do with the data. Kwop is their processor: we store and analyze it on their behalf, to show it in their dashboard. If you visited a site that uses Kwop and have a question about your data, contact that site first. They can delete your visits from their dashboard, and we will help them answer.

What the tracker records

• Pages: address, page title, the referring page, and the first and last page of the visit.
• Clicks: which element was clicked (a link, a button or anything else) and its visible text, cut to 60 characters. For a text field, only its placeholder or name, never what is typed in it. Fast repeated clicks on one spot are flagged as rage clicks, and clicks on checkout or plan links are noted.
• Scrolling and mouse movement, sampled rather than every pixel.
• The page as a replay: the layout and text shown on screen and how they change, so the visit can be played back like a video. Text displayed on the page, such as a name in an account menu, appears in the replay unless the site masks it.
• Device and browser: desktop, tablet or mobile, and the browser name, read from the browser’s user agent.
• A random visitor ID and session ID, kept in the browser’s local storage. A new session starts after 30 minutes without activity.

What the tracker does not record

• What people type in form fields. The values of every input, text area and dropdown are masked inside the visitor’s browser, so passwords and card numbers typed in the site’s fields never leave the page. (Text typed into an editable area that is not a form field, such as some rich-text editors, is part of the page and shows in the replay unless the site masks it.)
• Masked or blocked parts of a page. Text inside an element with the class flow-mask is masked, and an element with the class flow-block is not recorded at all.
• Canvas drawings.
• IP addresses. They are not saved with visits.

Emails typed in the site’s own forms

One exception to masking: when a visitor types an email address into an email field on the site (for example a sign-up or checkout form), the tracker reads that email so the customer can tie that person’s visits to their payment. Password and hidden fields are never read. A site can turn this off with data-capture-email="off" on the tracker line, or with data-flow-no-capture on a single form. A site can also identify a visitor itself with Flow.identify(), which can include a name.

Consent

A site can add data-consent="required" to the tracker line. Then nothing is recorded until the site calls Flow.consent(), for example when the visitor accepts its cookie banner.

Payments from the customer’s own Stripe, Whop or Shopify

On the Pro plan, a customer can connect their own Stripe, Whop or Shopify account with a key that can read payments. Kwop only reads: it never charges, refunds or changes anything in those accounts. The first sync reads the last 90 days.

• For each paid payment we keep the payer’s email, the amount (for Stripe, minus refunds), the currency, the product and the date. For Whop, also the plan ID; for Shopify, also the order lines. We do not store card numbers or bank details.
• Kwop also reads the account’s products, prices and promo codes, and keeps their price history, to show which plan each visitor picked.
• A payment is linked to a visitor when the emails match. A payment whose email never appeared on the site is kept but not shown, so it can be linked if that person identifies later.
• Connection keys are encrypted at rest (AES-256-GCM). The dashboard only ever shows a short hint of the key.
• When a customer disconnects, the key is deleted and Kwop stops reading new payments. Payments already linked stay in the dashboard.

Visitor scores and follow-up emails

Kwop scores each visitor’s buying intent, explains why they stopped and writes a follow-up email from what they actually did. This runs on Kwop’s own servers, without an outside AI model. Kwop does not email visitors: the customer copies the email and sends it themselves. Kwop notes that a follow-up was copied, to show whether that visitor came back or paid afterwards.

AI assistants connected through MCP

On the Pro plan, a customer can connect Claude, ChatGPT, Gemini or Cursor to Kwop through our MCP server, using a private link from the dashboard’s MCP page (or the token in that link, sent as a Bearer token). Its 9 tools read data, and one of them drafts a follow-up email; none of them sends anything or changes the connected Stripe, Whop or Shopify accounts. What the assistant reads, which can include visitor emails and payments, then goes to the assistant the customer chose, under that provider’s own terms. The customer can regenerate the link at any time, and the old one stops working right away.

Services we use

The database and the replays are stored on servers operated by Kwop, reached only through Cloudflare over HTTPS. We do not sell personal data.

Deleting data

• A visitor: in the dashboard, open the visitor and click Delete. Their visits, replays, clicks, follow-up history and email are erased for good. Their payments are kept as anonymous amounts, with no email and no link to the visitor.
• A connector: disconnect it in the dashboard. The stored key is deleted.
• A Kwop chat: delete it from the chat list.
• Your whole account: email [email protected] from your account’s address and we delete your account and its data.

How long we keep data

We keep account data, recordings and payments while the account is active, and delete them on request. Some things expire on their own: login sessions after 30 days, sign-up codes after 15 minutes, and a visit ends after 30 minutes without activity.

Security

• kwop.io is served over HTTPS, and login cookies are HttpOnly and Secure.
• Passwords are hashed with scrypt and a unique random salt.
• Stripe, Whop and Shopify keys are encrypted at rest with AES-256-GCM.
• Typed fields are masked in the visitor’s browser before anything is sent.
• Changing your password logs out every other session of your account.
• Sign-up, log-in and code attempts are rate limited per IP address. These counters live in memory for a short time and are not saved.

Your choices

You can see and change your account details in your settings, cancel your plan at any time, and ask us about your data or for its deletion by email. If we change this policy, we update the date at the top of this page.

Contact

Questions about privacy at Kwop: [email protected]. You can also read our terms of service and learn about Kwop.