What this page is
This text is general information; it is not legal advice and gives no compliance guarantee under any regulation. Its purpose is to state plainly what this website actually does — and does not do — with personal data.
What data we collect
This site is made of static files: there is no account, membership, comment, form or payment system. The site code asks for and stores no name, e-mail, phone number or other personal data from visitors.
The single exception is correspondence you initiate: once a verified channel is published, what you send and your address are used only to answer your request — the principle is written here even before the channel opens.
Put in reverse: the site carries no analytics script, no heat-map, no session recorder, no A/B tool, no ad pixel, no fingerprinting technique. The source is open to inspection — view the page source and you will find no third-party measurement domain. "We collect nothing" is not a policy sentence here; it is a technically auditable state.
For contrast, list what a typical corporate site collects: analytics identifiers, ad cookies, form submissions, newsletter lists, session recordings. None of these exists here — no mechanism to collect them was built. 'We don't collect' is not a policy preference on this site but an architectural fact, verifiable by anyone in the source code.
Server logs
Like any web host, the server this site runs on may keep access logs (IP address, timestamp, requested page, browser string). Such logs are the hosting provider’s standard security and debugging practice; the site owner does not use them for marketing or profiling.
Log retention and format follow the hosting provider's own policy; the site owner does not export raw logs, share them with third parties, or turn them into per-visitor analysis. Looking at logs in exceptional cases — say, suspected abuse — serves understanding misuse of the system, never profiling a visitor.
Rather than hiding that logs exist, we draw their limit: the owner's access to them is whatever the hosting panel exposes, they are not shared with third parties, never fed into marketing systems, and rotate away on reasonable schedules. Should a legal obligation arise, action is taken only on a properly formed request from the competent authority and strictly within its scope.
Third parties
Pages contain no third-party analytics, advertising, social pixels or external font/service calls. All CSS, JavaScript, images and documents are served from this domain; your browser sends requests nowhere else.
The choice also buys resilience: a page that calls no external domain cannot be broken by that domain's outage or policy change. For the visitor the practical consequence is simple: every byte you see here comes from the domain in the address bar, and that claim is verifiable in your browser's network tab within seconds.
This choice protects performance and privacy at once: no external font servers (system fonts are used), no external scripts, no social widgets. Your browser's network tab is the live proof — open the page and see only webtrustengine.com addresses in the request list.
Retention and deletion
Since the site stores no visitor data, there is nothing to delete on the site side. E-mail threads are kept until your request concludes and for a reasonable archive period; write to the same address to have them removed.
Correspondence that turns into a service relationship puts client files under a separate regime: working copies are kept for the duration of the engagement, move to archive order at delivery, and are destroyed on request — a regime stated in writing in the agreement. The website itself hosts none of those files in any form.
Your rights
Data-protection law where you live may grant you rights such as access, correction and erasure. Route such requests via the contact page; they are answered honestly and within the real practice described on this page. When a direct channel is published, this page updates too.
The honest description of the request flow: identity is verified only to be sure the request concerns your own correspondence, with the minimum data possible; the reply comes within a reasonable time and rests on the actual practice this page describes. Since the site keeps no record about you, most requests have a one-sentence answer — and that sentence is not an evasion but the consequence of the architecture.
If identity verification is needed to answer a request, only the minimum required to validate it is asked; nothing more is requested or retained. The response-time target is reasonable business days, and answers reference the real practice on this page in plain language rather than legal jargon.
Children and international transfer
The site is not directed at children and, collecting no data at all, processes none about them. With no visitor data collected, there is no cross-border transfer either; your e-mail correspondence travels on the infrastructure of the e-mail provider you use.
Changes and questions
If practice changes, this page is updated and — per the site’s release discipline — the change enters the manifest/checksum records. Questions about this page follow the routing on the contact page. If your question is does the site process X, the answer is most likely already here: it does not.
How this page relates to the engine
In WebTrustEngine's 10-domain model, 'Privacy / Cookie Readiness' is a domain of its own: the engine classifies visible tracking signals, cookie notices and third-party calls on the sites it reviews. This page is that same lens turned on this site — we do not exempt ourselves from the audit we describe.
The symmetry hands you a practical test: reading any vendor's privacy page, ask 'does their site do what it says?'. Alignment of word and behaviour is the cheapest and sturdiest measure of trust in this field.
Children's privacy
The site carries corporate content for a general audience; it contains no children's sections, gamification or data-collecting interactions. Since no personal data — age included — is requested from any visitor, processing children's data is structurally out of the question.