Privacy Policy
Questions about this privacy notice, or about the way personal data is handled on this site, can be addressed to the data-protection point of contact of the publisher. The postal and electronic contact details are printed in the footer of every page on this site, together with the registered company name and number of the publisher.
The point of contact is an editorial function rather than a certified data-protection officer, because the volume and nature of personal data processed here does not require a DPO under UK GDPR. If the scope of processing changes — for example, if we start operating a reader forum or a direct-mail newsletter — we will appoint a DPO and update this notice before the change takes effect.
If you are not satisfied with the response from our point of contact, you can lodge a complaint with the UK Information Commissioner's Office. The ICO's contact details are published on the ICO website.
When you browse the site, our hosting provider receives the usual connection metadata — your IP address, the time of the request, the page you asked for, the referring page if any, and your browser's user-agent string. This is standard web-server logging; it is required for the pages to load and for us to defend the site against abusive traffic.
When you fill in the contact form, we receive the fields you typed into that form (email address, subject line, message body) and the technical fingerprint of the submission. We do not run behavioural profiling, we do not fingerprint your device beyond what is needed to filter spam, and we do not pass the form content to any marketing automation tool.
We do not operate a comment system, we do not run a reader-login area, and we do not ask you to create an account. We do not use social-media sign-in. We do not host a payment surface. All of these are commonly abused for tracking, so keeping them absent is itself a privacy protection.
Server access logs are retained in a short-term bucket for up to 30 days to help us investigate performance and abuse incidents, then they are deleted automatically. Longer retention is possible only for a specific log line that is part of an open security incident, and in that case we retain the line until the incident is closed.
Contact-form submissions are retained for as long as the thread is live, plus a short archive window of up to twelve months, after which the message and any reply are deleted. If you ask us to delete a submission earlier, we will do so unless the retention is required to defend a legal claim.
We do not retain any analytics timeline about individual readers because we do not collect one. We do retain anonymised aggregate counters — a daily page-view count per URL, for example — and we may retain those indefinitely because they do not identify any single reader.
Server logs are used to keep the site running: to debug a slow page, to block a request that looks like a scraping attack, to confirm that an edge cache is behaving as expected. They are not used to build a profile of a reader or to decide which article to promote.
Contact-form submissions are used to reply to you and, where you gave an explicit example that improves one of our pages, to improve the article you referred to. We do not use the content of your message to send you unrelated communications; we do not share it with Tenobet or any other operator unless you asked us to forward it.
We never sell personal data. We never trade personal data in exchange for services. If a vendor we use (hosting, email, anti-spam) requires access to the data to perform its service, that access is covered by a data-processing agreement that forbids further use.
Our hosting provider processes the usual network metadata on our behalf. Our outbound mail provider processes the content of a reply we send to you. Our anti-spam filter sees the content of inbound mail. These are the three categories of processor we rely on; each operates under a written data-processing agreement that constrains them to our instructions.
We do not run third-party advertising on this site, we do not embed social-media widgets, we do not load pixels from analytics suites, and we do not include tag managers. If a third-party request appears in your browser developer tools while you load one of our pages, it is either (a) the fonts loader, (b) the asset CDN of the hosting provider, or (c) a mistake we would appreciate you reporting.
A reader-initiated click to «Play now» leaves our site and enters Tenobet's own property. From that point onward, you are subject to the operator's privacy notice, not ours. We have no visibility into what happens inside the Tenobet platform and we do not receive personal data back from Tenobet beyond anonymous commission-level reports.