Skip to main content

Cookie policy

Which cookies and similar techniques the Sanabil Foundation website uses, why, which ones need your consent, how Instagram and TikTok posts are shown, and how to change your choice.

Current cookie information — 17 October 2026

This dated notice supersedes any earlier statement on this page where the two differ.

The HTTP-only sanabil_session cookie supports sign-in for the configured session period (normally 30 days) and is cleared on logout. The HTTP-only snb_csrf security cookie lasts for the browser session. The snb_public_locale and snb_admin_locale cookies remember your language for one year. The browser stores the cookie choice as snb_cookie and the aggregate-count choice version as snb_aggregate_consent in localStorage. These choices are not a visitor identifier.

The signed, HTTP-only snb_payment_resume cookie keeps a payment kind and reference for 24 hours so an interrupted donation, event or invoice checkout can be resumed. It does not store a card number or mean a payment succeeded.

With Statistics only or Accept all, optional server counters may record public page views and fixed form-action totals when enabled; daily aggregate totals are kept for 90 days without a visitor ID or form contents. Google Analytics loads only when configured and you choose Accept all. It is excluded from signed-in, account, payment, receipt, private-link and search pages; query strings and incoming referrer URLs are not sent in the page configuration. Global Privacy Control and Do Not Track stop optional counting. Necessary security logs are separate from optional statistics.

Instagram and TikTok players load with Accept all or when you separately allow a player. Loading a player sends technical data, including an IP address, to that provider. Essential only and Statistics only do not permit these optional players.

When configured, reCAPTCHA loads when you interact with a protected form, for security and fraud prevention, before any optional cookie choice. Reading a page alone does not load the v3 challenge. Google then receives technical request and device data and can set its _GRECAPTCHA security cookie when the check executes. It is separate from optional analytics consent; the exact deployed product and contractual terms require verification.

Use Cookie settings in the footer to choose again or withdraw optional consent. Withdrawing stops future optional loading and counting. A third-party player or script that already loaded cannot be recalled from that provider; reload the page after changing choices to stop further loading.