Cookie Policy

Last updated: 31 May 2026

Topolog uses a minimal set of cookies. Only strictly-necessary cookies are on by default; functional, analytics, and advertising cookies load only if you opt in, and stay off until you do. We never sell your data.

Strictly necessary

Functional

If you opt into the “Functional” category and you’re signed in, we load the Intercom Messenger so you can chat with us from inside the dashboard. Intercom sets a small set of cookies (prefixed intercom-) to keep your chat session attached across navigations. Nothing functional loads on the marketing site or while signed out. Turning the category off (Settings → Data, or “Manage Cookies” in the footer) calls Intercom(‘shutdown’) on the next page, which removes the widget and clears its cookies.

Analytics & error tracking

We use Vercel Analytics for page-view counts. It is privacy-preserving and does not use cookies or any other client-side storage. It stays on regardless of your consent choice because no identifier touches your device.

If you opt into the “Analytics” category, two additional things turn on, both routed through Vercel and both cookieless:

• Vercel Speed Insights — persists a short session id in your browser’s sessionStorage (cleared when you close the tab) and sends per-page Core Web Vitals (load timings, device class) so we can spot real-user performance regressions.
• Marketing interaction events — on the marketing pages we record anonymous custom events when you click a CTA, change a pricing-page control, or reach a scroll milestone (25 / 50 / 75 / 100%). These ride the same cookieless Vercel beacon; no identifier is set on your device. The data tells us which pages convert and which sections lose attention. Page is identified by pathname only — no query strings, no IP, no UA-fingerprint.

Decline the category and nothing is written to sessionStorage, the Speed-Insights beacon never runs, and the marketing event functions are no-ops — no per-page detail is sent to Vercel beyond the cookieless page-view count.

We also use Sentry for error tracking, but only on our servers. The Sentry SDK never runs in your browser, so it sets no cookies and writes nothing to your device’s storage.

Advertising

If you opt into the “Advertising” category, two things turn on:

• Meta Pixel — a small script from Facebook / Instagram’s parent company that sets the _fbp and _fbc cookies and posts events to Meta when you take key actions (sign up, subscribe, purchase). We use it to measure which Meta ad campaigns bring real signups; without it our paid- acquisition spend is a black box.
• Attribution capture (topolog-attribution) — a first-party cookie that captures utm_source,utm_medium, utm_campaign, and fbclid from the URL the first time you land on Topolog via an ad, so we can attribute a later signup back to the campaign that brought you in. We use first- touch attribution: if a later visit lands with different utm params, the original cookie is kept. The cookie is automatically deleted after you complete signup (the values are moved into your profile row).

Decline the category and neither the Pixel nor the attribution cookie ever loads. Turning the category off later (Settings → Data, or the “Manage Cookies” footer link) removes the Pixel script tag and deletes the _fbp, _fbc, and topolog-attribution cookies.

Your choices

Strictly-necessary cookies can’t be disabled without breaking the product. Browser controls let you clear them at any time. The Functional (chat support), Analytics (performance & marketing interaction), and Advertising (Meta) categories can be toggled live from Settings → Data or via the “Manage Cookies” link in the footer. Changes take effect immediately — revoked-category scripts shut down and their cookies are deleted on the spot, no page reload needed.