Privacy · plain language

A privacy policyyou can actually read.

Three things on this site involve data — the services that deliver the page, the assistant panel, and the contact form — and every one of them is named below. No legal maze, no fine print, and nothing described more kindly than it behaves.

Last updated 17 August 2026 no accounts · no cookies from us · no ad trackers

Section 01

The short version

You can read every page of this site without an account, without a cookie set by us, and without an advertising tracker following you afterwards. Nothing you read is recorded against your name, because we never learn it.

Three things on the site do move data, and each has a section of its own: the chat assistant, which sends what you type to a model; the outside services that deliver the page; and the forms, which send what you fill in to one inbox.

That shape is a decision rather than an oversight. Being clear and honest is how we work, and it starts with how we treat a visit.

The rest of this page spells out the detail in plain language. If anything is unclear, write to [email protected] and a person will answer.

Section 02

What we collect

Nothing, unless you hand it over. This is an informational website — you can read every page without creating an account or telling us who you are.

We use no advertising trackers, and we set no cookies: the small files many sites store in your browser to recognise you or follow you elsewhere. We do not build a profile of you, and we do not follow you to other websites.

That covers browsing, and browsing only. The moment you type into the assistant, fill in a form or send an email, you are choosing to send something — and sections 04, 06 and 07 say exactly where it goes.

Section 03

What stays in your browser

One session flag — a temporary note your browser keeps for itself. It remembers that the intro animation already played during this visit, so you do not have to watch it again on every page. It never leaves your device, and it is not a tracker.

The readiness check is the other one. Its five answers are held in the open page while you answer, used once to pick a band, and then gone: they are never transmitted and never written to your device. Reload the page and it starts from the first question again.

The chat assistant is not in this category, and it would be easy to assume it was. It is described on its own in the next section.

Section 04

The chat assistant

The assistant panel in the corner of the site is a language model, not a script full of canned answers. It does not run inside your browser, and it is worth knowing that before you type into it.

When you send it a message, the panel posts that message — together with the conversation so far, so the reply follows on — to a FuseLoom endpoint running on Cloudflare. The endpoint adds FuseLoom's own written notes about the firm and passes the whole thing to Anthropic, whose Claude model writes the reply. The reply comes back the same way and appears in the panel.

We do not keep the transcript. There is no database behind the panel, nothing is written to your device, and no copy is emailed to anyone. The conversation exists only in the page you have open, and closing the tab ends it. Anthropic receives your message in order to answer it, and handles it as our supplier under its own terms.

When a question needs a decision the assistant should not make on FuseLoom's behalf — a scope, a contract, a commitment — it stops and offers you the callback form or our inbox. It does not send us anything by itself. Nothing you typed reaches a person unless you take one of those two routes and say it again yourself.

So: do not paste anything confidential into it. Customer records, contracts, credentials, anything under an NDA — bring those to an email or a call, where you know exactly who is reading. The assistant is there for questions about FuseLoom, and it is the wrong place for your own private material.

Section 05

The outside services

A handful of outside services help this site load, answer and reply, and each one technically receives some data along the way. They are named here, one by one, with nothing left off the list.

  • fonts Google Fonts serves the typefaces you are reading. When your browser fetches those font files, Google receives your IP address — the number that identifies your internet connection — and basic details about your browser. That is simply how the web delivers files; we do not receive that data ourselves.
  • measuring Cloudflare Web Analytics counts visits. It records the page you looked at, the site that sent you, your country, your browser and device type, and how quickly the page loaded. It sets no cookies, it does not fingerprint your device, and it cannot follow you to another website. We use it for one thing: to see which pages are actually read and whether the site is fast enough. A privacy extension that blocks cloudflareinsights.com stops it, and the site works exactly as well without it.
  • hosting Cloudflare hosts the site and keeps standard infrastructure logs — routine technical records of requests — for security. Every page request appears in them, including this one. The small server-side functions behind the contact form, the call request and the assistant also run on Cloudflare. How long those logs are kept, and where, is set by Cloudflare rather than by us, so we will not state a period we cannot enforce.
  • anti-spam Cloudflare Turnstile is the check that sits inside the contact form, so the form can tell a person from a bot without making you solve a puzzle or create an account. It loads on the contact page and nowhere else. Whether it stores anything in your browser is Cloudflare's to state rather than ours; what we can state is that FuseLoom sets nothing and reads nothing through it.
  • the model Anthropic writes the chat assistant's replies. It receives what you type into the panel and the conversation so far, and nothing else about you. See section 04.
  • email Resend delivers the emails a form sends: the request that reaches us, and the acknowledgement that reaches you. See section 07.

