Privacy

Written from what the code does, not from a policy template. The tools run in your browser and this site has no application server of its own. What follows keeps apart things that are easy to run together: what this site never asks you for, what it records when you use a tool, what may leave the page for Google, and what any web page unavoidably reveals to the machines that serve it.

Who runs this

Is It a Good Fit? is an independently operated decision-tool website. Privacy questions can be sent to [email protected].

What this site does not ask you for

• No account, no email, no sign-in. There is nothing to register for and nowhere to register it. The site is a set of static files: no code of ours runs on a server, and there is no database behind it.
• No name, no contact details. No question in any tool asks for your name, your address or a way to reach you, and no field collects one.
• Your specific answer values are not transmitted. A tool reads your answers, applies its published rules and renders a result, all inside the page you already have open. No hours, no counts, no selections and no free text are sent anywhere.

That is a statement about what is asked for and sent, and it is deliberately not the larger claim that nothing identifying is involved anywhere. Serving a page and measuring its use both involve other computers, and the sections below set out what reaches them.

What is recorded when you use a tool

Seven events are defined. None of them carries an answer value. What they carry is which tool was used, the name of a question that was answered, and the category of result the tool reached.

• tool_view — a tool page was opened. Carries: tool
• tool_start — you touched the first field. Carries: tool
• tool_answer — you answered one question. Carries: tool, the question's name. Never its value.
• tool_complete — you submitted the form. Carries: tool, result category, the plan named, any alternative plan, whether the result was "no plan fits"
• recommendation_shown — the result was displayed. Same fields as above.
• amazon_cta_impression — a sign-up link was actually on screen (half of it visible, not merely present in the page). Carries: tool, result category
• amazon_cta_click — you clicked a sign-up link. Carries: tool, result category, the plan named

Each event also carries the time it fired and the path of the page it fired on — the path only, never the query string or the fragment.

The part worth being precise about

"No answer values" is true, but it is not the whole picture, and a policy that stopped there would be misleading. The result category and the plan named are calculated from your answers. Recording them records a coarse summary of what you answered — a reading membership being recommended already says something about how much you read, even though your figure for it was never transmitted.

What Google receives

When the analytics script runs, Google receives each event listed above: its name, the properties recorded beside it, the time it fired, and the path of the page. It also receives what any request to any server carries — your IP address, and the details your browser volunteers.

It does not receive your answers. How many hours you listen, how many books you read, what you pay, which option you picked — none of that is transmitted, under any field name, in any form. What leaves the page about your answers is the name of the question you answered, and at the end the category of result the tool reached. As the section above says, that category is a coarse summary of what you answered, and it is the most that leaves.

The property is set up not to use this data for advertising. Advertising personalization is off, Google Signals is off, the property is not linked to a Google Ads account, remarketing is off, and no User-ID is sent — this site has no way to know who you are, and does not try to find out. Event data is kept for 14 months.

Google's own account of what it does with data from sites that use its services is at How Google uses information from sites or apps that use our services.

What your browser may keep

This site keeps nothing between visits, but it does not control what your browser does with a page it has already rendered. Browsers restore form state — reload a page, or come back to it with the back button, and the fields may still hold what you typed, and the result may be shown again from the browser's own copy of the page. That is your browser's behaviour, it varies between browsers and settings, and this site can neither switch it off nor promise it will not happen. If you are using a shared computer, close the tab rather than relying on the page having cleared itself.

Cookies

The code of this site sets no cookies of its own, and uses no local storage, session storage or device identifier. It also does not read or act on Do Not Track or Global Privacy Control signals — that is a limitation, not a promise.

One cookie here is not this site's. The analytics script described below is Google's, and it may set a first-party cookie named _ga, and a second whose name begins with _ga_. First-party means your browser files them under isitagoodfit.com, even though the code that writes them is Google's. They hold a randomly generated identifier, which is how a returning browser is told apart from a new one. This site's own code neither reads nor writes them.

Cookie lifetime and data retention are two different clocks, and it is worth not running them together: how long a cookie stays in your browser is set by Google's script, while how long the recorded events are kept is a setting on the analytics property, described below.

What every request to this site reveals

The site is a set of files served by a hosting provider, and requesting one is a conversation with that provider's computers. Like any such request it carries your IP address, the time, the path asked for and the identifying details your browser volunteers, and it will normally appear in that provider's request logs. This is how the web delivers pages; it is not something this site chooses to do, and it is not something this site can switch off.

Those logs are the provider's, kept under the provider's policy. This site is served by Cloudflare Pages, and Cloudflare's privacy policy governs them. This page does not restate that policy's retention periods — the authoritative version is there, and it can change without this repository noticing.

Where the recorded events go

An event is delivered to three places, and two of them are switched off unless configured:

• An in-memory list on the page. Always. It is how the site's own behaviour can be inspected, and it disappears when you navigate away or close the tab.
• Google Analytics 4. A measurement ID was set when this page was built, so Google's script loads from googletagmanager.com and receives the events. That script is Google's code, not this site's. It is also the only reason your browser contacts Google at all on this site.
• A collection endpoint — not configured. No endpoint address was set when this page was built, so no such request is made.

Consent, and what this site does not do

There is no consent prompt on this site, and no cookie preference panel. That is a deliberate decision for a first launch, not a finding about the law: the site is small, it runs no advertising, and building regional consent machinery for the small number of visitors outside its main market was judged not worth doing yet.

The honest description of that is US-first, not compliant everywhere. Visitors in the European Economic Area, the United Kingdom and Switzerland are measured on the same terms as everyone else, without being asked first. If this site later sets out to serve those markets deliberately, a consent tool will be chosen and this page will change — before that expansion, not after it.

Following a link off this site

When a tool recommends a plan, the button leads to the provider's own site. Clicking it is a request to that site, and from that point the destination's privacy policy applies, not this one. The link also carries this site's affiliate tag, which is how a resulting purchase is attributed back here; the tag identifies this site, not you, and it is the same tag for every visitor who follows that link.

Opting out

There is no control on this site for turning measurement off, and no way to ask for recorded events to be deleted — no such mechanism has been built, and none is promised here. Measurement is on for every visitor, and the events described above are recorded with no answer values in them and kept for 14 months.

What exists is what your browser offers, and it works: blocking googletagmanager.com stops the analytics path completely, since that is where the script is loaded from, and blocking this site's own scripts stops the events before they are created. Google also publishes a browser add-on that opts a browser out of Google Analytics across every site that uses it, not only this one.

Not yet decided

These are open, and are listed rather than guessed at. Any of them may change what this page should say.

• Whether a collection endpoint will be used at all, and who would run it.

None of the four questions the gate waits on is open any more. Who operates this site, how to reach them, how long analytics data is kept, and whether a consent prompt is used are each answered above. The gate still reads this list rather than trusting this sentence: a production build that configures a measurement ID while any of the four is reopened fails outright, and the failure names the question.

Related

How this site makes money covers the affiliate relationship and what it does not change. The sources page is the register behind every factual claim the tools make.