This site has no account, no form, no payment and no newsletter. There is nothing here for you to fill in, so there is almost nothing to collect. What remains is analytics, which is off until you say otherwise, and the server logs any website keeps. Both are described below in the specific rather than the general.
Measured in a real browser on 4 August 2026, loading a page of this site makes requests to exactly two hosts that are not this one, and both belong to Google: www.googletagmanager.com and www.google-analytics.com. That is the complete list.
Worth stating what is not on it. Every photograph on this site is a file served from this domain, so your browser never contacts a stock-photo library or an image CDN. There are no web fonts loaded from a font service, no embedded videos, no social widgets, no advertising network, no chat popup and no A/B testing tool.
Beyond that, this site is hosted by Vercel, so Vercel's servers handle the request and keep the ordinary access logs a web server keeps, which include your IP address. That is a condition of the site existing rather than a choice about you.
This site uses Google Analytics 4, measurement ID G-NYN8K5B9Z1, behind Google Consent Mode v2. Before you answer the banner, all four consent signals are set to denied, and two of them are never granted by anything on this site at all.
| Signal | Before you answer | If you allow analytics |
|---|---|---|
| analytics_storage | denied | granted |
| ad_storage | denied | denied, always |
| ad_user_data | denied | denied, always |
| ad_personalization | denied | denied, always |
There is no "Accept all" on the banner because there is nothing else to accept. The three advertising signals have no path to granted in this site's code, so agreeing to analytics does not quietly agree to ad targeting.
If you allow analytics, two cookies are set: _ga and _ga_NYN8K5B9Z1. They give you an identifier that persists between visits so that two page views can be recognised as one visit. Verified on the live site: with an empty cookie jar and no answer given, no cookies are set at all.
If you decline, no cookie is set and no identifier persists.
Consent Mode works by loading Google's script immediately and telling it what it may not store. So on your first page view, before you have touched the banner, one request does reach Google. It carries your IP address and the address of the page you are on. It does not set a cookie and it does not create an identifier that follows you.
This is how Google designed the mechanism, and it is still a request about you that you did not agree to, so this page says so instead of describing the banner as though nothing happens until you press a button.
One consequence deserves naming directly, because it is specific to a site about medical screening. A page address on this site can be revealing on its own. /tests/colonoscopy/ says what you were reading about. If that matters to you, the reliable protection is not the banner, it is a browser that blocks the request: any tracker-blocking extension, Firefox's strict mode, or Safari with cross-site tracking prevention will stop it before it leaves your machine.
Your choice is kept in your own browser's local storage under the key medi-consent, holding one word, granted or denied. It is not a cookie, it is never sent to this site or to anyone else, and clearing your browser's site data removes it, after which the banner asks again.
You can change your mind at any time.
That button needs JavaScript, which is also what analytics needs. With scripting off, there is no analytics to consent to and nothing for the button to change.
This is a gap, and labelling it is better than papering over it. The contact page carries no email address, phone number or form, because none is live. Nothing you send can be collected here, because there is nothing here to send it to.
When that channel opens it will handle a different category of information from anything described above. Arranging a screening means discussing what you want examined, and that is health information rather than a page view. It deserves its own commitments about who reads it, where it is stored, how long it is kept and when it is deleted, and those commitments belong on this page before the channel exists rather than after. They are not written yet.
The same applies to the rights you have over data about you, including asking what is held, asking for it to be corrected or deleted, and withdrawing consent. Withdrawing analytics consent works today, with the button above. The rest requires somewhere to send the request, and that is the missing piece.
Google processes the analytics described above under its own privacy policy, and Vercel handles the hosting and its access logs under theirs. Neither is a document this site controls, and both are worth reading if the summary above is not enough.
Last updated 4 August 2026. Every claim on this page was checked against the deployed site on that date, not against an intention. If the site changes what it loads, this page is wrong until it is updated, so it carries a date for the same reason every figure on this site does.