Cookie Policy

01.What this policy covers

This policy explains how LeadScraper uses cookies and similar technologies on https://lead-scraper.orangeglacier-46fc85b5.eastus.azurecontainerapps.io and in the LeadScraper application. It sits alongside our Privacy Policy, which describes how we handle personal information more broadly.

By "cookies" we mean cookies plus the technologies that do a comparable job: local storage, session storage and pixels. We refer to them all as cookies below for readability.

02.What cookies are

A cookie is a small text file that a website asks your browser to store. On your next visit the browser sends it back, which is how a site can recognise that you are still signed in, remember a preference, or count a visit without recognising you personally.

A first-party cookie is set by the site you are visiting. A third-party cookie is set by another domain whose code the site has loaded. Session cookies are deleted when you close your browser; persistent cookies survive until they expire or you clear them.

03.Why we use cookies

We keep this deliberately narrow. Cookies are used to sign you in and keep you signed in, to protect accounts against fraud and abuse, to remember interface preferences, and to understand in aggregate which pages are useful so we can improve them.

We do not use cookies to build advertising profiles, and we do not sell information collected through cookies.

04.The categories we use

Every cookie on our properties falls into one of the following categories.

• Strictly necessary — authentication, session integrity, load balancing, CSRF protection and abuse prevention. The service cannot function without these, so they are set without asking and cannot be switched off from inside the product.
• Functional — remembering choices you have made, such as a saved project view, a dismissed banner or an interface preference. Losing these is an inconvenience rather than a breakage.
• Analytics / performance — aggregate, de-identified measurement: which pages are visited, how long a page takes to load, where errors occur. We use this to prioritise work, not to identify individuals.
• Advertising / targeting — we do not currently set cookies in this category. If that ever changes we will update this policy and, where the law requires it, ask for your consent through a banner before setting them.

05.Cookies we set

TODO(launch): list the actual cookies once your final analytics and auth stack is in place — name, provider, category, purpose and retention period. A specific table is what regulators and enterprise reviewers look for, and a generic description will not satisfy either.

Until that table is published, the summary in the section above describes the categories in use.

06.Third-party cookies

Some cookies are set by providers we use to run the service — for example our hosting platform, our payment processor during checkout, and our error monitoring and analytics tooling. These providers set cookies under their own domains and handle that data under their own policies.

We keep this list as short as we practically can, and we do not embed advertising networks or social media tracking widgets on our marketing pages.

07.How to control cookies

You can accept, block or delete cookies through your browser settings, and every major browser lets you do this per site. Blocking strictly necessary cookies will stop you being able to sign in, so expect the application to break if you do.

• Chrome — Settings → Privacy and security → Third-party cookies, and "See all site data and permissions" for per-site control.
• Safari — Settings → Privacy, plus "Manage Website Data" for per-site control.
• Firefox — Settings → Privacy & Security → Cookies and Site Data.
• Edge — Settings → Cookies and site permissions.
• Mobile browsers expose the same controls under their privacy settings.

08.Do Not Track and Global Privacy Control

There is still no agreed standard for how sites should respond to the browser "Do Not Track" header, so like most services we do not alter behaviour based on it. Where we are legally required to honour an opt-out preference signal such as Global Privacy Control, we do.

09.Local and session storage

The application uses browser local storage and session storage for things a cookie is a poor fit for — keeping interface state between page loads and caching data so screens do not have to be refetched constantly. This data stays in your browser, and clearing your site data removes it.

10.Changes to this policy

We will update this page when our use of cookies changes and revise the "last updated" date at the top. Material changes will be communicated to account holders by email.

11.Contact

Questions about this policy, or about a specific cookie: support@leadfinder.com. Postal address: 2261 Market Street, San Francisco, CA 94114, US.