What we collect, and why

Who is responsible

Cleave, operated by Daniel Frost in Denmark, is the data controller. Contact dannifrost97@gmail.com about this notice or your data.

What we collect

When you reserve or buy, we use:

• your name, email address, and company name if supplied;
• order ID, reservation and payment dates, product, price, and order status;
• source information: an explicit utm_source passed with the order request when present, otherwise the browser-provided referrer (stored up to 200 characters), or site when neither is available;
• your optional answer about where you first found Cleave and a short supporting quote;
• the licensed business, whether another order represents the same or an affiliated company, prior relationship, sales assistance, attribution method, standard-order status, and a broad cohort-fit assessment; and
• payment, refund, chargeback, release, and manual classification facts.

Most of this comes from your form, payment, and email replies. If company independence is genuinely ambiguous, we may make one limited check in a public company registry. We do not use enrichment or profile scraping. This site currently uses no analytics cookies, ad pixels, or third-party tracking scripts.

Why we use it and our lawful bases

Contract: to reserve the product, send the payment link and download, administer the single-business license, and deliver lifetime updates. Legitimate interests: to learn which acquisition experiments produce real independent-business orders, distinguish assisted from self-serve sales, prevent duplicate counting, and keep the founding-price count accurate. This measurement does not decide your price, access, or other rights, and there is no solely automated decision-making.

Where it is stored and who receives it

Transactional order facts are stored in Cloudflare D1. The database currently runs in Cloudflare's Western Europe region, but it is not configured with an EU-only jurisdiction restriction. Cloudflare and its subprocessors may therefore process personal data outside the EEA under its Data Processing Addendum and applicable transfer safeguards. The manual evidence record is kept in one approved, founder-only file outside Git and outside the product package. Payment and email providers receive only what is needed to take payment and fulfil the order. We do not sell the data, publish person-level evidence, or share it for advertising.

How long we keep it

Order and contact details are kept while needed to fulfil the order, administer the license, deliver updates, and meet applicable accounting or legal obligations. Personal evidence used for the 90-day acquisition test is kept through ratification of the final report and only for the short deletion period approved in the private data inventory before collection, then deleted or reduced to non-identifying totals. A released, never-paid reservation is deleted when it is no longer needed for follow-up or a legal obligation.