Legal
LEADOXE CRM is owned and operated by VEYSAPP LLC. This Policy explains when the LEADOXE website and applications use cookies or similar browser storage.
Cookies are small text files placed on a device by a website. Similar technologies include local storage, session storage, and service-worker storage. They can remember a session, retain a preference, or help protect and operate a service.
LEADOXE may use strictly necessary technologies to authenticate signed-in users, protect sessions, remember essential interface settings, maintain security, and deliver requested application features. Disabling these technologies may prevent the application or account features from working correctly.
Optional tags load only after you select Accept on supported public marketing pages of leadoxe.com. They do not load on tenant subdomains, account, dashboard, platform administration, integration connection, API, or legal pages. Reject non-essential keeps them off. Tag configuration and vendor cookie behaviour may differ by browser and region. The list below contains only vendors configured for this website.
No optional analytics or advertising vendors are configured for this website.
Measurement uses page activity and fixed event names. Contact details and message text are not included in our measurement events. Contact forms are masked for Clarity; no advanced matching or server-side advertising conversion integration is implemented.
When optional tags are configured, Cookie settings in the footer lets you change your choice. The choice is stored in local storage as leadoxe.marketing.consent.v1 until changed or site storage is cleared. Rejecting after accepting reloads the page to stop vendor scripts. Existing vendor cookies may remain; browser controls can remove cookies and site storage. Google Consent Mode v2 starts with denied signals. Attribution parameters and a landing path are stored in leadoxe.marketing.source.v1 in session storage for this tab, and attached as a Source line to a contact request. They are not sent by our event helper.
Storage duration depends on its purpose. Session technologies normally expire when the session ends; persistent settings remain only as reasonably needed for their stated function. We may update this Policy when technologies or legal requirements change and will revise the effective date.
