What the browser stores in this release

1. What cookies and storage are

Cookies are small pieces of data a website can ask a browser to store and send with later requests. Browsers also provide localStorage and sessionStorage, which can store values on the device without sending them automatically with each HTTP request.

2. Current storage used by Sarnio

The current front-end uses sessionStorage for one simple preference: remembering that the visitor acknowledged the site's basic cookie/storage notice during the current browser session. That value is named sarnioCookieNotice and is not designed to identify the visitor.

PHP sessions may set a necessary session cookie so the contact form can use a CSRF token and basic anti-abuse timing. The exact cookie name is determined by the PHP environment, commonly PHPSESSID. It is used for security and form continuity rather than analytics or advertising.

3. Consultation-preparation checklist

The interactive checklist on the consultation guide operates only in the page's current DOM state. The supplied JavaScript does not save the selected health-preparation prompts to cookies, localStorage or sessionStorage and does not send them to the server.

4. Analytics

No GA4 Measurement ID is configured, so Google Analytics is not loaded by the supplied site. There are no analytics cookies created by Sarnio's code in this release.

5. Google Tag Manager

No GTM Container ID is configured. The supplied templates do not insert GTM or a GTM noscript iframe while the configuration field is empty.

6. Cookiebot or other consent platforms

No Cookiebot Domain Group ID is configured. Sarnio therefore does not claim Cookiebot is active. The small in-house notice describes the limited storage actually used by the current code.

7. Advertising and affiliate cookies

No advertising pixel, affiliate tracking cookie, partner click identifier or external sales link is implemented in this release. The site's declared affiliate business model does not by itself create a browser cookie.

8. reCAPTCHA

No reCAPTCHA site key is configured. The contact form instead uses server-side CSRF protection, a hidden honeypot field and simple rate limiting. If reCAPTCHA is added later, the cookie/privacy documentation should be updated first.

9. Google Maps

Google Maps is not embedded. The supplied address is shown as plain text only, so the page does not intentionally load Google Maps resources or mapping cookies.

10. First-party and third-party storage

The current necessary PHP session and sessionStorage acknowledgement are first-party in the sense that they relate directly to use of sarnio.guru. No intentionally configured third-party analytics, advertising or map storage is active.

11. Duration

The notice acknowledgement stored in sessionStorage generally lasts until the relevant browser tab or session is closed, subject to browser behaviour. PHP session-cookie duration is controlled by the server's session configuration and may expire at the end of the browser session or earlier/later depending on the host's settings.

12. Managing storage

You can clear website data using your browser's privacy or site-data controls. Blocking necessary session cookies can prevent the contact form's security token from working correctly. Blocking sessionStorage may cause the notice to reappear more often.

13. Consent and necessary storage

The current site does not condition access to health information on accepting analytics or advertising because those categories are not active. If non-essential technologies are added later, consent logic should be designed to meet applicable Kenyan data-protection requirements before those technologies run.

14. Future changes

If GA4, GTM, Cookiebot, reCAPTCHA, advertising pixels or affiliate tracking are enabled, this Cookie Policy must be updated to identify the technology, purpose, provider, duration and available controls.

15. Contact

Questions about site storage can be sent to [email protected].