Cookies

Four cookies, and three of them are mine.

One question, asked once, about counting visits. Then the whole list, checked against what a browser actually receives.

Last updated 25 October 2026

NameWhat it holdsLastsWhy
jt_aidA random identifier. Not your name.Two yearsSo a return visit is recognized as a return rather than counted as a stranger.
jt_gpcA single digit, and nothing else.One yearOnly set if your browser sends Global Privacy Control. It is how the page knows to stay quiet.
jt_consentYour answer to the banner. Yes or no, nothing else.One yearSo the question is asked once, and so the analytics tag knows to stay off.
__cf_bmSet by the booking service, not by me.Half an hourIt tells their bot filter you are a person. Only on the booking page.

Three places remember what you typed

The CRM Score, the quote form and the prompt builder keep answers in this browser. A closed tab does not cost you the work.

It is not a cookie and it is never sent anywhere. It clears when you finish, when you press start again, and after seven days.

That is the entire list, unless you accept

jt_gpc is set only if your browser opts you out. It exists to switch things off rather than on.

No advertising cookies, and no tracking pixel from a social network. Those are not here whatever you answer.

The analytics tool is the one exception, and only if you say yes. It sets its own cookies. They get listed here the day it goes in. Until then this table is the whole of it.

The booking one is the only thing another company sets here. It only happens if you open the booking page. It is a bot filter, not a tracker.

This list used to say one cookie. A browser check on 20 September 2026 found the booking page setting a second one.

How to refuse it

Turn on Global Privacy Control in your browser. When that signal is present the cookie is never set. The visit is counted without anything that could identify you.

Blocking cookies in your browser settings also works. Nothing on this site breaks without it.

Why the identifier is set without asking

jt_aid is a first party cookie. It holds no personal detail and is never shared. Under California law that is an opt out rather than an opt in. The browser signal is the opt out.

Why there is a banner now

This page used to say a banner would be theater. Nothing here needed one at the time. That has changed.

I am adding an analytics tool, to see which pages help. Somebody else makes it, and it runs in your browser. The old wording promised a real question before anything like that. Here it is, asked once.

It stays off until you say yes. Saying no is one click. It is the same size as yes, in the same place. Nothing here works differently afterwards.

What is never here

No advertising tag, of any kind, whether you accept or refuse. There are no paid ads until this business is profitable. The build refuses one if anybody adds it.

If your browser sends Global Privacy Control, you see no banner at all. That signal is already an answer, and I treat it as one.