Cookies are small files a website stores on your device. We use very few of them, and none that build advertising profiles. When you first arrive we ask which you are happy with; essential ones cannot be switched off, everything else is off until you say otherwise.
| Cookie | Type | Purpose | Expires |
|---|---|---|---|
| cl_consent | Essential | Remembers the choice you made in the cookie banner so we do not ask again | 12 months |
| Cal.com booking cookies | Essential to the booking | Set on cal.com and app.cal.com, and only on the Book a call page, so the calendar you are using can keep its place. Not set anywhere else on this site | Cal.com’s own periods |
| cl_sess | Essential | Keeps you signed in to the client, practice, staff or payment pages once you have signed in. Not set by the public pages | 24 hours, or 30 days if you tick "remember me" |
| cl_setup | Essential | Carries you from an activation code to choosing a password | 15 minutes |
| _ga, _ga_* (Google Analytics) | Optional | Which pages are read and where visitors arrive from, in aggregate, and which steps of getting started are completed. Analytics only: advertising storage is declared off. Never runs on the pages where you upload a ledger or sign in. Set only if you turn analytics on in the banner or in Cookie settings | Up to 13 months |
| Advertising (_fbp, _gcl_*, and the signals Google Consent Mode carries) | Optional | Lets the advertising platforms we use (Google, Meta) see that a visit or a sign-up came from one of our adverts, so we know which adverts work. Set only if you turn advertising on; off, those platforms are told nothing (Consent Mode denied). Never runs on the pages where you upload a ledger or sign in | Up to 90 days (Meta), 90 days (Google click id) |
| Analytics (aggregated) | Optional | Which parts of a page are read, with typed input masked (Microsoft Clarity, when in use). No cross-site tracking and no advertising use. Never runs on the pages where you upload a ledger or sign in. Set only if you turn analytics on | Up to 12 months |
| Browser storage (not a cookie) | Essential | The public pages keep a note of a scan in progress and a form draft in your browser's own storage. Nothing is sent anywhere | Until you clear it |
Strictly necessary cookies keep the site working and need no consent, which is why the banner does not ask about them. Optional analytics and advertising cookies are set only if you turn them on, and you can change your mind at any time from the Cookie settings link in the footer of every page, or the button below. Declining optional cookies does not restrict any part of this site, including the scan tool and the calculator.
Advertising or retargeting cookies, social media tracking pixels, or any cookie that follows you across other websites. If that changes, this page will change with it and we will ask for your consent again.
Some pages load fonts and, where present, embedded video from third parties, which may set their own cookies or log your IP address. We keep these to a minimum and list our providers in our processor register, available on request.
One page loads more than that. Book a call shows a booking calendar provided by Cal.com, which loads a script and a frame from cal.com and app.cal.com and sets cookies on their domains so the calendar can remember where you are in the booking. That is the service you came to the page to use, so it loads with the page rather than waiting for a consent choice, and it appears nowhere else on this site. What you type into it reaches Cal.com and then us when you confirm the booking; nothing about it is analytics and none of it follows you to other sites. If the calendar is blocked on your network, the page offers you a direct link and an email address instead, and neither loads anything.
Every browser lets you block or delete cookies in its settings. Doing so for all sites may affect how other websites work. Questions: privacy@clearline.co.uk.
Two optional categories, each only if you agree, each with its own switch. The banner's Accept all and Reject all do the same job in one click; neither is harder than the other.
Advertising measurement tells Google and Meta that a visit or a sign-up came from one of our adverts, so we can see which adverts work and stop paying for the ones that do not. Meta is told about a few steps only: a free report released, each stage of getting started, a call booked, a checkout started and a subscription bought. Our server sends Meta the same events (Meta's Conversions API) with your IP address and browser so they are not lost to ad blockers, and on a purchase the plan, its price and your email address hashed one way, never the address itself. With advertising off, Google's Consent Mode carries a "denied" signal, the Meta pixel does not load, our server sends Meta nothing, and no advertising cookie is set.
Google Analytics, loaded through Google Tag Manager, counts which pages are read, where visitors arrive from and which steps of getting started are completed, in aggregate, with IP addresses anonymised. We tell Google it may use it for analytics only: no advertising storage, no advertising personalisation, no cross-site profile.
Microsoft Clarity shows us which parts of a page people read and where they get stuck. It records how the page is used, not who you are.
Our own counter records which steps of the free scan people complete, so we can see where the tool is confusing. It stays in your browser and is never sent anywhere.
None of them runs on the pages that matter most. The ledger scan, the client portal, the payment page and the debtor pages carry no third-party analytics at all, because those screens show real invoices and real customer names belonging to people who never agreed to anything. Excluding them entirely is simpler and safer than trying to hide parts of the screen.
One thing we do count ourselves. On the public pages, including the scan, our own server counts how many people reach each step: a visit, the calculator, a scan, the report, each stage of getting started. It receives the name of the step, the page, the site you arrived from and nothing else — never anything from a ledger, never your email, and nothing is placed on your device to do it: not a cookie, not a local file, not an identifier. The count is grouped by connection for a single day and cannot be turned back into a person or followed to the next day. It is kept for six months and is not shared with anyone. It does not run on the payment or debtor pages, or once you have signed in.
Changed your mind? and you will be asked again.