Effective 14 August 2026Register revision 2.0WORKFLOW AI SOLUTIONS LTDCompany number 17005372
01 The result, in one line
Load a page here and nothing is written into your browser's storage by this domain. No identifier is issued to you, nothing is kept between one visit and the next, and no measurement product is loaded that would want to. The rest of this notice shows the working behind that sentence, because a claim of this kind is worth nothing unless it can be checked.
You can check it. Open your browser's developer tools on any page of this site, look at the storage panel, and compare what it shows against the table in section 3.
In the United Kingdom the relevant rule is regulation 6 of the 2003 Privacy and Electronic Communications Regulations, which the Information Commissioner enforces. It is broader than its nickname suggests: it governs storing anything in a visitor's terminal equipment and reading anything back out of it, whatever the mechanism is called. A cookie is one mechanism. So are the browser storage interfaces, a cache entry deliberately used as a marker, and a pixel that exists to make a request.
The rule sets a permission gate with one exception. Consent must be obtained first, unless the storage is strictly necessary to deliver the thing the visitor actually asked for. Convenience is not necessity, and neither is knowing how many people read a page.
Where storage carries an identifier, the UK GDPR applies on top of the 2003 regulations, which is why the privacy notice and this one are written to be read together.
Everything a page here can put in front of your browser, in one table. The final column is the state of your device after the step has run.
Every step of a page load, and what it leaves behind
Step
What it fetches
Why
Left on your device
The page
An HTML document from this domain
It is the thing you asked for
An ordinary browser cache entry, on the timings the response headers state
The stylesheet
runsheet.css from this domain
Layout, type and colour
A cache entry, no identifier of any kind
The script
runline.js from this domain
Reveals sections on scroll and hands the enquiry form to your mail client
A cache entry. The script writes no cookie and touches no storage interface
The mark
favicon.svg from this domain
The tab icon
A cache entry
The typefaces
A stylesheet and font files from Google's font hosts
The two families these pages are set in
Cached font files. Section 4 explains what Google sees
Scroll the table sideways to read every column
Absent from that table, and worth naming so the absence is unambiguous: analytics of any kind, advertising or remarketing tags, social network buttons, embedded video players, chat widgets, session recorders, heat maps, consent management platforms and A/B testing tools. None is installed, so none is described further down the page.
The typefaces are the single exception to everything being served from here. The stylesheet is requested from fonts.googleapis.com and the font files themselves from fonts.gstatic.com, both operated by Google. That request is made by your browser directly, so Google receives your internet address, the user agent string, and the fact that a font was wanted for a page on this domain.
Neither of those hosts issues a cookie when serving a font, and the files are cached by your browser like any other static asset. What remains is a connection log at Google's end, governed by Google's own privacy terms rather than by this notice. Section 7 of the privacy notice lists the suppliers standing in the path for everything else.
Hosting the same two families from this domain would close that request off entirely, and it is on the list of changes to make. Section 8 describes how any such change reaches this page.
Asking a server for a page necessarily tells it something. The hosting platform in front of this site records the internet address the request came from, the moment it arrived, the path requested, the response code and the user agent string, and it uses them to serve the page and to absorb abusive traffic.
That record lives on the platform, not on your device, so regulation 6 has nothing to say about it. It is covered instead by the request log entry at section 4.4 of the privacy notice, which sets out the ground relied on and how long the entries survive. Nothing in that log is queried to build a picture of an individual visitor.
A consent dialogue exists to obtain permission for storage that needs it. Read section 3 again: there is nothing on this site whose permission gate is open. Putting a banner in front of you anyway would ask you to agree to nothing, train you to dismiss a control that matters elsewhere, and require a consent platform that would itself write to your device to remember the answer.
So the design decision runs the other way. The behaviour is documented in a table you can verify in thirty seconds, and the page stays out of your way. If a future change puts something behind that gate, section 8 says exactly what would appear.
Browser controls are worth knowing about even where a particular site gives them nothing to do, and they apply to this site as much as to any other.
Blocking storage. Every current browser can refuse cookies and site data, either globally or for one domain. Applied here, the pages render and behave identically, because nothing on them depends on being remembered.
Clearing what is already there. Clearing browsing data removes cached files, including the fonts. The next visit simply fetches them again.
Blocking the font hosts. A content blocker or a browser setting that stops requests to Google's font hosts will stop the request described in section 4. The pages then fall back to the typefaces your system provides, and every word remains readable.
Private windows. A private or incognito window discards cache and storage when it closes, which on this site changes nothing about what was there in the first place.
Browser menus move between releases, so the reliable route is the settings search box in your own browser rather than a walkthrough written here that would be wrong within a year.
Suppose the practice one day wants to know which pages get read. The sequence would be published rather than deployed quietly: this notice gains a row in the table in section 3 naming the tool and what it writes, the effective date and revision number at the top of the page move, and where the tool needs permission a request for consent appears before it loads rather than after.
A visitor who declines would get the same pages, since nothing here is worth gating behind measurement. That is the commitment; the table is how you audit it.
Questions about this notice, or about something your browser has found that section 3 does not account for, go to [email protected]. Evidence of a gap between this page and the site's behaviour is the most useful message we could receive, and it gets either a correction to the page or a change to the site, with a reply saying which one happened.
The regulator for this subject is the Information Commissioner's Office, at Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, on 0303 123 1113. Complaining to it is open to you at any point, including without raising anything here first.