— Privacy notice
Privacy.
We tell clients that a revenue system should be inspectable: you should be able to see what it did and why. This page applies that standard to what this site knows about you.
The short version
This site collects almost nothing on its own. We know what pages are viewed, in aggregate and without cookies. We do not record your screen, follow you across other sites, or build a profile of you.
The one place you give us personal information is a form you choose to fill in. That goes to HubSpot, our customer relationship system, so a person here can reply to you.
When you contact us
The contact form and the Outcome Engine plan request send what you typed to HubSpot. That is first name, last name, email address, company if you gave one, and your message or plan summary. We also send the address of the page you submitted from, so we can tell which part of the site prompted you to get in touch.
We use it to answer you and to manage the working relationship that follows. We do not sell it, and we do not share it with anyone outside the providers listed below.
The form has a hidden field that is always left empty. It catches automated spam, and nothing typed into it reaches us.
Cookies and browser storage
HubSpot sets cookies when you visit, including the one our forms read to connect your enquiry to your earlier visits. HubSpot documents the full list it sets. You can block or clear these in your browser at any time; the forms still work without them, they just arrive without that history attached.
The site itself keeps three small things, none of which leave your browser or identify you:
- indigo-trigger-theme — a cookie remembering whether you chose light or dark, for a year.
- indigo-trigger:outcome-engine — the answers you give the Outcome Engine, so they survive moving between pages.
- indigo-trigger:site-alerts-dismissed — which announcements you have closed, so we stop showing them.
What stays in your browser
The Outcome Engine is worth calling out. Everything you tell it — the outcomes you pick, the numbers you enter, what you flag as a problem — is held in your own browser and is not sent to us as you work. It reaches us only at the point you submit the plan request, and then only the summary shown to you on screen. Clearing your browser storage erases it completely, from our side as well, because we never had a copy.
Analytics
We use PostHog to count how the site is used, configured to be as close to anonymous as the tool allows. It runs in cookieless mode and sets no persistent identifier, so we cannot recognise a returning visitor. It honours a Do Not Track signal from your browser.
It is also restricted at our end rather than only in its settings. Session recording, autocapture, heatmaps, console capture, and performance capture are all switched off. The page text and form fields are masked. Only a fixed list of events can be sent; anything else is dropped before it leaves your browser, as is anything from an admin or API address. Query strings are stripped from every URL, and any property whose name looks like a name, email, company, message, question, or answer is removed.
The result is that we can see a page was viewed or a form was submitted. We cannot see who did it or what they wrote. If Core Web Vitals reporting is switched on, Vercel Speed Insights measures loading performance on public pages only.
Server logs and security
Our server records a request identifier, which route was called, the status, the outcome, and how long it took. It does not record what you submitted, your cookies, or any part of a message.
Public endpoints are rate limited, which means your network address is held in memory briefly to count requests. It is never written to a log or stored.
Who processes this information
We keep the list of providers short on purpose. Each one is a processor acting on our instructions:
- HubSpot — customer relationship management, form submissions, and site analytics.
- Vercel — hosting, content delivery, and media storage.
- Neon — the PostgreSQL database behind the site.
- PostHog — anonymous, cookieless site analytics.
Where it is processed
Indigo Trigger is based in the United States and our providers process this information in the United States. If you are contacting us from elsewhere, your information will be transferred there.
How long we keep it
An enquiry stays in HubSpot for as long as we are in touch and for as long as we need the record of our dealings with you. Analytics events carry no identifier, so there is nothing in them to attach to you. Ask us to delete what we hold and we will.
Your choices
Write to us and we will tell you what we hold about you, correct it, or delete it. Depending on where you live you may have a formal right to those things; we would rather just do it than argue about which law applies.
You can clear or block cookies in your browser, and turning on Do Not Track will stop our analytics entirely.
Artificial intelligence
The public site does not currently run an AI assistant, and nothing you type into it is sent to a language model. If that changes, this page will describe what is sent, to whom, and what is kept before the feature goes live.
Changes, and how to reach us
If this notice changes materially we will update the date below rather than quietly revise it. Questions, corrections, or a request about your own information:
info@indigotrigger.com
Indigo Trigger LLC, 5 Market St. Suite 1, Portsmouth, NH 03801
Effective 17 September 2026
