Privacy

What stays on your device

Your factors, weights, scores and result stay in your browser. Session storage holds them so a refresh doesn't lose your work, and closing the tab clears them. We never store any of it. The one exception is the factor names you ask us to suggest scores for, described below. Your browser builds the PDF export too.

What leaves your browser

We don't keep any of it. A few things pass through briefly, and here's exactly what.

Reach the factors step, and your browser sends your decision question, the context line and your option names to an AI provider (currently OpenRouter) so it can draft factor suggestions. This happens automatically when you land on that step. Your weights, scores and result never go anywhere, and we keep no copy of the request.

On the same step, Suggest more asks for factors your list leaves out. Only if you press it, your browser sends the same question, context line and option names, plus the factors already on your list, to the same provider. You can use it once per decision, and we keep no copy of the request.

On the scoring step, each factor has a Suggest button, and Suggest all covers every factor with an empty score. Only if you press one, your browser sends your decision question, the context line, your option names and the name of each factor it covers to the same provider, which passes them to a scoring model called Jev, made by TypeSafe. It sends back suggested scores. Your weights and the scores you typed are not sent, and we keep no copy of the request.

If you send feedback, the thumbs up or down and any text you type in the suggestion box go to our database. Nothing else comes with it: not your question, not your options, not your result. Skip the box and nothing is recorded.

If you write to us from the contact page, your name, email address and message go to the same database, so someone can read it and reply. Nothing from the wizard goes with them. Alongside each message we store a scrambled form of your IP address, salted with the date so it changes daily, which caps how many messages one sender can file in an hour. The address itself is never written down.

Google Analytics

Every page loads Google Analytics, so we can see how many people visit and which pages they read. It runs on every page, including this one. It sets cookies in your browser and sends Google the usual web measurement data: the pages you view, roughly where in the world you are, your browser and device, the site or search that sent you, and a random ID that recognises the same browser on a return visit. Google's privacy policy governs what Google then does with it.

Nothing you type into the wizard is sent to Google. Not your question, not your options, not your factors, weights, scores or result. We never give Google your name or email address, and we run no advertising and no remarketing.

Browser settings, tracker blockers and Google's own opt-out add-on all stop it. The site works exactly the same with it blocked.

The five counters

Separately from Google, the site keeps five tally marks of its own. One goes up when the wizard loads. One when you reach the factors step, so your choices are named. One when you reach the scoring step, so every factor has a weight. One when an answer appears. One when someone saves a PDF. That is the entire list.

Nothing that could identify you is recorded next to those counts. Not your IP address, not a scrambled version of it, not a browser or device fingerprint, not a cookie, not a visitor ID, not the page you came from, not even the time of day.

A stored row is a date, a counter name and a number: on 8 September 2026, the "an answer appeared" counter went up 12 times. There is no column that says who, because no such column exists. We cannot tell whether those 12 were 12 people or one person twelve times, and neither can anyone who reads the database.

Your question, your options, your factors, your weights, your scores and your result are never sent with a counter. None of them are ever stored.

Hosting

The site runs on Cloudflare Workers. Like any web host, Cloudflare handles standard request data such as your IP address, browser and the time of the request, to serve pages and block abuse. Cloudflare's privacy policy covers that. We keep no logs of our own.

Cookies

Google Analytics sets its own, described above. We set none beyond that, and we run no advertising cookies. Your browser's local storage holds your light or dark theme preference, and it never leaves your device.

Changes and questions

If we change this policy, the date at the top changes with it. Anything unclear, email us from the contact page.