Privacy Policy
The short version: this site sells you nothing and asks you for nothing, but it is not true that nothing about your visit is collected. Since 29 August 2026 this site has carried Cloudflare Web Analytics — a Cloudflare feature we switched on to see where visits come from and to keep harmful bots out; when we checked twelve of our pages on 1 September 2026, every one of them carried its script. Around it sit the ordinary things, and the table below lists them: the standard logs any web server keeps, made from requests the Cloudflare proxy in front of this site receives before we do; whatever cookies that proxy may set for security and performance; and any email you choose to send us. There are no ads on this site today. We may in future carry advertising, and we may in future collect data about the people who read this site for analytical and marketing purposes; the sections below say what each of those would mean, and what gets published when one of them starts.
What actually runs when you open a page here?
Two kinds of script, and only one kind is ours: when we read the source of twelve of our live pages on 1 September 2026, each of them carried our own structured data and a script Cloudflare had inserted. The scripts we write into a page hold structured data (application/ld+json): a machine-readable summary of the page for search engines. They describe; they do not run. We write no analytics code, no tag manager, no advertising tags and no social widgets into our pages — but writing none and running none are two different claims, and here they came apart: the analytics on this site is a Cloudflare feature, switched on in a dashboard at Cloudflare, and it is in none of the files we publish. We load no external images, fonts or iframes either — our diagrams are SVG we draw in-house and the logo is drawn inline in the page. Nothing we write into a page reads or writes cookies or browser storage, and no page carries a form; what Cloudflare’s own script does in your browser is Cloudflare’s, and we have not measured it.
Call it the served-page gap: the file we publish is not always the HTML that reaches you. Every page here is delivered through the Cloudflare proxy this site sits behind, and a feature switched on at Cloudflare can add to the copy that proxy hands back. This page has now had to describe two such features. The first was email-address obfuscation, which rewrote our address so that spam harvesters could not read it and added a small Cloudflare script to turn it back for a human; it was on when we checked the live site on 27 August 2026, and it was off when we checked again on 1 September 2026 — our address stood readable in the source of this page, five times, with no script behind it. The second is analytics: on 1 September 2026, on the twelve pages we checked, every one carried a Cloudflare script element. It is in none of our files. Turning the first feature off closed that case and not the class — and the class produced a second case before we had rewritten this page.
So the honest form of this section is a dated check rather than a present-tense claim: what we can tell you is what the live pages carried when we last looked, and when we looked.
The scripts we write into a page do not watch you. The one Cloudflare added to every page we checked on 1 September 2026 does the counting, we asked for it, and the table below says who holds what it counts.
So what is collected, and by whom?
| What | Who holds it | What it amounts to |
|---|---|---|
| Web-server logs | Cloudflare, then our hosting | IP address, time of request and user agent — the ordinary record any web server keeps in order to serve pages |
| Proxy cookies | Cloudflare, not us | This site sits behind the Cloudflare proxy, which may set its own security and performance cookies. Those are Cloudflare’s and governed by Cloudflare’s terms |
| Email you send | Us | Your address and whatever you write in it — nothing more, because there is no other channel |
| Cloudflare Web Analytics | Cloudflare, not us | Switched on by us at Cloudflare on 29 August 2026, to see where visits come from and to keep harmful bots out. Cloudflare added its script to every page we checked on 1 September 2026, and holds what that script reports, under Cloudflare’s terms, on the same footing as the web-server logs in the first row of this table. We have not measured what it stores in your browser, and we do not claim it stores nothing |
| Search Console | Aggregated search queries that led people here. The report is Google’s, and it does not identify a visitor |
Why does Cloudflare head that first row? Every request to this site arrives through the Cloudflare proxy, so Cloudflare receives your request data — IP address, user agent, the page you asked for — before our own server sees it. That is how a proxy works, not a per-visit choice of ours — and it works in both directions: the HTML you read is the copy Cloudflare hands back, which is how a Cloudflare feature can add to that copy a script we never wrote, the served-page gap described above. What Cloudflare keeps of it, and for how long, is set by Cloudflare under Cloudflare’s terms, not ours.
Cookies set by the pages we write: none. What Cloudflare’s own features set is Cloudflare’s, and we do not measure it.
What happens to an email you send us?
We read it and we reply. If it reports an error it enters the process published on our Corrections Policy page — acknowledged within 2 business days, re-checked against primary sources, and if it is confirmed the page is corrected and its last-verified date updated; material corrections are noted on the corrected page and listed, dated, on the Corrections Policy page. Your address is not added to a mailing list, because there is no mailing list. It is not sold, rented or passed to anyone else. Ask us to delete the correspondence and we delete it: info@dragonautoguide.com.
Are there ads on this site?
Not today. No advertising networks, no ad partners, no third-party advertising cookies, no affiliate links and no paid links — every outbound link on this site points at a government register or a manufacturer’s official site.
That may change, and in two ways. This site may in future carry advertising served by third-party advertising networks; if it does, those networks — not us — would set their own cookies or similar identifiers to select and measure the ads shown, and those could include ads chosen on the basis of your earlier visits to this and other sites. And we may in future collect data about the people who read this site for analytical and marketing purposes, beyond the traffic measurement described above. Neither had begun by 1 September 2026, the day this page was rewritten.
What we owe you is the order: before the first ad appears on this site, and before any collection for marketing purposes begins, this page is updated to name each partner and to state what it collects — an order we have already missed once, on 29 August 2026. Disclosure first, then the ad. We have missed that order once already — the analytics above started on 29 August 2026 and this page did not describe it until 1 September 2026 — and nothing automatic enforces it, because a feature can be switched on in a dashboard at Cloudflare without one line changing in anything we publish. So read it as a commitment with a known failure mode, and use the check at the end of this page, which does not depend on us.
One thing advertising will not do is move a number or soften a conclusion. Our Editorial Policy says content is not sponsored by any carmaker, and that affiliate links, where present, are disclosed and never influence technical conclusions. It carries no advertising clause yet; before the first ad appears, it will — the same commitment as the one above, with the same known failure mode. Your browser’s own cookie controls, meanwhile, work whatever we publish — they do not depend on us.
What about links that leave this site?
Outbound links go to government registers and manufacturers’ official sites — the documents behind our tables. Follow one and you are on their site under their terms; what they log is theirs, not ours. We have no visibility into it and no control over it.
What can you ask us for?
In practice, two: ask what correspondence we hold from you, and ask us to delete it. There is no account to close, no profile to export and no purchase history to retrieve, because none of those exist here. What the analytics collects, for as long as it runs, is a different matter and not ours to hand over or delete: it is held by Cloudflare under Cloudflare’s terms, like the request data in the first row of the table above, and we make no claim to control it.
When does this page change?
The rule we set ourselves is that this page changes before the practice does, not after. On 29 August 2026 it did not: analytics started that day, and this page went on saying there was none until we rewrote it on 1 September 2026. That gap is listed, dated, on our Corrections Policy page. What you are reading here is the rule and the place we broke it, not a mechanism we do not have.
If you would rather check us than believe us, check the page rather than the promise: open the source of this page as your browser receives it, and read every script tag on it. When we did that on 1 September 2026, each of the twelve pages we checked carried two — our structured data, and Cloudflare’s analytics script — except our home page, where a second block of our own structured data made it three. Find a script tag that nothing above accounts for, and this page is out of date: tell us.
Last updated: 1 September 2026. Questions: info@dragonautoguide.com.