Cookies and storage
Across almost the whole site there are no cookies and no third parties. There is one deliberate exception — the contact page, which loads Google reCAPTCHA to stop spam. Everywhere else, the site stores just two things in your own browser, both only after you do something that asks for them, and neither is shared with anyone.
Cookies
On every page except one, there are none. Not first-party, not third-party, not analytics, not
advertising. Those pages never write to document.cookie, and you can verify it: the
site is a few static files, and the only script of its own is assets/app.js.
The exception is the contact page. To keep the form from being flooded by bots it loads Google reCAPTCHA, which sets a cookie of its own. It is set by Google, not by this site — this site can neither set nor read it — and only on that page, only because it carries a form. If you never open the contact page, you never meet it.
- _GRECAPTCHA — Google, contact page only
- Set by Google reCAPTCHA to tell humans from bots and stop spam through the form. It is a Google cookie, governed by Google's privacy policy, and typically lasts several months. It is not set unless you open the contact page, and this site never reads it.
That is the only cookie anywhere on the site, and the only place any data leaves for a third party. If you would rather it never load, simply do not open the contact page — everything else works with no cookies and no third parties at all.
What is stored in your browser
Two entries in local storage, which is a private area of your own browser. It is not sent to the server with requests the way a cookie is — it never leaves your machine.
- peptidex-theme
- Remembers whether you chose the light or dark theme. Written only when you press the theme button. Kept until you clear it.
- peptidex-age-verified
- Records that you confirmed you are 18 or over, so you are not asked again on every page. Written only when you press that button. Holds a date, nothing about you, and expires after 90 days.
That is the complete list. Neither identifies you, neither follows you between sites, and neither is readable by anyone else.
Analytics
Checking what is configured…
If analytics is ever switched on here it will be the cookieless kind wherever possible — aggregate page counts with nothing stored on your device and no cross-site tracking. Anything that does set a cookie or build a per-visitor profile will ask before it runs, not after, and declining will be exactly as easy as accepting.
Third parties
There is one, and only on the contact page: Google reCAPTCHA, which the form uses to block spam. It loads a Google script and sends data to Google under Google's privacy policy. Everywhere else there are none — no tag managers, no embedded video, no social buttons, no advertising, no hosted fonts and no content delivery network; every stylesheet, script, image and font is served from this domain or is already on your device.
Links to research publications point to sites such as PubMed and journal publishers. Following one takes you to them and their own policies apply there, as with any link.
Server logs
Worth stating plainly because it is true of every website: the host serving these pages keeps ordinary access logs, which typically record IP address, time, the page requested and your browser's user-agent string. That is a function of the hosting, not something this site adds, and it is not used to build a profile of you.
Removing it
Clearing site data for this domain in your browser settings removes both entries immediately. Private or incognito windows discard them when you close the window. If storage is blocked entirely the site still works — you will simply be asked to confirm your age again, and the theme will follow your system setting.
If this changes
If anything is ever added that tracks visitors or sets a cookie — analytics being the obvious candidate — this page will say so, and it will ask for your consent before it runs rather than after. Nothing of that kind is present today.