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. We add no tracking and no third-party asset to the files we publish. Cloudflare, which delivers every page here, can add to the copy that reaches you, and one thing it has added is Cloudflare Web Analytics, a Cloudflare service meant to count page views: we first found its script on the pages we checked on 1 September 2026, it was on each of the four pages we checked on 3 October 2026, and that day we decided to keep it. 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; the reports of network errors that proxy may ask your browser to send to Cloudflare; 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. 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. As we publish them, our pages load images and other files only from this site’s own address: the logo, the brand images and the diagrams are the site’s own, and no font, image or frame in those pages comes from anyone else. But writing none and running none are two different claims: the analytics script named above is Cloudflare’s, and it is in none of the files we publish. Nothing we write into a page reads or writes cookies or browser storage, and no page carries a form. What Cloudflare’s script does in your browser is Cloudflare’s. On 3 October 2026 we saw it send one report to Cloudflare from each of the four pages we opened; what Cloudflare records from such a report, we have not measured.
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 setting at Cloudflare can add to the copy that proxy hands back without one line changing in any file we publish. When we checked four of our pages on 3 October 2026, requesting them the way a browser does, each copy differed from the file we publish by one script tag and by nothing else; that tag was the analytics script, and it named a Cloudflare address, static.cloudflareinsights.com, as its source. So this section is a dated check rather than a present-tense claim: what we can tell you is what the pages carried when we looked, and when we looked.
Outside the HTML, the proxy can add what the page source does not show: headers, the lines of data that travel with each page to your browser. Two of them, nel and report-to, may ask your browser to send reports of network errors on this site to Cloudflare. They were on every response we saved from the proxy on 7, 10, 13 and 28 September 2026, and neither is in any of the files we publish. When we read them on 7, 13 and 28 September 2026, they named a Cloudflare address, a.nel.cloudflare.com, and asked for reports of errors only, not of requests that succeed. Any such report goes to Cloudflare, not to us: we collect nothing through those headers, and we have not measured what a report contains or whether your browser has ever sent one.
The scripts we write into a page do not watch you. Cloudflare’s analytics script is meant to count page views, and we are not disowning it: on 3 October 2026 we decided to keep it. Whether it has counted your visit, we have not measured, and the table below says who holds whatever it reports.
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 |
| Network error reports | Cloudflare, not us | Two headers, nel and report-to, were on every response we saved from the Cloudflare proxy on 7, 10, 13 and 28 September 2026, and are in none of the files we publish. They may ask your browser to send reports of network errors on this site to Cloudflare, not to us, and we collect nothing through those headers. We have not measured what a report contains |
| 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 | A Cloudflare service meant to count page views. Its script is Cloudflare’s and is in none of the files we publish: we first found it on the pages we checked on 1 September 2026, it was on each of the four pages we checked on 3 October 2026, and that day we decided to keep it. An analytics script keeps no bots out. Cloudflare holds whatever 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. Our Cloudflare account carries the measure that does keep automated traffic out, and it was never the analytics: three request-filtering rules created on 26 August 2026, which match requests for WordPress addresses, for the fingerprints of automated tools, and for hidden files such as /.env and /.git/HEAD. None of the three can match an address this site publishes, so nothing you can reach from a page here is filtered by them.
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 when this page was last updated.
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. Disclosure first, then the ad. We have missed that order: on 1 September 2026 a Cloudflare analytics script was on every page we checked, and this page had described no analytics at all until we rewrote it that day. And nothing automatic enforces the order, 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. Whatever the analytics script reports 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. It has failed that rule twice, both times by describing less than was there. We number the two by the dates of their entries on our Corrections Policy page, not in the order they began, because we have not dated when either began. The first time it said there was no analytics while a script was on the pages we checked on 1 September 2026, and this page described none until we rewrote it that day. The second time it left out the nel and report-to headers described above. Both are listed, dated, on our Corrections Policy page. What you are reading here is the rule and the two places 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. On 3 October 2026, requested the way a browser requests it, this page carried two: our own structured data, and Cloudflare’s analytics script; our home page carried three, because it holds a second block of our own structured data. Make the check the way a browser does. A tool that does not ask for a web page can be handed a copy without the analytics script, as ours was on 3 October 2026, and then finds no trace of it: call it the blind check. The two headers described above will not be there: they travel with the page, not in it. Find a script tag that nothing above accounts for, and this page is out of date: tell us.
Last updated: 7 October 2026. Questions: info@dragonautoguide.com.