Sign inGet started

Churnly data policy

Last updated 21 November 2026. This is Churnly's own statement of what it collects and what it does not. It is not legal advice. Churnly is run by Churnly. Questions or requests: hello@hichurnly.com. It sits beside our privacy page, terms and subprocessor list.

Who is responsible for what

The short version

What we collect about you, the account owner

What we collect about your customers, and from where

What the AI sees

Drafts are written by Anthropic's Claude models through Anthropic's API. For each task we send only what that task needs: for a save run, the customer's name, email address, WhatsApp or phone number, plan, status, risk reasons, recent signals and up to the last 3 to 10 messages; for a reply, the customer's first name, plan, status and the last 8 messages; for letters, first names and short facts such as what they asked for and when they joined; for reading replies, subject and text; for matching, the notes and the titles and descriptions of what you shipped; plus your name, business name, voice, Sent-folder samples, your last 8 draft edits and style statistics. We never send access tokens or keys. Churnly does not store the prompts; it stores the drafts and run logs that come back. We do not train models on your data, and the Anthropic privacy terms for API use apply on their side. If AI is off or your allowance is used up, built-in templates write and nothing goes to Anthropic.

The AI cannot send anything. Every email, WhatsApp message, coupon, pause and retry waits for your approval. The one exception is auto-send, which is off until you switch it on and covers only plain thank-you replies with no link, price or promise that a second model has checked.

What we do not collect

Cookies and third-party scripts

Churnly sets one cookie that is needed to stay signed in (httpOnly, up to 30 days), and two that last 10 minutes during Google sign-in (a security check and the plan you picked). Two third-party scripts can load inside the app: Cloudflare Turnstile on the sign-in page, and Meta's script only when you connect WhatsApp. The marketing site's content security policy blocks all others.

Why we may process it

Who processes it, and where

Services you connect also receive requests from us: your own mail server (SMTP and IMAP), and GitHub, which gets the repository name and your optional access token. Our hosting is in the United States, so data from elsewhere is transferred there; the data processing agreement covers this. The current list is on the subprocessors page.

How long we keep it

How we protect it

Your rights and how to use them

If something goes wrong

If we learn of a breach affecting your data, we will tell you without undue delay by email so you can meet your own duties to your customers. Report a security problem to hello@hichurnly.com.

Children

Churnly is a business tool. It is not for children and we do not knowingly collect their data.

Changes

We will update this page and its date when what we collect changes, and email you before a material change takes effect.