Privacy Policy

Account data. Your name and email address, and the organisation you belong to, held by our sign-in provider (Clerk). If you sign in with a third-party identity provider, we receive the name and email that provider shares.

Content you enter. Rosters, creator records (handles, audience and engagement figures, niche, scores), campaign briefs, results, notes, and a team logo if you upload one. Creator records can be personal data about people who are not our users; you are responsible for being entitled to hold that information.

Usage data. Which plan you are on, how many valuations you have run against your plan’s limits, and standard server logs (IP address, browser, pages requested, timestamps) kept for security and troubleshooting.

Payment data. Paid plans are billed through Stripe, which holds your card details and billing address; we hold only a customer reference, your billing currency and the state of your subscription. We never see full card numbers.

Acceptance records. When you accept our Terms of Service, we record the version, the language, the time, your IP address and your browser, so we can show what was agreed and when.

To run the Service for you and your team: sign you in, price what you enter, remember creators you have priced before, keep campaign history, produce reports, enforce plan limits, and bill you. To keep the Service secure and working. To answer your messages. We do not sell personal data, do not show advertising, and do not use your content to train generative AI models.

We also use aggregated, de-identified figures drawn from use of the Service (for example, ranges of rates and outcomes across many valuations) to calibrate and improve our pricing model and benchmarks. These figures do not identify you, your organisation, your clients or any creator, and we never disclose your content to other customers.

Providers who process data on our behalf, each under their own security commitments: Clerk (authentication and organisations), Railway (application hosting and the database), Cloudflare (DNS and the redirect on our bare domain), and Stripe (payments, tax calculation and invoicing). Team members you invite can see the rosters, campaigns and creator records saved under your organisation. We disclose data otherwise only if the law requires it.

The Service sets the session cookies needed to keep you signed in, and nothing else. There are no advertising or cross-site tracking cookies.

Data is stored on servers operated by the providers above, several of which are located in the United States, so your information may be stored and processed outside Québec and Canada and be subject to the laws there. Before transferring personal information outside Québec we assess whether it will be adequately protected. We keep your content while your organisation has an account. When an account or organisation is closed, we delete its content within thirty days, except where a copy has to be kept for legal or accounting reasons. Server logs are kept for a short rolling period.

You can view and edit your content in the app at any time, remove creator records you have saved, and delete campaigns. To export or delete everything, to correct something we hold about you, or to ask what we hold, email ash@clearingrate.com from the address on your account and we will act within thirty days. Depending on where you live, you may have further rights under local data-protection law, and the right to complain to a supervisory authority.

Under Québec’s Act respecting the protection of personal information in the private sector, the person in charge of the protection of personal information at 9576-8958 Québec Inc., operating as Clearing Rate is Ash Molaei, who can be reached at ash@clearingrate.com or 16 rue Cambridge, Hudson, Québec J0P 1H0, Canada. You may also contact the Commission d’accès à l’information du Québec or, outside Québec, the Office of the Privacy Commissioner of Canada.

Connections are encrypted in transit, sign-in is handled by a dedicated provider, data is isolated by organisation on every request, and only people who need production access have it. No system is perfectly secure; if we learn of a breach affecting your data we will tell you without undue delay.

We will update this policy as the Service changes. The effective date above shows the current version; for a material change we will also tell you by email or in the app.