Skip to main content

Cookie Policy

giid.io Cookie Policy

This Cookie Policy explains how giid.io ("we", "us", "our") uses cookies and similar technologies on giid.io (the "Site"). It should be read alongside our Privacy Notice and Terms of Use.

Last updated: May 20, 2026

1. What cookies are

Cookies are small text files placed on your device when you visit a website. We also use related technologies such as local storage; for simplicity, we refer to all of these as "cookies" in this policy.

2. Our approach to cookies

We use consent-based loading for non-essential cookies. When you first visit the site, no analytics or advertising scripts run without consent. Google Analytics 4 starts in Google Consent Mode v2 “denied” by default. No cookies are stored and no data is sent to Google until you explicitly opt in. The Meta Pixel and TikTok Pixel are not loaded at all until you grant advertising consent.

You can withdraw consent at any time using the Cookie settings link on this page (see section 6).

3. Analytics: Google Analytics 4

If you consent to analytics, we load Google Analytics 4 ("GA4") to help us understand how visitors use the site so we can improve it.

Privacy controls

  • IP addresses are truncated before storage. GA4 anonymises IPs server-side by default; we also set the legacy `anonymize_ip` flag for completeness.
  • No personally identifiable information is included in custom events. We do not pass names, email addresses, phone numbers, or any other PII into GA4.

4. Advertising: Meta Pixel and TikTok Pixel

If and only if you consent to advertising cookies, we load the Meta Pixel (Facebook) and the TikTok Pixel to measure the effectiveness of our advertising on those platforms.

We also use Meta’s Conversions API: our servers send the same events directly to Meta so measurement still works when browsers block tracking scripts. When you are signed in, this data includes your email, first name, last name, and our internal user ID each transformed by a one-way SHA-256 hash before transmission, so Meta receives a fixed-length code rather than the original values.

For the full disclosure of what is sent to Meta, the joint-controller arrangement under GDPR Article 26, and your choices, see sections 6 and 7 of our Privacy Notice.

5. What we measure

5.1 Page views

The site is a single-page application. We send a page_view event to GA4 each time you navigate between routes.

5.2 Marketing attribution (UTM parameters)

If you arrive at the site via a link containing UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) we capture those values and attach them to your subsequent funnel events to understand which marketing channels lead to sign-ups.

5.3 Sign-up funnel events

We track the following custom events as you move through the sign-up flow:

  • signup_landed : you arrive on the sign-up page.
  • signup_form_start : you begin filling in the sign-up form.
  • signup_form_submit : you submit the sign-up form.
  • signup_field_abandoned : you leave the sign-up form before completing it (records which field you last focused on, not its contents).
  • signup_complete : the sign-up is successfully completed.
  • sign_up : GA4’s standard sign-up conversion event.

None of these events include personal information.

6. Managing your preferences

You can withdraw or change consent at any time using the Cookie settings link below. Most browsers also let you block or delete cookies directly. See the help pages for Chrome, Safari, Firefox, and Edge.

7. Changes to this policy

We may update this Cookie Policy from time to time. The "Last updated" date at the top of the page reflects the most recent changes.

8. Contact

If you have questions about how we use cookies, contact us at privacy@giid.io.