LegalLead360 Legal
Lead360 Cookie and Browser Storage Policy
How Lead360 uses cookies, local storage, session storage, security tools, preferences, authentication, and customer-configured website technologies.
Lead360 uses cookies and browser storage for authentication, security, sessions, preferences, communications, carts, and application state. Customer-built sites may use additional technologies selected by the customer.
Scope
This policy applies to Lead360-operated websites and applications. A website, funnel, form, mini app, campaign, or customer app created by a Lead360 customer may use additional cookies, pixels, tags, or storage controlled by that customer or its connected providers. The customer must provide its own cookie notice and consent controls where required.
What these technologies are
Cookies are small values stored by a browser and sent with requests. Local storage persists values on a device until removed. Session storage generally lasts for a browser tab or session. Similar technologies include pixels, SDKs, cache entries, device identifiers, and server logs.
How Lead360 uses them
| Category | Examples and purpose |
|---|---|
| Authentication and security | Access tokens, staff sessions, administrator sessions, impersonation controls, collaboration sessions, anti-abuse signals, and Cloudflare security or Turnstile checks. |
| Application state | Active account, conversation identifiers, campaign sessions, booking progress, form state, cart contents, checkout references, and workflow state. |
| Preferences | Language, dark mode, sidebar state, visible columns, notification state, media permissions, and install preferences. |
| Communications | Chat session identifiers, call state, notification coordination, and message history stored on the device. |
| Performance and diagnostics | Request logs, error details, traffic measurement, security events, and service reliability information. |
| Consent-based website analytics | Page visits, referrers, UTM and advertising identifiers, conversion paths, and return visits after a visitor becomes a known contact. Analytics remains disabled until the visitor allows it and is disabled when Global Privacy Control applies. |
| Customer-selected tools | Analytics, advertising, chat, payment, social, or embedded services configured on a customer page. |
Lead360.io legal and support pages
Lead360.io uses a first-party Lead360 external tracker only after analytics consent. It records page visits, referrers, UTM and advertising identifiers, conversion paths, and return visits that may attach to an activity timeline after a visitor becomes a known contact. The tracker does not identify an anonymous visitor by name. Cloudflare may separately process network, security, and traffic information at the edge.
Your choices
- Use browser controls to view, block, or delete cookies and site data.
- Use device settings to clear local and session storage.
- Disconnect customer-selected integrations or advertising tools where available.
- Use Privacy choices on Lead360.io to allow or withdraw analytics consent.
- Use a customer page consent control when one is provided.
- Contact the customer that operates a page for choices about that customer cookies and tracking.
Blocking essential authentication or storage can prevent sign-in, checkout, calling, chat, forms, automations, or other features from working. Lead360 does not currently provide a universal consent-management platform for every customer-built site. Customers must configure consent appropriate to their own pages and audience.
Do Not Track and Global Privacy Control
Browser Do Not Track signals are not interpreted consistently across the industry. Lead360.io disables its consent-based analytics tracker when Global Privacy Control is present. Where Global Privacy Control or another legally recognized signal applies to a Lead360-controlled sale or sharing opt-out, Lead360 will also treat it according to applicable law. Customer websites and connected providers may require separate configuration.
Duration and updates
Storage duration depends on purpose. Session values may expire when the browser closes; authentication and campaign values may persist for a defined period; preferences may remain until cleared; server logs follow the Retention Policy. We may update this page when technology or legal requirements change. Questions may be sent to [email protected].
Contact
Questions about this document
Email [email protected] and include the document name, customer account, and the issue you want us to review. Do not send passwords, private keys, payment credentials, or PHI.
Contact Lead360