A small technical footprint
Dulavero does not load advertising cookies, analytics trackers or social-media pixels. Its scripts and style libraries are served locally. Browsing an article does not require a personal profile or sign-in.
The contact session
Opening the Contact form requests a security token from its PHP endpoint. A necessary session cookie links that token to your browser session. The session helps reject forged submissions and repeated messages sent too quickly. Blocking this cookie can prevent the form from working.
An optional notice preference
Privacy choices lets you ask the browser to remember that you have read the notice. This is stored locally under a Dulavero-specific preference key. It contains a simple choice, not your message or role-reader text. Unticking the option and saving removes that record.
What the reader does not keep
The interactive role reader does not use local storage or a server account. Its pasted text and annotations exist only in the current page. Clearing the tool or reloading the page starts a new reading.
Managing your browser
You can also remove cookies and website data through your browser settings. Doing so may end a contact-form session and remove your saved notice preference. It does not delete a message already stored on the server; ask about that separately through Contact.
External destinations
Following a link to an official learning or help page leaves Dulavero. That page may use different cookies and controls. Review its own information if you choose to use it. This description was prepared for the site’s current implementation on 29 October 2026.