COOKIES
Cookie & Local Storage Policy
A plain description of what this build actually stores and what is not currently configured.
Last updated: 6 October 2026.
1. Current implementation
The current site uses a lightweight preference banner. When you choose “Essential only” or “Accept all”, the selection is stored in your browser using localStorage under a site-specific preference key so the banner does not reappear on every page.
2. Analytics and advertising
No GA4 ID, GTM container ID or advertising integration was provided for this build. Those services are therefore not loaded. “Accept all” does not silently activate analytics that has not been configured.
3. Cookiebot and reCAPTCHA
No Cookiebot Domain Group ID and no reCAPTCHA site key were provided. Fake identifiers are not used and related scripts are not loaded.
4. Essential server data
The hosting environment may set technical cookies or generate server logs necessary for security, load balancing or session management. The actual hosting stack was not supplied, so this policy does not claim a specific cookie name or provider.
5. Changing your choice
You can clear this site’s local storage using your browser settings. After clearing it, the preference banner will appear again. Browser controls may also allow you to block cookies or site storage more broadly.
6. Future changes
If analytics, affiliate tracking, advertising, embedded maps, captcha or other non-essential technologies are added, the consent mechanism and this policy must be updated to accurately describe the new processing before those tools are activated where consent is required.
7. What “essential” means here
Essential storage is limited to functionality that is reasonably necessary for the site to remember a preference or operate safely. The current preference key does not contain your name, email address, health information or message content. It records only the category of consent selected in the browser.
8. Third-party embeds
No third-party video player, social-media embed or map is intentionally loaded by this build. If embedded content is introduced later, it may set its own cookies or make requests to another provider and must be evaluated before deployment.
9. Consent records
This lightweight banner stores the choice locally in the browser; it does not create a central consent database. If the operator later requires auditable consent records for analytics or advertising, an appropriate consent-management implementation should be configured using real production identifiers.
10. Browser controls
Browsers usually allow users to inspect, clear or block site data. Blocking all storage may cause the preference banner to reappear because the website cannot remember the previous choice. Browser settings are independent of the site’s own banner.
11. Relationship to the Privacy Policy
This Cookie Policy should be read together with the Privacy Policy, which explains contact-form data, server logs, possible service providers, international transfers and data-subject rights.
12. Contact
Questions about storage technologies on pryntor.store may be sent to [email protected].