Privacy

We use a self-hosted Plausible instance and Google Analytics 4 to count pageviews. Site code emits eight named custom interactions: that a cost was calculated, a route list was filtered, a result table was sorted, evidence was opened, a vendor link was followed, an unknown was encountered, an answer was reached, or an export was downloaded.

Plausible sets no cookies and does not track people across sites. Google Analytics starts with analytics and advertising storage denied, so the site does not set analytics or advertising cookies.

The base Plausible loader does not add automatic outbound-link, file-download, or form-submission events. Each of the eight named custom interactions has a fixed payload: page or vendor identifier where relevant, the kind of control used, sort column, export format, link placement, or the field whose value is unknown. The browser discards every other data attribute before calling Plausible and Google Analytics. Those custom events never attach a destination URL.

Google Analytics 4 Enhanced Measurement is also enabled in the current data stream and operates separately from the eight custom events. It can emit form_start and form_submit with the form identifier, form destination, and submit-button text, but not the values typed into form fields. It can emit click and file_download with link metadata including the full destination URL, and can measure scroll depth, site-search query parameters, and page-history changes. One provider or download action can therefore appear under both its named custom event and Google's automatic event.

Calculator volumes, success rates, and filter text stay in your browser and are not analytics properties. Every available workload was priced in advance from published vendor rules, and the controls switch among those checked results. A volume outside the available choices returns a clear refusal rather than an invented number. The separate contact form is described below.

Loading an analytics service sends the normal request information needed to deliver and measure the page view, including the requested page, referrer, IP address, and user agent. Plausible discards the IP address after generating an anonymous daily identifier. The eight custom interactions add only the fixed properties listed above; Google Enhanced Measurement adds only the automatic event context described above.

You do not need an account, name, email address, or payment details to use the public comparison. If you choose to submit a report, the contact form sends a category, reply email, short summary, and details. Name, affected page, and supporting source are optional. Those fields leave your browser only when you submit the form.

The contact Worker validates the form and the Turnstile security check, then forwards an accepted report to a private Discord operator channel. Turnstile receives the response token and request information needed to verify the check. The Worker does not write contact submissions to its mail KV or another application database. The resulting Discord message has no automatic deletion schedule.

Every price links to the vendor page it was read from, because a figure you cannot check is not worth publishing. Following one takes you to that company, where their own privacy policy applies and ours stops.

Some outbound links may in future earn us a commission. Those are labelled where they appear, and they never affect the order of any table on this site.

Use the contact form for a privacy question, to ask what contact report is held, or to request deletion. Include enough detail to identify the report. The reply address is used when follow-up is needed. Cloudflare and Discord process the security check and delivered message under their own service terms. Do not include passwords, keys, private billing records, or other secrets.