What this site knows about you.

The short version

If you only read this site, nothing about you is stored that could identify you. No cookie is set. No script reports your visit anywhere. If you send me a message, I get your name, your email and what you wrote, and I use it to reply to you and nothing else.

The one addition to that: if you arrived on a link with a campaign tag on it, the tag is remembered in this browser tab and included in the message you send, so I can tell which piece of outbound reached you. If you never send a message, nobody ever sees it and it is gone when you close the tab.

If you just read the site

The web server keeps an access log, the way every web server does. Before anything is written to disk, the last part of your IP address is replaced with a zero — so a visit from 203.0.113.47 is recorded as 203.0.113.0. That is done at the server, not afterwards, so the full address is never stored at all.

The log records the page requested, the time, the response status, the referring page and the browser's user-agent string. I use it once a night to produce a count of pages viewed, so I can see which parts of the site people actually read. The result is a summary on my own machine. It is not published, not shared, and not sent to any third party.

Logs rotate and are deleted on the server's normal schedule, within a few weeks.

If you use the contact form

The form asks for your name, your email address, which service you are interested in and a description of the job. All of it goes to my inbox so I can reply. That is the only reason I have it.

One line is added that you did not type: where you came from. If your link carried a campaign tag — the utm_source you see in an advertising or newsletter URL — or if another site sent you here, that is appended to the email as a single line of text. It exists because an inbox cannot otherwise tell a LinkedIn post from a referral from someone typing the domain in, and I need to know which of those is worth doing again. It is not a profile, it is not linked to anything else, and it goes to the same inbox as the rest of your message.

Form submissions are delivered by Web3Forms, which passes the message on as email and does not require you to create an account. If the form fails for any reason, the page falls back to opening your own email client instead, in which case nothing passes through a third party at all.

I keep enquiry emails in my inbox because that is where a conversation lives. If you would rather I deleted yours, ask and I will, and I will confirm when it is done. I do not add anyone to a mailing list, because there is no mailing list.

Cookies and analytics

No cookies at all — none first-party, none third-party. No Google Analytics, no Meta pixel, no heatmaps, no session recording, no advertising or measurement script of any kind. Nothing about your visit is transmitted anywhere as you read.

There is one piece of browser storage, and only if you arrive on a tagged link or from another site: a single sessionStorage entry holding that campaign tag or referring address, described above. Type the domain in yourself and nothing is written at all. Session storage is not a cookie — it is readable only by this site, is never sent with a request, and is discarded the moment you close the tab. It is written so that a message you choose to send can say where it came from. If you send nothing, it does nothing.

That is why there is still no cookie banner on this site: nothing here tracks you between visits or between sites, so there is nothing to consent to.

Who else is involved

The site runs on a server I rent and administer myself. The hosting provider necessarily handles the network traffic that reaches it.

Web3Forms delivers contact form submissions as described above.

The typefaces are served from this site's own server rather than from Google Fonts. Loading them from Google would have meant your browser contacting Google, and Google receiving your IP address, purely to draw the text. They are hosted here instead so that does not happen.

Nobody else. No advertising network, no analytics vendor, no font CDN, no chat widget, no social buttons that phone home. There is one video on the site — the recording on the document extraction page — and it is served from this server like every other file here, not embedded from YouTube or anywhere else. It does not autoplay and it reports nothing back. Apart from sending the contact form, visiting this site sends nothing to anyone except this server.

If we work together

A build is different from a website visit. If you hire me, I will usually need access to systems and data belonging to your business — documents, an inbox, a database, an API key. I treat all of it as confidential and use it only to do the work you asked for.

Wherever it is practical, what I build runs on infrastructure in your name, so your data stays with you rather than passing through me. Several of the builds can run entirely on hardware you control, with no external calls at all, for work that cannot legally leave your building.

When a project ends I remove the credentials and working copies I no longer need. If your work is subject to specific obligations — health data, financial records, anything with a regulator attached — tell me before we start so the build can be designed for it.

Your rights

You can ask what I hold about you, ask for a copy, ask me to correct it, or ask me to delete it. Email [email protected] and I will answer the same day. There is no form to fill in and no process to navigate; it is a one-person business and the answer is usually short.

Changes

If any of the above changes — a different form handler, a different host, a new third-party request — this page changes at the same time. It describes what actually happens, so it is only useful if it is kept accurate.