Everything else — the icons, the graphics, the readiness check, the form itself — is built into the site, so no other outside service is contacted to display a page or to take what you type. There is no calendar service any more: asking us to call you back opens a form on this site rather than sending you to Google, so nothing about you reaches a calendar provider.

Section 06

When you email us

If you write to [email protected], we receive what you choose to send: your email address, your message, and any attachments. We use it to reply and, if we end up working together, to do that work well. Nothing else.

We do not sell or share your personal information.

Section 07

When you use a form

There is one form on this site and it appears in two places: on the contact page, and in the panel that opens when you ask us to call you back. It sends your name, an email address or a mobile number — whichever you chose to give — the part of the day that suits you, your timezone, and an optional note to a small FuseLoom endpoint running on Cloudflare.

There is a third, smaller one. At the end of the 45-second readiness check you can ask us to email you the result. That sends your email address and the answers you just gave — nothing else, and only if you ask. The check itself needs no address at all: your result is on screen either way, and ignoring the offer costs you nothing. What we receive is the same email you do, which is how we know what to say if you write back.

It will not send until you tick a box, and the box starts empty. The sentence beside it names one purpose and only one: using those details to reply to you. Leave it unticked and the form refuses — and so does the endpoint behind it, which rejects anything arriving without it.

Nothing you type is stored. The endpoint checks the anti-spam token, emails your request to us, sends you an acknowledgement if you left an address, and keeps nothing. There is no database, no CRM and no list behind this form. Until recently a booking system did keep requests — for thirty days, or ninety once a call was confirmed. That system has been removed and its storage with it.

Your details are never used for marketing. No newsletter, no announcements, no campaign, no “just checking in”. You are not added to a mailing list, because there is no mailing list. They are not sold, not rented, and not passed to anyone else for their own purposes. If we ever wanted to do any of that we would have to ask you first, separately, and you would be free to say no.

Where they sit until then is the one inbox they were emailed to, and not for long. Once we have spoken, the enquiry is deleted. We do not keep a file on people we have talked to, and we do not keep a list of people who once asked. If an enquiry never reaches a call — you change your mind, or we never hear back — it is deleted within ninety days anyway.

The one exception is not an exception to this promise so much as the end of it: if we go on to work together, your details stop being an enquiry and become part of the engagement, covered by the agreement we both sign. You will have read that agreement before it applies.

Ask and they go sooner: write to [email protected], say so, and it is done by hand — same day where we can. There is no account to close and no form to fill in to make that happen.

Those emails are delivered by Resend, a specialist email-delivery service. The anti-spam check is Cloudflare Turnstile. Both are named in section 05.

If you would rather not use a form at all, email us directly instead — it reaches exactly the same place.

Section 08

Your choices

Because we collect so little, your choices are simple. You can read this entire site without accepting anything, and there is no tracking to opt out of.

If you would rather your browser did not contact Google Fonts at all, browsers and privacy extensions can block requests to outside services. The site should still be readable — just in a plainer typeface.

And if you would rather no model ever saw a word from you, do not open the assistant. Nothing else on the site depends on it, and everything it can tell you is written on a page you can read instead.

Section 09

Changes to this policy

This policy describes the site as it works today. If that ever changes — say we switch on an analytics tool, or the assistant starts keeping a transcript — we will update this page and change the date at the top, so the policy matches the site.

We would rather keep it boring. A privacy policy with nothing dramatic to report is the kind we like.

Section 10

Who to write to

Questions about this policy — or about anything else? Email [email protected]. A person reads it, and a person replies.

The other half of the same question — what the site is for, and why a signed agreement outranks anything written here — is answered on the terms of use.

The fuller version of this answer lives on the trust page. Every outside service that touches this site, named — and the security headers your own browser can check without asking us.

Read the trust page
Still a question?

Talk to a person, not a policy.

If anything here raises a question — including “delete what you have on me” — write to [email protected] and you will get a straight answer in plain language, the same way we handle everything else.

Email [email protected]

Read by a person · the house rules that sit beside this policy are on the terms page