Cookie Policy

Cookies are small text files that a website asks your browser to store on your device. Modern browsers also expose similar storage mechanisms — localStorage, sessionStorage, and IndexedDB — which behave like cookies for legal purposes. Where this policy says “cookie”, treat it as including these.

That is the full list. We will update this table — and announce the change — before we add any new cookie.

We do not run third-party advertising cookies. We do not sell visitor data. We do not embed Facebook Pixel, Google Ads tags, LinkedIn Insight, TikTok Pixel, or any equivalent tracker. Sales and marketing decisions on our side are made from aggregated PostHog data and from data customers volunteer to us. The full list of subprocessors that ever handle data on our behalf — including the few that drop cookies — is published in the Privacy Policy.

When Converlane is embedded inside a customer’s product (for example, the public-pitch landing flow that customers can host on their own subdomain), the customer remains responsible for displaying their own cookie banner and obtaining any consent that local law requires. Our embedded surface ships with the same minimal cookie footprint described above.

The dashboard stores a small amount of UI state in localStorage — for example, the collapsed/expanded state of the sidebar, the table column ordering on the leads view, and the last selected workspace. None of this data leaves your browser. We treat it the same way we treat strictly-necessary cookies: it is part of the application, you can clear it from your browser settings, and we do not need consent to store it.

The meeting agent uses the browser’s IndexedDB only as a temporary buffer for screen-share frames during an active meeting. The buffer is cleared when the meeting ends.

You can clear and block cookies at any time using your browser’s settings — most browsers expose this under Settings → Privacy. Note that disabling the strictly-necessary Supabase session cookie will sign you out and prevent the dashboard from working.

To opt out of the optional PostHog analytics specifically, enable the Do Not Track header in your browser settings. We honour it server-side and will not initialise the PostHog client when it is set. You can also opt out programmatically by setting localStorage.setItem('ph_opt_out', '1') in the browser console; the analytics client will respect that flag on the next page load.

Most browsers — Chrome, Safari, Firefox, Edge, Brave — also let you block third-party cookies entirely. Doing so will not affect Converlane because we set only first-party cookies on our own domain.

We update this policy whenever we add or remove a cookie. The “Last updated” date at the top reflects the most recent change. Substantive changes will also be announced via an in-product banner.

Questions or requests about cookies are best handled together with privacy questions — email krishal@advisio.in. Full context is on the Privacy Policy.