Personal data
Cookie Policy
In force from 20 September 2026. Version 2026-09-20.
1. About this policy
TrueValue Technologies Ltd (company number 17462580), of 66 Paul Street, London, England, United Kingdom, EC2A 4NA, operates the TrueValue website and application. This policy explains technologies used to store information on, or access information from, your device. Contact privacy@truevalue.business with questions.
Read this policy with our Privacy Notice. It covers cookies, browser storage, pixels, tags and similar technologies, not only files called cookies. A technology can require a choice even when it does not directly reveal your name.
2. What these technologies do
A cookie is a small item stored by a browser. Session cookies normally expire when the session ends; persistent cookies remain until their stated expiry or earlier deletion. Local or session storage can hold information in a different browser store. Pixels and tags can trigger requests that disclose information about a page or event. Embedded content may connect your device to a third-party provider.
First-party technologies operate in the context of TrueValue. Third-party technologies involve another provider. Their duration, recipients and purpose are described in the completed inventory below. Calling a tool first-party, server-side, anonymous or cookieless does not by itself establish an exemption from the relevant law.
3. Categories and our approach
Strictly necessary technologies support a service you request, such as authentication, session security, load handling or remembering an applicable privacy choice. We use an exception only where its conditions are met, not merely because a technology is useful to our business. Disabling these technologies through your browser may prevent the requested function working.
Optional preferences support conveniences that are not necessary for a requested service. Optional analytics measure how people use the website or application. Advertising technologies can measure campaigns, connect visits with ad interactions or create audiences. Optional embedded media may allow an external provider to receive device information when content loads.
Our default approach is to obtain consent before activating optional analytics, advertising and non-essential third-party embeds. If we rely on a specific legal exception for a strictly limited statistical or appearance-related use, the inventory must identify that use and the applicable information and objection arrangements. Advertising use is not treated as exempt statistical measurement.
4. Giving, refusing and changing consent
Our privacy controls offer acceptance, rejection of optional technologies and category-level choices where appropriate. Optional categories are not preselected. Continuing to browse, closing a banner or accepting subscription terms is not treated as consent to optional tracking.
You may reopen the “Cookie settings” control on the website to withdraw or change a choice. Withdrawal is as accessible as giving consent. We stop future optional activity covered by the withdrawn choice and remove first-party optional identifiers where technically possible. A provider may retain information already lawfully received under its applicable retention rules; a separate privacy request may be needed for that information.
Refusing optional tracking does not remove access to the core paid service. An optional embedded feature may instead show a placeholder that lets you activate that particular content. We keep proportionate records of consent and rejection so that your choices can be respected and demonstrated.
5. Advertising and server-side events
Where advertising measurement is enabled, the register identifies the provider, events and relevant data categories. Hashing an email address does not automatically make it anonymous. We do not place deal-document contents, sensitive transaction information or confidential valuation inputs into advertising events or audience files.
Server-side events and conversion APIs must follow the applicable privacy rules and consent choices; they are not used to bypass a refusal made in the browser. Any separately proposed customer-list audience use requires its own lawful basis, disclosure and controls.
6. Technology inventory
| Category | Technology, provider and purpose | Duration and legal treatment |
|---|---|---|
| Authentication and session security | Your sign-in session (sb-bwdqywxthonvjsjpezeq-auth-token), placed in your browser's local storage on our own domain by our authentication provider, Supabase, when you sign in, and refreshed while you use the product; a client-portal session (portalSession) for sellers using the portal; and a workspace invitation you opened (pendingInviteToken), held until you have signed in and then removed. | The session lasts until you sign out or it expires without being refreshed; the portal session ends when you close the browser; the invitation is removed once used. Strictly necessary to provide the account or link you asked to use, so no consent is sought. |
| Consent preferences | tv_cookie_consent, in local storage: which optional categories you accepted or refused, when, and the version of the choices you were offered. | Kept for 12 months from your choice, after which we ask again, and renewed if the categories change. Strictly necessary to honour your choice. |
| Optional preferences | Settings you choose in the product, stored in your browser so that they are honoured next time: interface language (preferred_language), light or dark theme (theme), sidebar, dashboard and deal-page layout choices, favourites and recently visited pages, saved export and notification settings, reminders you set, autosaved drafts of forms you are completing, the home-page audience you selected (tv_home_audience), the demo mode you entered (tv-demo-mode) and prompts you dismissed. None is sent to a third party. | Local-storage items stay until you change or clear them; session-storage items end when you close the browser. Each is stored only when you make the choice it records, as the means of providing what you asked for, so no separate consent is sought. |
| Optional analytics | Our own first-party site measurement, with no third-party analytics service: a random browser identifier (tv_site_session_id) and the referrer and campaign parameters of your first visit (tv_site_attribution), stored in local storage and sent with page views and clicks on the public site to our own database; and, where you arrived through an M&A Network professional's link, that referral (tv_network_ref), kept so the introduction is credited if you sign up. | Activated only after you accept site measurement in our consent control. The identifier and attribution stay until you withdraw or clear them; the referral for 90 days. Withdrawing consent stops the measurement and deletes all three at once. |
| Advertising | The Meta Pixel (Meta Platforms Ireland Limited), loaded from connect.facebook.net only after you accept advertising. It sets the _fbp cookie, and _fbc when you arrive from a Meta advert, on our domain, and reports to Meta the pages you view, a visit to the pricing or feature pages, the start of sign-up, a completed registration and a free-tool request, with the page address. Under the same consent our server sends those events to Meta's Conversions API with your IP address, browser identifier and, on a registration or free-tool request, your email address hashed with SHA-256, so Meta can de-duplicate the browser and server copies. Purpose: measuring our Meta advertising and building audiences for it. | _fbp and _fbc last three months. Meta holds the events under its own terms as an independent controller. Consent is sought before anything is loaded; withdrawing it stops the pixel and the server events, removes the two cookies, and the pixel is not loaded on your next page. |
| Advertising | The OpenAI / ChatGPT Ads Measurement Pixel, loaded from bzrcdn.openai.com only after you accept advertising. When a visit comes from a ChatGPT advert, the pixel records the ad reference from the landing URL and may store OpenAI's first-party measurement cookies (__oppref and __obref). We send the standard conversion events registration_completed, checkout_started and subscription_created so we can attribute TrueValue sign-ups, accepted checkout starts and confirmed subscriptions to ChatGPT advertising. We do not send deal documents, valuation inputs, names, email addresses or card details in these event payloads. | Activated only after advertising consent. Withdrawing consent tells the OpenAI measurement SDK to stop future event pings and removes the first-party measurement cookies from our domain where technically possible. OpenAI retains advertising measurement data under its applicable advertising and privacy terms. |
| Embedded videos, forms or third-party widgets | None. We embed no third-party video, form, chat or map widget. Fonts are loaded from Google Fonts (Google LLC): the request for the font files carries your IP address and browser details to Google, which sets no cookie for it. | Nothing is stored on your device. The font request is needed to display the site as designed and is not consent-based. |
Browser-level expiry and a provider's retention of event data are different. The final register must disclose both where relevant; a session cookie label must not conceal long-term event storage.
7. Browser controls and third-party choices
You can also use browser settings to inspect, block or delete stored information. Browser deletion may remove the saved record of your choice and cause us to ask again. It may not erase records already held by us or another provider. Some controls apply only to one browser or device.
A provider's advertising preference tool is additional to, not a replacement for, the choices we must offer on TrueValue. We do not rely solely on browser settings as the mechanism for obtaining initial consent.
8. Changes and contact
We review the inventory when technologies or purposes change. Where a material new optional purpose requires consent, we request it before activation rather than relying on an old choice. The publication date identifies this policy version.
For questions, withdrawal assistance or complaints, contact privacy@truevalue.business. You may also use the Complaints Policy or contact the Information Commissioner's Office.