This policy describes what happens to information when you visit Daily Lab Dish. It is deliberately short because we collect very little.
What we collect
Our web server records standard request logs: the requesting IP address, the page requested, the time, the referring page and the browser user agent. These logs exist to keep the site running, to investigate abuse, and to measure advertising as described below. They are retained for a limited period and then deleted.
We do not require an account to read anything here, and we do not ask for personal details to access articles.
Analytics and session recording
We use Microsoft Clarity to understand how people actually use the site. Clarity records how pages are used, aggregating that into heatmaps and session replays: which links are clicked, how far people scroll, where they hesitate, and where a page fails them. This is behavioural data about page interactions, not a record of who you are.
Clarity is provided by Microsoft, so this data is processed on Microsoft infrastructure and is subject to Microsoft’s own privacy terms as well as this policy. Clarity applies masking to text input fields by default, so what you type into a form should not be captured. We use it to improve the site’s structure and readability, not to build an advertising profile, and we do not sell or share the data with advertisers or data brokers.
Advertising measurement
We advertise some articles on Meta’s platforms, which include Facebook and Instagram. To measure whether those advertisements work, our server sends Meta a record of page views using Meta’s Conversions API. That record contains the address of the page viewed, the time, your IP address, your browser user agent, and, if you arrived by clicking one of our advertisements, the click identifier that Meta attached to that link.
This happens entirely on our server, after your page has already been delivered. We do not load Meta’s tracking script in your browser, so no third-party advertising code runs on this site and nothing about this measurement slows the page down.
We do not send Meta your name, email address or any other detail that identifies you personally, because we do not hold any. Meta processes what we send under its own terms and may use it to attribute advertising activity. Blocking scripts in your browser will not prevent this, because it does not happen in your browser; if you would rather not be measured this way, the controls Meta offers over advertising data in your own account settings are the effective route, and you can also avoid arriving through our advertisements.
Cookies
The site itself does not set advertising cookies from third parties. Microsoft Clarity sets cookies to recognise a returning session so that activity can be stitched into a single replay. If you arrive by clicking one of our advertisements, our own server stores the Meta click identifier in a first-party cookie so that later page views in the same visit can be attributed to that advertisement. WordPress may also set functional cookies if you leave a comment or log in to an account, which applies to our editorial team rather than to readers.
Third parties
Aside from Microsoft Clarity and the Meta advertising measurement described above, we do not embed third-party trackers, social widgets or advertising scripts. Pages may reference external organisations by name, but naming them does not report your visit to them.
Your rights and contact
Depending on where you live, you may have rights to request access to or deletion of information relating to you. Given that we hold little more than transient server logs and pseudonymous interaction data, there is usually very little to retrieve. Contact us through the contact page with any request and we will respond.