What are cookies?
Cookies are small text files placed on your device when you visit a website. They allow the site to remember your preferences, recognise your device, and provide a more personalised experience. Vowly Event also uses similar technologies such as local storage, session storage, and pixel tags, which are collectively referred to as “cookies” in this policy.
Categories of cookies we use
We classify our cookies into four categories based on their purpose. Strictly necessary cookies are always active because they are essential for the Service to function. Analytics cookies are on by default so that we can measure how the Service is used; you can switch them off at any time in Cookie Preferences. Functional and marketing cookies require your explicit consent under UK PECR and the EU ePrivacy Directive.
- Strictly necessary: your cookie choice, what you did on an invitation (your reply, gifts, photos and guest-book entry), automated-abuse protection, the live support chat and a banner you closed; in the web app also your sign-in and what it remembers of your own settings. These cannot be switched off
- Functional: optional conveniences. We use none of these today; the category exists so that we could never enable one without asking you first
- Analytics: usage statistics that show us how the site is used, so we can run and improve it (on by default, can be switched off at any time)
- Marketing: advertising and re-targeting. We use none of these today; the category exists so that we could never enable one without asking you first
Specific cookies in use
Below is the complete list of what Vowly Event stores on your device, on this site and (marked web.vowly.co) in the organiser web app, checked against the code of both. The duration indicates how long each item persists after it is set.
- vowly_consent (cookie, strictly necessary, 12 months): records your cookie choices so we do not ask again
- _ga, _ga_* (cookies, analytics, on by default, 13 months): Google Analytics 4 with IP truncation, used to measure how the site is used. Switching analytics off in Cookie Preferences deletes them from this device
- _GRECAPTCHA (cookie) and _grecaptcha (local storage): set by Google reCAPTCHA on invitation pages to block automated abuse of RSVP forms, and in the organiser web app (web.vowly.co) only once you are signed in. Strictly necessary; see Third-party cookies below
- vowly_rsvp_device (local storage, strictly necessary): a random token created only when you submit an RSVP, so you can edit or cancel it later without an account
- vowly_rsvp_manage_*, vowly_k_* (local storage, strictly necessary): remember your RSVP so you are not asked for the event PIN again on the same device
- vowly_gifts_*, vowly_guest_photos_* (local storage, strictly necessary): remember the gifts you reserved and the photos you uploaded, so you can manage them without an account
- vowly_guest_name_* (session storage, strictly necessary): the name you put on photos you upload to an invitation, so a reload does not ask for it again; kept for that invitation only and deleted when you close the tab
- vowly_app_banner_dismissed_at (local storage, strictly necessary): on a phone, the time you closed the banner suggesting our app, so that it stays closed for 7 days; it holds only that time, which stays on the device until you clear this site’s data
- vowly_guest_lang_* (local storage, strictly necessary): the language you picked at the foot of an invitation, so that invitation opens in it next time on this device; written only when you pick one (never in the hosts’ preview) and kept until you clear this site’s data
- vowly_gb_* (session storage, strictly necessary): keeps what you are writing in a guest book if the page reloads, and shows your entry after you send it; deleted when you close the tab
- crisp-client/* (cookies and local storage, strictly necessary): live-chat session, so a reply reaches you. Set when the chat loads in the background, on every page except invitation pages. Always active
- web.vowly.co: firebaseLocalStorageDb, firebase-app-check-database, firebase-heartbeat-database (IndexedDB) and vowly.postLoginPath (session storage), strictly necessary: the Firebase software the web app runs on keeps you signed in (your user ID, email address, name and sign-in tokens, removed when you sign out), proves after sign-in that requests come from a real browser, and notes which of its services the page used; vowly.postLoginPath takes you to the page you asked for once you have signed in
- web.vowly.co: @vowlyevent_language, @vowlyevent_language_chosen, @vowlyevent_theme_mode, @vowlyevent_sidebar_collapsed, @selected_event_id, tour:*, hasSkippedFirstEvent:*, tasks.doneSuggestDismissed.*, vowly.trustpilotPromptAt, vowly_phone_app_card_dismissed, vowly_phone_app_has_app:*, vowly_theme_assets, @vowlyevent/platformFlags (local storage) and vowly:termsUpdateLater:*, vowly_chunk_reload, vowly_notice_reload (session storage), strictly necessary. They hold what the web app remembers on this device: your language, appearance and sidebar, the event you last opened, the guided tours you finished, the cards and reminders you closed or postponed, whether you already use our phone app, copies of public settings so screens draw at once, and a guard against reloading in a loop after an update. Some carry your user ID or an event’s ID in their name. The local-storage items stay until you clear this site’s data; the session-storage items go when you close the tab
- web.vowly.co: _ga, _ga_* (cookies, analytics, on by default, 13 months) and firebase-installations-database (IndexedDB): Google Analytics 4 in the web app, the same property as this site; once you are signed in, visits are counted under your account’s ID. The “Usage analytics” switch in your profile turns it off and deletes the _ga cookies, and vowly_analytics_consent (local storage) remembers that choice; the installation ID stays until you clear this site’s data. Global Privacy Control / Do Not Track turn it off too
- web.vowly.co: vowly_crisp_token (local storage, strictly necessary): after you sign in, a secret token that reopens your own support conversation; removed when you sign out. Crisp’s own crisp-client/* storage is added once you are signed in, or when you open the chat
- web.vowly.co: vowly_signup_ref, vowly_signup_campaign, vowly_signup_form (session storage), set only when a link to the web app says where you came from (?ref=, ?campaign=) or asks for the sign-up form: the first two are saved with your new account as the way you came to us, the third is deleted once the form has opened, and all go when you close the tab. vowly.pendingRef, vowly.pendingRefAttempts (local storage): someone’s referral code from such a link, kept until your account has claimed it or you clear this site’s data
- web.vowly.co: vowly_webpush_* (local storage), firebase-messaging-database (IndexedDB) and the service worker /push-sw.js, only if you turn on browser notifications: your choice and the device token that lets us notify you. The token is removed when you turn notifications off or sign out, your choice when you turn them off; the service worker stays registered until you clear this site’s data
Third-party cookies
Three third parties can receive data from this website as you browse it, and two video services only if you play a film on an invitation (below). There are no others: this site loads no advertising, social or tracking pixels of any kind, and all fonts are served from our own servers. The organiser web app (web.vowly.co) uses the same three and, marked web.vowly.co below, a few more; it loads no advertising pixels either.
- Google Analytics 4 (Google Ireland Ltd): usage statistics with IP truncation. On by default, on invitation pages too, where the page address is shortened to the page type so that your personal invitation link is not sent. You can switch it off in Cookie Preferences
- Google reCAPTCHA / Firebase App Check (Google Ireland Ltd): verifies that requests come from a real browser, for RSVP and photo uploads on invitation pages and for everything a signed-in organiser does in the web app (web.vowly.co). A security measure, without which these would be open to automated abuse; the sign-in and sign-up pages do not load it
- Crisp (Crisp IM SARL, data hosted in the EU): live chat support. Loads in the background on every page except invitation pages; part of the service, always active
- YouTube (Google Ireland Ltd) and Vimeo (Vimeo.com, Inc., US): only on an invitation whose hosts have added a film, and only once you press its play button. Until then the page loads nothing from either, not even a preview picture. Pressing play loads the player from www.youtube-nocookie.com (YouTube’s privacy-enhanced mode) or player.vimeo.com (asked not to track the viewing); YouTube or Vimeo then receives your device’s IP address and browser details and may store cookies or similar data in your browser under its own privacy policy. Only vowly.co is passed on as the page you came from, never the invitation’s own address
- web.vowly.co: Google sign-in (Firebase Authentication, Google): in Safari, on iPhone and iPad and in mobile browsers, the web app loads a hidden frame from vowly-event.firebaseapp.com and Google’s script from apis.google.com each time it opens, so that signing in with Google or Apple can open its window straight away; other browsers load them only when you sign in with Google or Apple. Google receives your device’s IP address and browser details. Signing in with Google or Apple then opens their own sign-in window
- web.vowly.co: Spotify (Spotify AB): the album covers in the music screens load straight from Spotify’s image servers, so Spotify sees your device’s IP address; the search itself goes through our servers. Invitation pages load nothing from Spotify
- web.vowly.co: Google Analytics 4 and Crisp work there too: analytics is switched off with the “Usage analytics” switch in your profile rather than in Cookie Preferences, and the chat loads in the background once you are signed in, or when you open it
- web.vowly.co: browser notifications, only if you turn them on. They reach you through Google’s Firebase Cloud Messaging and your browser maker’s push service
We use no Meta Pixel, no TikTok Pixel and no advertising or re-targeting cookies of any kind. A film on an invitation loads from YouTube or Vimeo only when you press play. Invitation fonts are self-hosted, so opening an invitation sends nothing to a font provider.
Managing your preferences
You control the optional cookies: analytics, functional and marketing. We display a cookie banner on your first visit where you can accept, reject, or customise them. Reject declines functional and marketing cookies, which stay off until you switch them on. Analytics is on by default and Reject does not switch it off: it stays on until you turn off the Analytics switch in Cookie Preferences. You can change your choices at any time via the “Cookie Preferences” link in the footer.
- Cookie preferences: the “Cookie Preferences” link in the site footer, and at the foot of an invitation page, reopens the panel and your choice takes effect immediately
- Browser controls: most browsers can block or delete cookies and local storage from their settings
- Global Privacy Control / Do Not Track: if your browser sends either signal we disable analytics automatically, without you having to touch the banner
- Switching off: turning analytics off stops the measurement and deletes the _ga cookies from this device straight away; functional or marketing cookies can be switched off again in the same panel at any time
- The web app (web.vowly.co): it shows no cookie banner. The “Usage analytics” switch in your profile turns analytics off there, and Global Privacy Control / Do Not Track do the same
What happens if you reject cookies?
Rejecting functional and marketing cookies, or switching analytics off, has no effect on your ability to use the platform: you can browse every page, open an invitation and reply to it exactly as before. The live support chat stays available. Reject does not switch analytics off; once you switch it off in Cookie Preferences, your visit no longer appears in our usage statistics. Strictly necessary items cannot be rejected, because without them we could not remember your cookie choice or let you edit an RSVP you already sent. A browser that sends Global Privacy Control or Do Not Track is not measured either.
Changes to this policy
We may update this Cookie Policy to reflect changes in technology, regulation, or our service. The “Effective” date at the top of this page indicates the most recent revision. Material changes will be highlighted in our consent banner upon your next visit.
Manage your preferences
You can change your cookie consent choices at any time through our preference centre or by writing to our data protection team.