Cookie Policy

Cookies we set

• Session cookies (names starting with "sb-") — set by our authentication provider (Supabase) to keep you signed in securely. Essential; deleted when you sign out or they expire.

• "leadly-auth-next" — a short-lived (10 minute) cookie that remembers which page to return you to after signing in with Google or Apple. Essential; contains a path, no personal data.

That's the complete list. Because both are strictly necessary for sign-in to function, Leadly does not show a cookie-consent banner.

Local storage (on your device)

Preferences and small caches are kept in your browser's local storage — they stay on your device and are not sent to our servers as tracking: your theme (light/dark), language and region, analytics opt-out flag, a random anonymous visitor id used for first-party analytics and blog feedback, your saved search location (ZIP/city), onboarding status, whether you voted on a blog article, cached search results, and where you first arrived from (referrer/campaign, no personal data).

You can clear all of this anytime via your browser's site-data controls; you'll be signed out and preferences reset.

Analytics without cookies

Our first-party pageview analytics use the random visitor id from local storage — not a cookie — and record only the page path, coarse device type, country, and referring site. No IP address is stored with analytics. Turn analytics off in Settings → Notifications → "Help improve Leadly with basic usage analytics."

Third-party services

A few embedded services set their own strictly-functional state when you use the features that load them: Cloudflare Turnstile (the sign-up bot check) and Google Maps (the map view in Find Clients). Stripe would apply at checkout only if paid plans are enabled. None of these are used by Leadly for advertising.

Questions: [email protected]. See also the Privacy Policy.