Privacy Policy
Last updated August 2026
This site is a marketing website, a scheduler, and a calculator. This page names every third party it hands data to, says what each one receives, and tells you how to stop them. The list is generated from the site's own source code and checked on every build, so it cannot quietly fall out of date.
The short version
You can read every page on this site without giving us anything. There is no account, no login, and no wall.
Nothing you type into the Coherence Calculator reaches us or anyone else. It is computed in your browser and stays there.
We do not sell the information you give us, and we do not hand your name, your email address, or anything you tell us to another company so they can market to you.
We do run analytics and advertising tags, and those share your browsing data with Google, LinkedIn, and Swan. Every one of them is named further down with what it takes, because a policy that says "a small number of third-party services" is not a disclosure.
What you give us on purpose
When you ask for a resource, such as the Cost of Incoherence brief, we collect your email address and which resource you asked for. We store that in our content system and use it to send you the resource and to follow up about related work.
When you book a call, Calendly collects your name, your email address, the time you chose, and anything you type into its booking form. We use it to prepare for the conversation.
When you email us, we keep the email.
That is the complete list. There is no other form on this site, and no field anywhere asks for anything we have not named here.
What the calculator does not do
The Coherence Calculator asks for revenue, contract value, headcount, and similar figures. None of it is sent to a server. The arithmetic runs in your browser, the inputs are held in the page address, and there is no account and no stored record. We could not show you your own numbers back, because we never had them.
The share link carries those figures inside the link itself. That is what makes it work without an account, and it means anyone you send the link to can read the numbers. Treat it the way you would treat the spreadsheet it replaces.
We also keep those figures out of our own measurement. The page address is stripped of the figures before any analytics event leaves your browser, and if session recording is ever switched on, every input and every number the page displays is masked before it is sent. The masking is applied in the browser, so the unmasked version never leaves your device.
The calculator stores one flag in your browser session, recording that you have interacted with it, so a single visit is not counted as several. It contains no figures and no identifier.
What is collected automatically
Every request for a page reaches our host, Vercel, which sees your IP address, your browser and device type, and the address you asked for. Any website works this way.
On top of that, the site loads measurement and advertising tags. Between them they collect your IP address, the page you are on, the page you came from, your device and browser, and cookie identifiers. They are listed individually below.
We set one cookie of our own, and only on an internal, passphrase-protected area of the site that is not linked from anywhere public. It holds no information about you. Every other cookie on this site is set by one of the companies named below.
When you submit the resource form, we briefly hold your IP address in memory to limit how often the form can be submitted. It is not written to storage and does not survive the server restarting.
Every third party, by name
This list is not maintained by hand. It is generated from a registry in the site source code, and an automated test loads a real build of the site, watches every network request it makes, and fails when the site contacts a company the registry does not name. That test runs on every change we propose to this site, so the disclosure and the site are checked against each other by a machine rather than by whoever remembers.
Each company below uses what it receives under its own privacy policy, not ours.
Google Tag Manager
- What it receives
- Page URL, referrer, user agent, IP address, and a client identifier.
- Why it is here
- Loads and manages the other measurement tags on this site. It is the container the analytics and advertising tags below are configured in.
- When
- Every page you open. Loaded directly by this site.
- Where to find it in a network log
- googletagmanager.com
Google Analytics 4
- What it receives
- Pages viewed, events such as form submissions and downloads, approximate location from IP address, device and browser, and a first-party cookie identifier.
- Why it is here
- Traffic and conversion reporting. Which pages bring in enquiries and which do not.
- When
- Every page you open. Loaded through our Google Tag Manager container.
- Where to find it in a network log
- google-analytics.com, analytics.google.com, g.doubleclick.net
PostHog
Configured but not currently running- What it receives
- Named product events with their properties, page URLs with the calculator payload removed, and a session recording with every form input masked before it leaves the browser.
- Why it is here
- Product analytics for the tools on this site: which steps people complete, where they stop, and what the calculator is actually used for.
- When
- Every page you open. Loaded directly by this site.
- Where to find it in a network log
- posthog.com
LinkedIn Insight Tag
- What it receives
- Page URL, referrer, IP address, device and browser, and LinkedIn cookies where the visitor has a LinkedIn account.
- Why it is here
- Attributing LinkedIn advertising to what happens on this site, and building audiences for LinkedIn campaigns.
- When
- Every page you open. Loaded through our Google Tag Manager container.
- Where to find it in a network log
- licdn.com, linkedin.com
Swan
- What it receives
- Page URL, referrer, IP address, and pages viewed during the visit.
- Why it is here
- Identifying which companies are reading the site so outbound follow-up goes to businesses that have already shown interest.
- When
- Every page you open. Loaded through our Google Tag Manager container.
- Where to find it in a network log
- getswan.com
usbrowserspeed
- What it receives
- IP address, user agent, page URL, and identity cookies set across a network of sites.
- Why it is here
- The identity-resolution host behind Swan above. It is listed separately and by its real name because the domain gives no hint of what it is, and a visitor reading a network log deserves to find it here rather than work it out.
- When
- Every page you open. Loaded through our Google Tag Manager container.
- Where to find it in a network log
- usbrowserspeed.com
IP-API
- What it receives
- IP address, and in return the city, region, country, timezone and network operator it resolves to.
- Why it is here
- Geolocation lookup performed by the Swan tag above. It was found by the registry check on this page rather than by anyone writing it down, which is the reason that check exists.
- When
- Every page you open. Loaded through our Google Tag Manager container.
- Where to find it in a network log
- ip-api.com
Calendly
- What it receives
- Name, email address, and anything typed into the booking form, plus the meeting time selected.
- Why it is here
- Scheduling calls. It loads on /book and nowhere else.
- When
- Only when you use the feature it belongs to. Loaded directly by this site.
- Where to find it in a network log
- calendly.com
Sanity
- What it receives
- IP address and user agent, from requests for images stored in the CMS.
- Why it is here
- The content management system this site renders from. Page text is fetched server side; images are served to the browser directly from their CDN.
- When
- Every page you open. Loaded directly by this site.
- Where to find it in a network log
- sanity.io
Vercel
- What it receives
- IP address, user agent, and requested URL, as the host serving every page.
- Why it is here
- Hosting and content delivery for this site.
- When
- Every page you open. Makes no request of its own. It receives the data by serving the page.
Advertising and visitor identification
Two of the tools above deserve more than an entry in a list, because they do the thing people most object to and would be easy to leave vague.
The LinkedIn Insight Tag reports your visit to LinkedIn and lets us build advertising audiences there. If you are signed in to LinkedIn, LinkedIn can connect this visit to your account. What LinkedIn then does with it is governed by LinkedIn, not by us.
Swan works out which company a visitor is coming from, so that our outbound follow-up goes to businesses that have already shown interest. It does this through an identity resolution network, usbrowserspeed.com, which sets cookies across a large number of unrelated sites, and it resolves your IP address to a location and network operator through IP-API.
That is company-level identification, performed without asking you first. We think you should know it is happening rather than find it in a network log. Blocking third-party cookies, or running any ordinary tracking blocker, stops all of it, and nothing on this site breaks when you do.
Some privacy laws define selling and sharing broadly enough to cover advertising and identification tags like these, whether or not money changes hands. No money is paid to us for any of it. Rather than argue about which label applies, we have described exactly what happens and named everyone involved.
Artificial intelligence
No AI model runs on your data on this site. There is no chatbot, no assistant, and no automated analysis of anything you type here.
An earlier tool on this site, the Coherence Signal, analysed publicly available information about companies. It has been retired, and its pages now redirect to our diagnostic page.
We publish two machine-readable files, llms.txt and llms-full.txt, for AI search engines. They carry the text of our own published articles and glossary. They contain nothing about visitors.
We do use AI tools inside client engagements. That work is governed by the agreement we sign with the client, not by this page.
How to turn it off
We do not currently run a cookie consent banner, so the tags described above load for everyone who visits. Being straightforward about that is more useful than a banner that most people dismiss without reading.
Any browser tracking protection or content blocker stops the advertising and identification tags. Blocking third-party cookies alone stops most of them. The site is built to work without any of them, so nothing you came here to read or use will break.
Google publishes a browser add-on that opts you out of Google Analytics across every site that uses it. LinkedIn lets you turn off off-site advertising data in your LinkedIn advertising settings.
You can also just ask us. Email the address at the bottom of this page and we will remove what we hold.
How long we keep it
Resource requests and booking records are kept while a working relationship is realistic, and afterwards only as long as ordinary business and tax obligations require. Ask us to delete yours and we will.
Analytics and advertising data is held by the companies named above, on their own retention schedules, and we cannot delete it on their systems for you. The opt-out routes in the previous section are the effective control there.
Your choices
You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Email the address below and we will do it.
We apply this wherever you live. We are not going to ask you to establish that you are covered by a law that requires it.
Changes to this page
When we add something that touches visitor data, this page changes in the same commit, because the build fails otherwise. The date at the top is the last time that happened.
Contact
Questions about this policy or your data can be sent to privacy@goldenratiogtm.com.
