InviteHandle Cookies Policy

1. About this policy

This Cookies Policy explains how InviteHandle uses cookies and similar technologies on invitehandle.com. Similar technologies include browser storage, tags, pixels and random identifiers used to operate the website and measure how it is used.

This policy should be read together with the InviteHandle Privacy Policy.

2. What cookies and similar technologies are

Cookies are small text files stored by a website in your browser. They can help a site remember a browser or session, maintain settings and understand how the site is used. sessionStorage is browser storage that normally remains available only within the current browser tab and is cleared when that tab or session ends. Tags and pixels are code that can send limited event information to analytics or advertising services.

3. Technologies we use

Website and security technologies. We may use essential storage or technical identifiers needed to operate pages, preserve form state, authenticate authorised users, protect the service and prevent abuse. These technologies are used only as necessary for their stated function.

Same-tab booking storage. We use sessionStorage to retain a random booking-journey tid in the current tab and, when supported campaign information is present, preserve first-touch attribution while a visitor moves from a landing page to /book. The supported attribution fields are gclid, gbraid, wbraid, utm_source, utm_medium, utm_campaign, utm_term, utm_content, landing page and original referrer. We also use sessionStorage for a delivery retry queue containing approved non-identifying booking-funnel event data. The queue holds no more than 12 events and expires events after 30 minutes. We do not store arbitrary query parameters or contact details in this storage. sessionStorage normally ends when the browser tab or session is closed.

Google Analytics 4. We use Google Analytics 4 to measure website use and the booking funnel. Depending on the configuration and your browser settings, GA4 may use first-party cookies such as _ga to distinguish browsers and _ga_<container-id> to preserve session state. Google states that the default lifetime for these cookies is up to two years, subject to our settings, your return visits and browser limits.

Google Ads measurement. After an inquiry has been successfully saved, an approved GA4 generate_lead event may be imported into Google Ads as a lead conversion. We do not use the displayed package price as confirmed revenue, and we do not create a confirmed-lead event for a failed inquiry.

4. The booking-attempt tid

When a booking journey starts, InviteHandle generates a random UUID called tid. The same tid is included on approved booking-funnel events and, if the inquiry is saved, stored with the inquiry. The tid continues across a refresh in the same browser tab. A new explicit booking action, a successfully completed inquiry, expiry after six hours, or a separate browser tab creates a new tid.

The tid is not used as Google Analytics user_id. InviteHandle does not send a name, email address, phone number, exact address, free-text answer or customer identity lookup linked to tid to Google Analytics.

The tid may be sent with approved funnel events regardless of a cookie preference. It is limited to one booking attempt and is used to reconcile funnel steps with the saved inquiry and prevent duplicate confirmed-lead measurement. Disabling cookies may limit Google’s ability to recognise a browser, session or advertising source, but it does not necessarily stop all tid-based funnel measurement.

5. Information sent for measurement

Approved funnel measurement may include tid, event_id, event name and time, page path, form name, locale, event category, city category, days until the selected event, guest-count band, package name, displayed package price, currency, preferred contact-method category, referral-source category, supported campaign attribution and entry-CTA context. Approved events are sent to Google Analytics and stored in InviteHandle’s first-party Supabase event ledger. We do not send or store directly identifying contact details, exact event dates, exact addresses, notes or free-text inquiry content in this funnel measurement.

6. How long technologies remain

The tid, attribution and retry queue held in sessionStorage normally remain only for the active same-tab browser journey; queued events are additionally limited to 30 minutes. A same-tab refresh continues the tid, while a new explicit booking action, a successfully completed inquiry, expiry after six hours, or a separate tab creates a new one. Raw events in InviteHandle’s first-party booking-funnel ledger are retained for 24 months from the server-recorded receipt time and then deleted. GA4 cookies may remain for up to two years by default, subject to configuration and browser controls. Attribution and tid information stored with a completed inquiry follows the retention period stated in the Privacy Policy.

7. Your choices

You can block or delete cookies using your browser settings. You can also use Google’s available advertising controls or Analytics opt-out tools. Blocking cookies may affect site features and may reduce attribution or reporting accuracy.

InviteHandle does not claim that all measurement stops when cookies are blocked or rejected, because approved tid-based funnel events may still be sent as described above. If we provide a cookie preference control, we will record and respect the applicable preference while keeping the booking form functional.

8. International processing

Google and other technology providers may process measurement data outside the UAE or KSA. We address international processing and applicable safeguards in the Privacy Policy.

9. Changes to this policy

We may update this Cookies Policy when our technologies, providers or legal obligations change. The current version will be published on this page with its effective date.

10. Contact

For questions about cookies, browser storage or measurement, submit a request through the contact form on invitehandle.com.