Cookie and Similar Technologies Notice
Version 5 draft for legal review
Updated 9 November 2026. The effective date and identity details are recorded as accepted by VIVA. Current technical settings have been checked on both review installations. Yellow CONFIRM notes use the same IDs as Appendix B in the Word review file and identify remaining decisions or proposed wording. Repeated IDs refer to the same item. This staging copy remains for legal and operational review.
VERSION 5 DRAFT FOR LEGAL REVIEW – 9 November 2026. Yellow CONFIRM notes identify open decisions in Appendix B. Verified configuration and internal VIVA tasks are recorded there. This draft is not approved for production publication.
Last updated: 9 November 2026
Effective from: 1 November 2026
On this page
What this notice covers
Cookies are small values saved by a website in your browser. We also use browser storage to remember choices and support functions you request. Similar technologies can include scripts, pixels or embedded content. This notice explains their purposes, duration and your choices. Our Privacy Notice explains who is responsible and how to contact us.
This notice is part of the Armenian, EU/UK and conditionally applicable California review described in our Privacy Notice. We distinguish storage needed for a requested function from optional analytics, marketing or other services. We ask for consent before optional technologies are used where consent is required. Browsing, scrolling or continuing to use the site does not count as consent.
Your choices
Use Cookie settings in the website footer to review purposes, reject optional technologies, accept selected purposes, or withdraw an earlier choice. Refusing optional technologies does not prevent an ordinary donation or enquiry.
Cookie settings opens the CookieYes panel. It remembers your choice for 365 days. Optional categories start off; empty categories have no individual switch. Its controls apply to connected technologies and do not block the separate external deliveries listed below.
Essential session or security storage cannot be switched off through optional-consent controls because it supports the function requested. You can block or remove storage in your browser, but doing so may sign you out or prevent that function working.
Storage used for website functions
| Name or type | Provider and purpose | Duration | When used |
|---|---|---|---|
cookieyes-consent | VIVA’s CookieYes manager; remembers your privacy choice | 365 days from creation or the latest rewrite | When the manager initialises or saves/changes the choice. |
viva_donation_access | VIVA; maintains a verified guest session to manage gifts | One hour in the current implementation | After a secure email-access link is redeemed. |
WordPress authentication/session cookies, including wordpress_logged_in_* and relevant secure-auth cookies | VIVA; supports sign-in and account security | Without Remember me: browser-session cookie, with server authentication valid for two days. With Remember me: authentication valid for 14 days; browser cookie expiry includes an additional 12-hour grace window. Signing out clears the login cookie. | When an account user signs in. |
wordpress_test_cookie | VIVA; checks browser cookie support | Browser session | During login. |
vivaDonationChoice in session storage | VIVA; remembers amount, currency and frequency while you use the donation form | Browser tab/session lifetime; browser session restoration can preserve it | While making donation choices. It does not store your name, email or card credentials. |
viva.theme.v1 in local storage | VIVA; remembers a selected light/dark display preference | Until cleared or overwritten; the current code sets no fixed expiry | After you choose a display theme. |
cya11y-user-settings in local storage | Accessibility widget; remembers your settings | Until cleared or overwritten. The current fallback cookie does not persist. | After you save accessibility settings. |
Display and accessibility preferences are intended to serve the choice you make. [CONFIRM R06.01: confirm storage exemptions or consent treatment.]
Optional services and third parties
[CONFIRM R06.03: confirm external-delivery notices and consent treatment.]
Separate off-site forms and other collection routes need their own privacy information. [CONFIRM R03.05/R08.05: finalise separate collection notices; finalise separate assistance information.]
| Service | Information and purpose | Duration and choice |
|---|---|---|
| Hostinger Reach | The remote review site loads cdn-reach.hostinger.com/js/embed.js before a cookie choice, disclosing network request information to Hostinger. No connected Reach subscription form or extra Reach browser storage was observed. | No Reach cookie/storage lifetime was observed. Provider request-log retention is separate. |
| Audience measurement | No analytics provider, cookie or analytics endpoint was observed on the checked published pages. | No analytics lifetime is currently configured. |
| Advertising or cross-site tracking | No advertising pixel or cross-site advertising service was observed on the checked published pages. | The California Privacy Notice addresses sale/sharing classification and any required opt-out. |
| Embedded videos, social content or other third-party content | No external video or social iframe was found on the checked published pages. Ordinary external links contact the destination when followed. | No embedded-player storage lifetime is currently configured. |
| Consent, accessibility and icon assets | CookieYes and AccessiYes assets were served locally. Some posts fetch WordPress emoji images from s.w.org, disclosing network request information. | Local assets follow hosting log arrangements; external icon-provider logs have separate retention. |
When you follow an ordinary external link, the destination handles information under its own notice. An embedded service can receive information while our page is open, so we assess embeds separately.
The bank’s hosted payment page may use its own session and security technologies. Ameriabank’s notice governs its use there; rejecting optional VIVA technologies does not waive the bank’s separate responsibilities.
How these choices differ from other requests
A cookie choice applies to the browser purposes and technologies actually connected to the consent manager. It does not cancel a recurring gift, close an account, erase an accounting record or by itself withdraw a separate permission to publish a story or send fundraising messages. Use Privacy Choices and Privacy Requests and Complaints for those actions.
[CONFIRM R06.05: finalise required California signal handling.]
Browser privacy signals
Legacy Do Not Track (DNT) and Global Privacy Control (GPC) are different signals.
The legacy DNT signal did not change the tested cookie categories or external asset requests. The current site provides its cookie-choice controls rather than a separate automatic DNT response.
The current review site has no separate sale/sharing opt-out or account-linked Global Privacy Control (GPC) flow. [CONFIRM R06.05/R06.06: finalise required California signal handling; confirm category-specific sale/sharing and history.]
Read the California collection notice and definitions of sale and sharing, the California rights section, and the Privacy Choices page for available controls.
Changing or removing storage
You can revisit Cookie settings, change the display/accessibility choices, sign out, or clear site storage in your browser. Clearing storage may also remove your saved privacy choice; you may be asked again on your next visit.
Withdrawal stops future optional use covered by that choice. It does not undo processing that was lawful before withdrawal. Where appropriate, use our privacy request route to ask about information already collected.
We update this notice when our technologies or purposes change and seek a new choice where required.
