What this site knows about you.
Almost nothing, and that is deliberate. There are no cookies, no analytics, no advertising pixels and no tracking of any kind on this site. This page explains the small amount that does happen, and what changes if we work together.
Last updated 3 September 2026
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.
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.
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
There are none. No first-party cookies, no third-party cookies, no local storage, no session tracking, no Google Analytics, no Meta pixel, no heatmaps, no session recording. That is why there is no cookie banner on this site: 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 on this site are served by Google Fonts. That means your browser requests the font files from Google, and Google receives your IP address in the course of serving them. No cookie is set by this and it is not used to identify you, but it is a request to a third party and you should know it happens.
Nobody else. No advertising network, no analytics vendor, no chat widget, no embedded video, no social media buttons that phone home.
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 contact@keepsrunning.com 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.