Last updated:

Cookie Policy

Effective Date: May 6, 2026 | Last Updated: October 16, 2026

1. Introduction

This Cookie Policy explains how leadder.co ("Platform", "Leadder", "we") uses cookies and similar tracking technologies. It is part of and should be read together with our Privacy Policy.

This Policy is designed to comply with the GDPR, UK GDPR, ePrivacy Directive (2002/58/EC), UK Privacy and Electronic Communications Regulations (PECR), CCPA/CPRA, and KVKK.

2. What Are Cookies?

A cookie is a small text file placed on your device when you visit a website. Cookies help websites remember your session, preferences, and usage patterns.

In this Policy, "cookies" includes:

  • HTTP Cookies: Classic browser cookies
  • Local Storage / Session Storage: HTML5 mechanisms for browser-side storage
  • Pixels / Web Beacons: Invisible 1×1 images to track page loads
  • SDK Identifiers: Mobile advertising IDs (IDFA, GAID)

3. Types of Cookies

3.1. By Duration

  • Session Cookies: Deleted automatically when the browser closes
  • Persistent Cookies: Remain on your device for a set period or until manually deleted

3.2. By Origin

  • First-Party: Set directly by leadder.co
  • Third-Party: Set by third-party services integrated on the Platform

3.3. By Purpose

  • Strictly Necessary: Essential for Platform operation; no consent required
  • Functional: Remember preferences
  • Analytics / Performance: Measure Platform usage; consent required
  • Marketing / Targeting: For advertising and retargeting; consent required

4. Cookies We Use

This section lists what the Platform sets or loads at the date above. Cookie names and lifetimes for third-party services are the ones those providers document; they can change on the provider's side.

These are essential for you to use the Platform and cannot be disabled:

NameSet byPurposeLifetime
sb-<project-ref>-auth-token (may be split into .0, .1)Supabase, on leadder.coSign-in sessionSet by Supabase, up to 400 days
active_tenant_idleadder.coRemembers which workspace you have selected1 year
meta_oauth_state, meta_oauth_return_to, meta_oauth_replaceleadder.coProtect and complete the "Connect Meta" sign-in flow10 minutes
leadder_cookie_consent (local storage)leadder.coStores your cookie choices12 months, then we ask again

4.2. Functional Cookies

These remember choices you make in the interface:

NameSet byPurposeLifetime
NEXT_LOCALEleadder.coLanguage preference1 year
NEXT_TIMEZONEleadder.coYour browser's time zone, so dates show on your own calendar day1 year
sidebar_stateleadder.coWhether the app sidebar is open or collapsed7 days
Local and session storage entries (for example leadder-settings, leadder:pendingFills)leadder.coKeep interface and in-progress workflow state in your browserUntil you clear your browser data or the session ends

Set only after you accept analytics cookies:

  • Google Analytics (loaded through Google Tag Manager), Google LLC: measures how the Platform is used. Typical cookies: _ga (distinguishes users) and _ga_<container-id> (keeps session state). Google documents a default lifetime of 2 years for both.

Set only after you accept marketing cookies:

  • Google Ads and the Google tag (loaded through Google Tag Manager), Google LLC: measure advertising conversions and support ad personalization. Typical cookies: _gcl_au and _gcl_aw, which Google lists with a 90-day lifetime. Google may also set other advertising cookies, listed at business.safety.google/adscookies.

The Platform loads a Google Tag Manager container only after you accept analytics or marketing cookies. Before that, no Google Tag Manager, Google Analytics or Google Ads script is requested.

We use Google Consent Mode v2. Every signal starts as denied. Your analytics choice controls analytics_storage; your marketing choice controls ad_storage, ad_user_data and ad_personalization. If you later withdraw consent, we send Google the updated (denied) signals. The tags that run inside the container are configured in Google Tag Manager rather than in the Platform's code; this section names the Google tags in use at the date above.

4.6. Error Monitoring

We use Sentry (Functional Software, Inc.) for error and performance monitoring. It runs independently of your cookie choices. For a sample of sessions, Sentry's session replay keeps a session identifier in your browser's session storage (sentryReplaySession); text is masked and media is blocked in replays.

On your first visit, a cookie consent banner appears allowing you to:

  • Accept all cookies
  • Reject all optional cookies
  • Manage your choices by category (functional, analytics, marketing)

Update or withdraw your preferences at any time via the "Cookie Preferences" link in the footer or at leadder.co/cookie-preferences. Withdrawing analytics or marketing consent denies the matching Consent Mode signals straight away; cookies already on your device can be removed in your browser settings.

5.2. Browser Settings

You can control cookies directly through your browser:

Note: Disabling strictly necessary cookies may break Platform functionality (login, session management).

5.3. Mobile Device Advertising IDs

  • iOS: Settings → Privacy → Apple Advertising / Tracking
  • Android: Settings → Google → Ads

5.4. Global Privacy Control (GPC)

If your browser sends a GPC signal, we treat it as an opt-out request for sale/sharing under CCPA/CPRA and equivalent U.S. state laws, and as a withdrawal of consent for marketing/analytics cookies.

Cookie TypeLegal Basis
Strictly necessaryPerformance of contract (GDPR Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f))
Functional, analytics, marketingConsent (GDPR Art. 6(1)(a); KVKK Art. 5/1)

You may withdraw consent at any time; withdrawal does not affect the lawfulness of prior processing.

7. Third-Party Data Sharing

When you accept analytics or marketing cookies, data is shared with:

Independently of your cookie choices, error reports go to Sentry / Functional Software (USA): https://sentry.io/privacy/

International transfers comply with GDPR Chapter V (SCCs, EU-U.S. Data Privacy Framework), UK GDPR, and KVKK Article 9. See Privacy Policy and the sub-processor list for details.

8. Do Not Track

If your browser sends a Do Not Track (DNT) signal, we treat it as a rejection of marketing cookies. You can also use our cookie preference panel.

9. Changes to This Policy

We may update this Cookie Policy periodically. Material changes notified via Platform notification or email. The "Last Updated" date reflects the most recent revision.

10. Contact

  • Controller: CZ Partners Reklam Teknoloji Eğitim Danışmanlık Ltd Şti
  • Email: privacy@leadder.co
  • DPO: dpo@leadder.co
  • Mail: Esentepe Mah. Büyükdere Cad. Levent 199 No: 199 İç Kapı No: 6 Şişli/İstanbul, Türkiye

This Cookie Policy should be read together with our Privacy Policy.