01 / 03Cookie Policy

Cookie Policy

How we use cookies and similar technologies.

This Cookie Policy explains what cookies and similar technologies are, how Tableview uses them on tableview.com and across the Tableview product, why we use them and how you can control them. It supplements and is part of our Privacy Policy. By using the site you consent to the use of cookies in accordance with this policy, subject to your choices in the cookie banner.

Last updated
May 17, 2026
Effective date
May 17, 2026

You can switch off everything except strictly necessary cookies from the cookie banner on your first visit, or anytime later from the "Cookie preferences" link in the footer. We honour the Global Privacy Control signal automatically.

Section 01

What cookies are

Cookies are small text files that a website places on your device (computer, tablet or smartphone) when you visit it. They are widely used to make websites work, to improve their performance, to remember preferences and to provide analytics and advertising functions.

We also use a small number of similar technologies that perform the same function but are not technically cookies, including local storage, session storage, pixels, beacons and server-set identifiers in HTTP response headers. For simplicity, we call all of these "cookies" throughout this policy.

Cookies can be classified by their origin (first-party cookies are set by the website you are visiting; third-party cookies are set by a different domain) and by their duration (session cookies expire when you close the browser; persistent cookies remain until they expire or are deleted).

Section 02

The categories of cookies we use

Strictly necessary cookies

Required for the site to function. Without these the site cannot operate. They include the session cookie that keeps you signed in, CSRF tokens that protect against forgery, language preference, the cookie consent record itself and basic load-balancing identifiers. Strictly necessary cookies do not require consent under EU/UK law and are set on every visit.

Performance and security cookies

Aggregate stats on which pages load fast, which ones throw errors, which routes are used most, and detection of patterns associated with credential stuffing, scraping and other abuse. We use these signals to prioritise engineering work and to keep the site safe. They do not identify individuals.

Analytics cookies

Tell us, anonymously and in aggregate, which marketing pages are useful, which calls-to-action work and which guides people read to the end. Powered by Google Analytics 4 with IP anonymisation enabled. Loaded only after you accept analytics cookies in the banner.

Marketing cookies

Let us measure whether our paid campaigns led to a useful outcome (for example a demo request) and let us reach professional audiences in our market with relevant content. These cookies are set by our advertising partners (Meta, LinkedIn, Google Ads) and fire only after you accept marketing cookies in the banner.

Section 03

The specific cookies we use

The table below lists the cookies you are most likely to encounter on tableview.com. Cookies set by third parties are governed by the third party's own privacy and cookie policies; we link to them where possible.

Strictly necessary

  • tv_session – first-party, session – keeps you signed in to the application.
  • tv_csrf – first-party, session – protects against cross-site request forgery on form submissions.
  • tv_locale – first-party, 1 year – remembers your selected language (en/es/de/fr/it).
  • tv_cookie_consent – first-party, 12 months – records your cookie consent choices so we do not ask again.

Performance and analytics

  • _ga, _ga_* – third-party (Google), 13 months – Google Analytics 4, aggregate site usage with IP anonymisation. Google cookies.
  • _clck, _clsk, CLID – third-party (Microsoft), 1 year / 1 day – Microsoft Clarity heatmaps and session replay on marketing pages, with input fields masked by default. Microsoft privacy statement.

Marketing

  • _fbp, fr – third-party (Meta), up to 90 days – Meta Pixel conversion tracking for Meta paid campaigns. Loads only after consent. Meta privacy policy.
  • li_sugr, bcookie, lidc, UserMatchHistory – third-party (LinkedIn), up to 12 months – LinkedIn Insight Tag conversion tracking. Loads only after consent. LinkedIn cookie policy.
  • NID, _gcl_au – third-party (Google), up to 13 months – Google Ads conversion measurement. Loads only after consent. Google cookies.

Cookie names, durations and third parties can change as we improve the site. The current set used in your browser is always visible in your browser's developer tools (Application → Cookies).

Section 04

How to control cookies

  • Use the Cookie preferences link in the site footer to change your choices at any time. Withdrawal is as easy as consent.
  • Most browsers let you block or delete cookies entirely from their settings (typically Settings → Privacy & security → Cookies). Doing so may break parts of the site.
  • On mobile, you can reset advertising identifiers from the OS-level privacy settings.
  • For analytics opt-out specifically: Google Analytics offers a browser opt-out add-on.

Section 06

Changes to this Cookie Policy

We update this Cookie Policy when the cookies we use change or when relevant law changes. The "Last updated" date at the top reflects the most recent revision.

03 / 03Get in touch

A real human reviews every legal request.

If you have a question about this Cookie Policy or want to exercise a right under it, write to us. We answer within five business days for routine requests; statutory deadlines are met in every case.