In short
- No cookies, no tracking scripts, no advertising trackers, no accounts and no newsletter. Visits are counted only in aggregate, on the server.
- The checker runs in your browser. The article text you paste is not sent to us.
- Only two things ever leave your browser through the checker: an address you ask it to fetch, and an access code check. Both are described below.
- Book purchases happen on Google Play, under Google's own policy.
No patient data. This site does not accept patient data. Do not paste identifiable patient information, such as names, dates of birth, record numbers or photos, into the checker or send it by email.
Who is responsible
The controller for this site is Niyazi Umut Özdemir, MD. For any privacy question or request, write to info@uzclinic.com. This site is run separately from the author's clinical practice.
Hosting
This is a static website hosted by Netlify. Like most hosting providers, Netlify may keep technical server logs when a page is requested, which can include your IP address, browser type, the page requested and the time of the request. These logs are handled by Netlify for operating and securing the service, under Netlify's own privacy policy. We do not use them to build profiles of visitors.
To see how much the site is used, we use Netlify's server-side analytics. It counts page views, approximate visitor numbers, referring sites and countries in aggregate from those same server logs. It adds no script and no cookie to the pages, and we see only totals, never individual visitors.
What this site does not do
- It sets no cookies.
- It adds no analytics or tracking scripts to its pages and uses no advertising or social media trackers.
- It has no user accounts, contact forms or mailing list.
- It does not sell personal information, and it does not share it for targeted advertising.
The checker
Article text. The audit runs inside your browser. The text you paste is analyzed on your device and is not sent to our servers.
Fetching a published page. If you ask the checker to fetch a page by its address, only that address is sent to a Netlify function. The function fetches the public page and returns it to your browser. Nothing is stored.
Access code. When you enter the access code from the book, the code and a random device identifier are sent to a Netlify function to check whether the code is valid. The device identifier is generated in your browser; it is not linked to your name, email or payment. Each activation is recorded in Netlify Forms with the code, the holder label attached to the code if there is one, the random device identifier and a timestamp. We use these records only to see how many devices use a code and to manage access codes.
The link checker and the AI visibility test
Link checker. When you check a link, the address of the page that is said to link to you is sent to the same Netlify function, which fetches the public page and returns it to your browser. The search for your link runs in your browser. When you use "Re-check all" in the link ledger, the pages in your ledger are fetched the same way, one after another. Nothing is stored on our side. If you paste a page's source instead, it is analyzed in your browser and not sent anywhere.
AI visibility test. The questions are built in your browser from the details you type (specialty, topic, city, and optionally a name). The tool does not send them to us or to any AI service; you ask them yourself. Your marks, saved profiles and monthly measurements are not sent to our servers.
Both tools check the access code the same way the checker does, as described above.
Stored in your browser
The three tools keep a few small items in your browser's local storage, all starting with
mv_: the access code you entered and its holder label, the random device identifier,
your region choice for the advertising rules scan, a counter for PDF reports, short fingerprints
of pages you fetched, so the checker can tell you whether a page changed since your last audit,
the questions the checker hands over to the AI visibility test, your link ledger, and your AI
visibility profiles and measurements. The ledgers can be exported to a file and imported again,
for example to move them to another device. These items stay on your device. You can remove them at any time by clearing this site's data in
your browser settings.
Buying the book
The book is sold only on Google Play Books. Purchases, payment and any account details are handled by Google under Google's own terms and privacy policy. We do not receive your payment details.
Legal basis
Where the EU or UK General Data Protection Regulation applies, we rely on legitimate interests to run and secure the site, to answer the requests you send us, and to manage access codes. Where you write to us, we use your email only to reply.
How long we keep information
Activation records are kept only as long as they are needed to manage access codes. Emails are kept only as long as needed to handle your request. Hosting logs are kept by Netlify according to its own retention practices.
International transfers
Netlify and Google are based in the United States and may process data in the United States and other countries. Where the law requires it, these providers state that they use recognized safeguards for such transfers.
Your rights
Depending on where you live, you may have the right to ask for access to the personal information we hold about you, to have it corrected or deleted, to restrict or object to its use, and to receive it in a portable form. In the European Economic Area and the UK you may also complain to your data protection authority. Several US states give similar rights to know, correct and delete, and the right to opt out of the sale or sharing of personal information; we do not sell or share it.
To make a request, write to info@uzclinic.com. Because the checker does not collect names or emails, we may need the random device identifier stored in your browser to find a record. We will not treat you differently for using your rights.
Children
This site is written for health professionals and is not directed to children.
Changes
If this notice changes, the new version will be posted on this page with a new date.
Last updated: September 29, 2026