Privacy policy
Last updated: September 8, 2026
Diabetes Academia is a diabetes handbook written in plain language for patients, free of charge and free of advertising. We built it on a simple principle: the best protection for your data is not to collect it at all. You can read any page without an account, without subscribing and without telling us who you are.
In short
- We do not ask for and do not store your name, e-mail address or any other identifying data.
- We use no tracking cookies, marketing pixels or ads.
- We keep only aggregate access counts on our hosting servers (the page visited, the day, the referring site and the technical protocol version), with no cookies, no IP addresses and no personal identifiers of any kind.
- When you vote under an answer we again keep only an aggregate counter (the day, the page, the question, the language and the choice), with nothing that identifies you (details in section 6).
- There are no user accounts, newsletters or comments.
- We load nothing from third parties on our pages: no external fonts, no social media buttons.
- The contact form is anonymous by design: we save only the text of your message, the language, the page it came from and the time it was sent (details in section 5).
- What you read on this site stays between you and your browser: the access counts show how many times a page was opened, not who read it.
1. Who operates this site
The website diabetesacademia.com is created and run by Assoc. Prof. Dr. Sorin Ioacara, senior consultant diabetologist, for exclusively educational purposes. For the purposes of data protection law (EU Regulation 2016/679 — the GDPR), the controller of this website is Assoc. Prof. Dr. Sorin Ioacara.
For any question about this policy you can write to us through the contact page. The form is anonymous — if you expect a reply, include a way to contact you in your message.
2. Data we do NOT collect
The site has no accounts, no log-in, no subscriptions, no payments, no comments and no forms that ask for personal data. As a result, we do not collect or store:
- names, surnames or identifying details;
- e-mail addresses or phone numbers — we never ask for them (if you voluntarily include a contact in your form message, see section 5);
- medical data or information about your health — everything you read stays in your browser;
- your browsing history on other websites;
- precise location data.
We do not use Google Analytics or any other traffic-analysis service, we show no ads and we embed no social networks in our pages. The pages load no third-party resources; every file (text, styles, images) comes from our own domain.
3. What happens technically when you visit the site
The site is hosted on Cloudflare's infrastructure (Cloudflare, Inc.), which delivers the pages and protects the site from cyber attacks. As with any website, when your browser requests a page, the server briefly processes technical connection data (your IP address and information about your browser) strictly to deliver the page and keep the site secure (for example, protection against DDoS attacks). This processing is transient and is based on the legitimate interest of keeping the site working and safe.
We do not receive, access or store this data at an individual level; the statistics we see are aggregated (for example, the total number of visits), with no way to identify a person.
In rare cases, when the security system suspects automated behavior (a bot), Cloudflare may show a
security check that sets a strictly necessary cookie (for example cf_clearance). Its
role is exclusively security, not tracking or marketing, and it expires automatically.
Cloudflare, Inc. is based in the United States, so the technical processing described above can also take place outside the European Economic Area. The transfer is covered by the European Commission's standard contractual clauses and by Cloudflare's certification under the EU–US Data Privacy Framework.
The monthly database backups are kept for at most 90 days in the author's account at GitHub, Inc., also in the United States, under the same safeguards.
4. Site search
When you use the search box, the text you type is sent to our server only to return the relevant pages from this site. The search is processed by the Cloudflare AI Search service on our behalf. The query is not linked to your identity, we attach no identifier to it and we build no profiles based on your searches.
5. The contact form
The contact form is designed to be completely anonymous: it has no required name or e-mail fields, and when you submit it we save only:
- the text of the message you wrote;
- the language the site was displayed in;
- the page you sent the message from (just the page address, no other details);
- the date and time it was sent.
We do not save your IP address, browser identifiers or cookies together with the message. For this reason, messages cannot be linked to you — not even by us. Please do not include medical information about yourself in the message. If you expect a reply, you may include a way to contact you (for example, an e-mail address) — we use it solely to reply to you, and it is deleted once the message is processed. Any details included in the text are stored as part of the message until it is processed.
Messages are deleted no later than 12 months after they arrive, through a monthly scheduled deletion. Aggregate visit statistics, which contain no personal data, are kept indefinitely.
6. The rating under each answer
Under every answer in the articles there is a bar with the question "Did this answer your question?" and three choices — No, Partly and Yes. The vote is anonymous by design, just like the contact form. When you press a button we add one to an aggregate counter and keep only:
- the day you voted, without the exact time;
- the page and the question you voted on;
- the language the site was displayed in;
- the choice you made.
We do not save your IP address, browser identifiers or cookies together with the vote. Two identical votes sent on the same day from the same page cannot be told apart, so the counter cannot be linked to a person, not even by us.
The bar appears only if your browser has JavaScript enabled, and the vote is sent only after you press a button. Aggregate counters, which contain no personal data, are kept indefinitely. What we do with the votes, and what they do not change, is described on the Editorial policy page.
7. Links to other websites
The articles contain bibliographic references to external scientific sources (for example PubMed) and links to international guidelines. Those websites have their own privacy policies, which we cannot control.
8. Children and teenagers
The site is written for patients and their families, including the parents of children with diabetes. We do not knowingly collect data from anyone — neither adults nor minors. The content can be read safely at any age without leaving personal data behind.
9. Your rights
The GDPR guarantees your rights of access, rectification, erasure, restriction, objection and portability over your personal data. Because the site neither asks for nor stores identifying data, these rights have, in practice, almost nothing to apply to here: there are no accounts or profiles for us to access, correct or delete on request. The one exception is the text of a message sent through the contact form, if you voluntarily included personal data in it (section 5).
If you nevertheless believe your rights have been infringed, you can write to us through the contact page and you can contact the data protection authority in your country of residence, or the Romanian supervisory authority (ANSPDCP) — www.dataprotection.ro.
The form is anonymous by design, so we can only reply if you voluntarily include a way to contact you in the message. When you do, we reply within 30 days of receiving it.
10. Changes to this policy
If the way the site works changes (for example, we add a new feature that processes data), we will update this page before the change takes effect and we will update the "last updated" date at the top. We will never lower the level of protection described here without announcing it explicitly on this page.