Privacy

This describes what this site does today. It is short because the site does very little.

What this site collects

Nothing. Two pages do take input from you, and none of it reaches us. The TuneUp Score asks eight questions and a little context about your business; the money-flow tool takes a month's figures. Neither one sends what you type anywhere. The working out happens in your browser, the result is drawn on the page you are standing on, and that is the end of it.

Nor is any of it kept. Nothing you enter is written to your browser's storage — no localStorage, no session storage, no cookie — so closing the tab ends it, including a set of answers you had part-finished. And there is nothing at the far end to receive it either: this site has no endpoint that accepts data. /api/lead and /api/scan are reserved names that both answer 501 Not Implemented, and no form on any page posts to them, or anywhere else.

There is no account, no newsletter, and no way to submit anything to us.

The site sets no cookies and runs no analytics — no Google Analytics, no tag manager, no pixel, no session recording, no privacy-friendly alternative to any of those either.

Scripts do run here, and here is each of them. The two tools above are scripts: they are what draws your result, and they run on your own machine. The booking page carries one whose entire purpose is to avoid loading a third party until you ask it to. And every page carries a small one, served from this domain, that unscrambles our email address so that address scrapers get less of it — Cloudflare adds that one as the page is served, not us. You will see it in your network tab, which is why it is named here.

You can verify all of this from your browser's network and storage tools; it is the kind of claim that should be checkable rather than trusted.

The booking page and Calendly

Booking runs on Calendly, which is a third party. It is the only third party this site touches, and the booking page is built so that you choose when that begins.

• The booking page loads nothing third-party until you activate the calendar. Not the Calendly script, not the calendar, nothing.
• Activating it loads Calendly, which loads its own vendors. On page view of the calendar, before you interact with it, Calendly's page loads Google Analytics, Google Tag Manager, Segment, Facebook, Stripe, reCAPTCHA, OneTrust and Airbrake. These run on Calendly's origin inside the calendar frame. We cannot prevent them and we are not going to imply that we can.
• Calendly is told which page you came from, through an embed_domain parameter on the calendar's address.
• All of this is on the booking page before you press the button, not here afterwards.

Cookies set by the calendar — OptanonConsent and __cf_bm — belong to calendly.com. Nothing is set on companytuneup.com.

If you would rather not load it at all, the booking page carries a plain link to Calendly. Following it is the same handoff, made deliberately, and you can see that you have left this site.

If you book, whatever you enter goes to Calendly and then to us as a calendar invitation. That is a booking, not a mailing list.

Hosting

The site is served by Cloudflare Pages. Like any web host, Cloudflare receives the ordinary request data required to serve a page — your IP address, the page requested, your browser's user agent. We do not add anything to that, do not enable Cloudflare's analytics, and do not have a visitor-level view of who reads this site.

Getting in touch

If you email [email protected] or call, we have whatever you chose to tell us, for as long as that correspondence exists. There is no system behind it here.

When this changes

Two of the things this site offers are built and live, and the first section above covers both: the TuneUp Score and the money-flow drawing. Neither collects anything, which is why they add nothing to this page beyond that paragraph.

The external scan and the full TuneUp Report are not built. When either goes live it will collect something, and this page gains a section describing exactly what and for how long — written and published in the same change that makes the capability real, so that this page never describes something that does not exist, and never fails to describe something that does.

Until then, the sections above are the whole of it.