Legal Data Hunter Cookie Notice
This Notice explains how Legal Data Hunter, Inc. uses cookies, local storage, and similar technologies on legaldatahunter.com and related LDH web interfaces.
It should be read with the Privacy Notice. This Notice provides information and is not a contract.
1. What these technologies are
Cookies are small text files stored by a browser. Local storage is browser storage that a site can use to keep information on a device. Similar technologies may include pixels, tags, software development kits, and device or network signals.
Some technologies are necessary to provide a requested service, keep an account secure, remember a privacy choice, or maintain a session. Others may be used for analytics, preferences, or other optional purposes.
2. What LDH uses
LDH uses the following first-party browser technologies:
| Technology | Purpose and data | Duration |
|---|---|---|
oauth_state cookie |
Secure, HttpOnly, SameSite=Lax state value used to protect an OAuth sign-in against request forgery. | Up to 10 minutes and deleted after the callback. |
login_next cookie |
Secure, HttpOnly, SameSite=Lax value remembering the requested page during sign-in. | Up to 10 minutes and deleted after the callback. |
auth_token local storage |
Authentication token used to keep an account signed in across page loads. | The token is valid for up to 7 days. It is removed on sign-out or after an invalid-session response. |
| Map-data local storage | Cached public geographic map data used to avoid downloading the same map repeatedly. | Until replaced by a newer cache version or cleared in the browser. |
| Submission and feedback local storage | A recent-submission timestamp used for client-side abuse prevention and, where supplied, a feedback username remembered for convenience. | Until overwritten or cleared in the browser. |
Sleek Analytics is disabled by default. It may be enabled only on the selected exact public-page allowlist after LDH records an operational attestation that the provider-side configuration satisfies the CNIL audience-measurement exemption. The allowlist may include public informational and pricing pages and LDH's local checkout-success page; it does not include Stripe's hosted checkout. When enabled, LDH's adapter sends only the allowlisted page path and a fixed allowlisted event name; it suppresses query strings, fragments, document referrers, page content, plan, amount, Stripe session data, account/customer identifiers, and custom event properties. The browser opt-out is applied before the provider script is loaded.
The required attestation covers first-party audience measurement only, no advertising, profiling, cross-site tracking, customer-file enrichment, or cross-checking; the CNIL identifier-lifetime limit; IP truncation or equivalent provider-side non-retention; limited retention; and restricted provider data use. If every condition cannot be confirmed, Sleek remains disabled until an opt-in consent flow is implemented.
3. Consent and choices
Authentication, security, and requested functional storage operate without consent where permitted because they are used to provide the service or feature requested by the user.
LDH does not treat cookieless operation alone as sufficient. Sleek may operate without an analytics-consent banner only while the recorded configuration attestation remains current and every applicable CNIL audience-measurement exemption condition is satisfied. Otherwise Sleek remains disabled until LDH implements opt-in consent.
If LDH activates an optional technology that does not qualify for an applicable consent exemption, LDH will:
- ask for consent before activating it;
- separate optional choices by purpose where required;
- make refusal as easy as acceptance;
- allow consent to be withdrawn; and
- keep a limited record of the choice.
Strictly necessary technologies may operate without consent where the law permits, but LDH will still describe them. A technology is not treated as necessary merely because it is useful to LDH.
You can also control cookies through browser settings. Blocking necessary storage may prevent account login or other requested features from working. Browser controls may not remove all forms of local storage or similar technology.
4. Providers and international processing
When Sleek is disabled, no Sleek event data is sent. When it is enabled under a current exemption attestation, Sleek acts as processor for the path-only audience events described above. The browser adapter uses no-referrer; ordinary network-layer information necessarily exposed to the destination must remain within the attested provider-side IP and data-use controls. Sleek processing may involve infrastructure in locations used by its listed subprocessors.
More information is available in the Sleek Privacy Policy, Sleek DPA, and LDH Subprocessor List.
5. Retention
The browser-side durations are stated in the table above. If Sleek is enabled, its event-retention setting must match the current exemption attestation and the documented operational limit; if that setting cannot be verified, Sleek remains disabled.
6. Changes
LDH may update this Notice when technologies, providers, purposes, or legal requirements change. A revised Notice will show a new version and effective date. LDH will request a new choice before materially expanding consent-based processing where required.
7. Contact
Questions or privacy requests: zach@legaldatahunter.com
Legal Data Hunter, Inc. 2810 N Church St STE 89040, Wilmington, DE 19802, United States