Legal
This Cookie Policy explains how VovoCare uses cookies and similar technologies on its website and platform.
Cookies are small files placed on your browser or device that allow a website to recognize your device and store certain information.
Depending on their purpose, cookies may be used to:
VovoCare uses cookies only for legitimate website and platform purposes, such as keeping the site working properly, remembering user preferences, improving reliability, and, where enabled, understanding how the site is used.
Some cookies are essential to the operation of the site. Others are optional and may be used only if you choose to allow them.
VovoCare may use cookies and similar technologies for the following purposes:
These cookies are required for the website or platform to function properly. They may be used for things such as:
These cookies help remember settings you choose, such as language or interface preferences, so that your experience is more consistent across visits.
Where used, these cookies help VovoCare understand how visitors use the website, which pages are viewed, whether errors occur, and how the site can be improved.
These cookies are used only where permitted and, if legally required, only after consent has been obtained.
If website measurement is enabled and you accept all cookies, Google Analytics 4 (when configured) measures visits; the screens, form steps, errors and key actions used; and registration, care-request and paid-booking steps. We send only route templates and predefined event codes, not names, contact details, care-request contents or authentication tokens.
If website measurement is enabled and you accept all cookies, Google Ads measures advertising visits and successful care-request publication. Google cookies may retain advertising click attribution. Ad personalization and enhanced conversions are not enabled by this implementation. Google tags are blocked before consent and when you choose essential cookies only.
Depending on the final technical implementation of the site and platform, VovoCare may use cookies or similar storage technologies for:
Some cookies may be placed by third-party service providers that support the operation of the website or platform. For example, these may include hosting, analytics, embedded content, or communication tools.
VovoCare seeks to use trusted providers and to limit third-party tracking where possible. Where third-party cookies are non-essential, they should only be used in accordance with applicable consent requirements.
Cookies may remain on your device for different periods of time:
Use Cookie settings in the footer to accept all cookies or switch to essential cookies only at any time. Optional measurement stops when you withdraw consent. Existing Google cookies may remain until they expire or you delete them in your browser. You can also control cookies through your browser settings:
VovoCare may update this Cookie Policy from time to time to reflect changes in legal requirements, technical setup, or the tools used on the site. When material changes are made, the revised version will be published on this page with an updated effective date.
If you have questions about this Cookie Policy or about VovoCare’s use of cookies and similar technologies, you may contact: privacy@vovocare.org
Last updated: 7 October 2026
When website measurement is enabled, Google Analytics 4 (GA4), if configured, measures website visits, family registration start and verified activation, care-request start and successful publication, and observable paid-booking confirmation and accepted completion. Booking events depend on a consenting visitor returning to the family dashboard and the application observing the backend payment or completion state; they may be delayed or missed and are not a complete payment record. Google Ads, when enabled, measures advertising attribution and successful care-request publication; registration and paid-booking events are sent only to GA4.
GA4 also measures how the website is used, so we can find and fix the points where people get stuck: the screen, tab, dialog, form section or empty or error state shown (as a fixed screen code); moves between screens; form progress (a section shown, started or completed, a submission and its confirmed result); why a form or action could not continue (a fixed field and error code, such as a missing date or an unavailable time slot); and the use and confirmed outcome of key actions such as applying for a job, selecting a caregiver, starting payment, cancelling, confirming or disputing a completed service and leaving a review. Each event also includes the account type (family, caregiver or not signed in), the site language, the screen layout (compact or wide) and the website release. Staff and administrator accounts are not measured.
Optional measurement relies on your consent (Article 6(1)(a) GDPR and applicable cookie rules). Google tags are blocked before acceptance and with essential-only consent. Accept all cookies permits the enabled measurement services. Advertising personalization, Google Signals and enhanced conversions are disabled by this implementation.
You can withdraw consent at any time through Cookie settings in the footer by choosing essential cookies only. Withdrawal stops future optional application measurement and does not affect earlier lawful processing. Existing Google cookies may remain until expiry or browser deletion. Optional measurement consent is not required to register, publish a request or make a booking.
Google receives pseudonymous cookie/client and session identifiers, device and browser information (such as operating system, browser type, language and screen information), event names and timing, and consent state. Connections to Google expose the IP address and HTTP/browser information; for EU, Swiss and UK visitors, GA4 uses IP addresses to derive approximate location and discards them before logging or storage. These data are not all anonymous.
Application measurement URLs contain the site origin and sanitized route templates, which can indicate locale, family/caregiver area or workflow, rather than raw account, booking or request IDs. Page titles are fixed to VovoCare; referrers are reduced to their origin. Only validated gclid, gbraid, wbraid, utm_source, utm_medium, utm_campaign and utm_id attribution identifiers are retained in measurement URLs; other query fields, search terms and tokens are removed.
The Ads publication conversion includes its destination/label, value 0, currency EUR and a purpose-scoped pseudonymous transaction_id derived by HMAC for deduplication. This value is not booking revenue. GA4 receives predefined funnel events, without booking revenue or an application User-ID; opaque receipts used for local GA4 deduplication are not sent as GA4 event parameters.
Application event payloads exclude names, contact details, care-request contents, health details and authentication tokens. These exclusions do not make cookie identifiers, attribution data or technical connection data anonymous.
These interaction events contain only predefined codes. They never include what you type or select (such as names, contact details, addresses, dates, care descriptions, messages, review text or ratings, or dispute and cancellation reasons), uploaded files, or account, booking or request IDs.
When you have accepted all cookies and are signed in, VovoCare also sends GA4 a limited set of account milestones confirmed by our servers (verified sign-up, completed profile, caregiver activation, job application, caregiver selection, checkout start, confirmed payment with the platform commission and booking amount, completion report, accepted care completion, caregiver payout release, review and dispute submission, and refunds). They are linked only to the same pseudonymous GA4 browser identifier and the validated campaign identifiers listed above, never to your name, contact details, account ID or care details. Choosing essential cookies only removes this link and stops these server events for your account.
Recipients include Google Ireland Limited and Google LLC and their relevant affiliates/subprocessors. VovoCare remains controller for its measurement purposes. For Analytics customer personal data processed on our instructions, Google acts as processor under the Google Ads Data Processing Terms. Google Ads attribution and standard conversion tracking are controller services under the Google Ads Controller-Controller Data Protection Terms; Google acts as an independent controller for that processing, rather than as our processor for every service.
If the Analytics “Google products & services” data-sharing setting is enabled, Google is also a controller for data shared under that setting, governed by the Google Measurement Controller-Controller Data Protection Terms. The application’s disabled personalization/Signals/enhanced-conversion flags do not establish the account’s data-sharing settings. Google’s own privacy notice explains its processing and controls.
Google may process measurement data outside the European Economic Area, including in the United States. Google documents reliance on the EU–US Data Privacy Framework for applicable transfers to certified US entities and on European Commission Standard Contractual Clauses where a relevant adequacy/transfer framework does not apply, together with contractual, technical and organisational safeguards. The applicable processor or controller terms govern the transfer chain; Irish receipt does not mean all processing stays in the EEA. Details and copies of the applicable terms and safeguards are available through the official links below or by contacting privacy@vovocare.org.
Google documents default expiry of two years for _ga (visitor distinction) and _ga_<container-id> (session state), and 90 days for _gcl_ advertising-attribution cookies when used. These are provider defaults, not verified account-specific durations: account overrides, cookie renewal and browser limits can change actual lifetimes. Cookie expiry is separate from Google’s server-side data retention.
VovoCare’s consent cookie has a 365-day maximum age. The corresponding version-2 localStorage choice is valid for 365 days, although the stored entry remains until overwritten or browser deletion; legacy essential-only choices remain effective. Consented campaign attribution and expected booking-transition markers in sessionStorage are used for up to 24 hours, subject to the tab/session ending earlier. Booking-state baselines are session-scoped and attribution/booking session entries are removed on withdrawal. The localStorage deduplication ledger (vovocare-measured:…) has no automatic expiry and remains until browser storage is cleared; it stores opaque receipt keys and a sent marker.