Your consent choices
Cookie policy
This page explains the categories of cookies and similar storage used by this site. The CookieYes preference center remains the current source for the live provider inventory.
Plain-language policy. Provider inventories and tag configurations can change. The preference center may therefore show more current details than this summary.
What cookies and storage technologies do
Cookies, local storage, session storage, pixels, scripts, and similar technologies can remember a consent choice, support a requested feature, measure usage, or measure marketing traffic. This site does not use custom fingerprinting or a first-party visitor identity system.
Necessary
Necessary technologies are used for core operation, security, routing, and remembering consent-management state. They remain active because turning them off could prevent the site or the consent interface from working. Only technologies genuinely needed for those purposes belong in this category.
Analytics
When Analytics consent is enabled, Google Analytics 4 and Microsoft Clarity may be activated through Google Tag Manager. They help us understand route views, campaign attribution, demo engagement, assistant starts, CTA interactions, and broad abandonment points. The implementation is designed not to send assistant transcripts, voice content, payment identifiers, form contents, or arbitrary free text.
Marketing / Advertisement
When Marketing/Advertisement consent is enabled, Meta Pixel and LinkedIn Insight Tag may be activated through Google Tag Manager to measure traffic and campaign performance. Advanced matching, hashed-email matching, customer-list matching, and server-side Conversions API are not enabled for this phase.
Functional services
Some requested features use external services. Cal.com powers the discovery-call booking experience, Vapi powers assistant demonstrations, and Stripe powers the test/sandbox payment demonstration. These services are loaded or contacted as part of their requested feature flows and may use provider-controlled cookies or storage. They are not treated as analytics or marketing tags.
How consent works
CookieYes is configured through Google Tag Manager. The intended launch configuration uses Basic Google Consent Mode: optional analytics and advertising storage are denied before consent, and Google tags are not intended to fire before consent. The banner offers Accept all, Reject optional, and Manage preferences.
You can reopen the preference interface at any time using Cookie Settings in the footer. If you withdraw optional consent, future tags should stop firing and provider/CMP cleanup should occur where supported. Provider-specific cleanup can vary, so the preference center and provider documentation are the authoritative references.
Current inventory
This policy intentionally does not list individual cookie names or claim a fixed inventory that could become stale. CookieYes should maintain and display the current scan, category, purpose, provider, and duration information for the published implementation.
Questions
For privacy or cookie questions, contact Nelson Solutions through the address on the Privacy policy page. This is a practical implementation description, not legal advice; professional review is recommended before relying on it as definitive advice.