Privacy proof — receipts for our privacy claims

Last verified: May 2026

This page exists so you don't have to take our Privacy Policy on faith. Every claim we make about how SiteKiln handles your data is verifiable. Here's the proof.

1. Trust badge

The "No tracking. No accounts. No newsletter." badge in the footer is not marketing — it's a contract. If any of the points below stop being true, the badge comes down before the practice changes.

2. This page itself

The fact you can read a public, dated audit of our privacy practices — with the actual mechanisms, not just adjectives — is point one of the spine. Most sites don't publish this. We do.

3. Content Security Policy (CSP) headers

Open your browser's network inspector and load any page on this site. Check the response headers. You'll see a strict CSP that limits where the page can load scripts, images, fonts and data from — self plus a tightly-scoped allowlist (currently https://plausible.io for analytics). No ad-network domains. No tracker domains. No fingerprinting CDNs.

4. Self-hosted assets

Fonts, images, icons and CSS are served from our own domain. We don't pull from Google Fonts, jsDelivr, or any other third-party CDN that would log your IP and User-Agent every time you load a page. Inspect the network tab — you'll see requests only to our domain and to plausible.io.

5. No-JS fallback

Turn JavaScript off in your browser. Reload the homepage. Read a guide. Search the site. It all still works. That means the site does not require client-side execution to function — no tracker can fire from a script you didn't intend to run, because the site doesn't depend on scripts.

6. Outbound-link hygiene

Every external link on the site uses target="_blank" with rel="noopener noreferrer". The noreferrer is the important bit — it stops the destination site from seeing which SiteKiln page you came from. View page source on any guide and search for an external link to verify.

7. No email capture, anywhere

There is no newsletter signup. There is no "subscribe to updates" box. There is no email gate on guides. The only place we ask for an email is:

• The sponsor enquiry form on /advertise (business contact, not consumer email).
• The builder tool gate on document builders — that's a one-time verification you're a real tradesperson, not a mailing list.

Search the site. Right-click → view source on the homepage. There is no <input type="email"> in any persistent CTA.

How to verify

You don't need to trust us on any of this. Open DevTools, look at the Network tab, look at the response headers, look at the page source. Everything claimed above is observable from your own browser in under five minutes.

If you find a discrepancy between this page and what the site actually does, email hello@kilnguides.co.uk and we'll fix one or the other within 24 hours.