This page describes exactly what the Cadrian site collects, where it goes, and how to get it deleted. It is written from the code that runs on the page, not from a template.
What you send us
The form asks for two things, and sends them in two steps.
- Your email address. Step one. We send it to ourselves the moment you submit that step — before you have written your question — recorded with the stage
partial. We do this so that a click from a paid ad still leaves us a way to reach you if you stop at step two. - Your question. Step two. Free text, up to 700 characters. It is sent together with your email, recorded with the stage
complete. - The time you submitted, as a UTC timestamp.
That is the whole form. We do not ask for your name, your company, or your phone number, and no field is pre-filled from anywhere else.
There is one field you cannot see: an empty anti-spam trap, positioned off-screen. A person filling in the form never touches it, so it always arrives empty. When something has been typed into it, the submission came from a bot — our server drops it and stores nothing.
How we know which ad brought you
On your first pageview we read the URL and save a short attribution record in your browser’ssessionStorage, under the key cadrian.attribution. It holds whichever of these are present:
- the campaign tags on the link —
utm_source,utm_medium,utm_campaign,utm_content,utm_term - the ad click identifier —
li_fat_id(LinkedIn),gclid(Google),fbclid(Meta) - the path of the page you landed on
- the page you came from, or the word
directwhen there was not one - the time it was captured
This record is sent along with your email and question when you submit. Its only job is to tell us which ad or link brought you here. First touch wins: a later pageview does not overwrite it. It lives in sessionStorage, so your browser drops it when you close the tab. If your browser blocks storage, we skip it and the form still works.
Analytics: PostHog
We use PostHog for product analytics. This deployment is configured to send analytics to https://us.i.posthog.com. The script is not part of the initial page load — it is fetched lazily once your browser goes idle, and only when a project key is configured. On a deployment without one, PostHog is simply absent.
PostHog records:
- pageviews and page-leaves — which page, when, and how long you stayed;
- one event when you complete the form, carrying whether you wrote a question and how many characters it was — not the text of it — plus the attribution values above.
Until you submit, you are anonymous to us. PostHog is configured withperson_profiles: "identified_only", so no person profile is created for someone who only reads the page. When you submit, we identify you in PostHog by your email address, and that visit is joined to it.
PostHog keeps an anonymous device id in your browser using both localStorage and a cookie, so two visits from the same browser count as one person rather than two.
Advertising: LinkedIn
When a deployment has a LinkedIn partner ID configured, the page loads the LinkedIn Insight Tag. We run it inside a web worker rather than on the main thread, but that is a speed choice only — it does what LinkedIn’s tag normally does: tells LinkedIn a page was viewed, and reads and writes LinkedIn’s own cookies. With JavaScript switched off, a one-pixel image sends a pageview request carrying the configured partner ID to px.ads.linkedin.com.
After our lead endpoint accepts your submission, we fire one conversion event to LinkedIn so the campaign that brought you here gets credited. That event carries a conversion id. It does not carry your email address or your question.
With no partner ID configured, none of this is on the page at all.
Fonts
The page loads its typefaces from Google Fonts (fonts.googleapis.com andfonts.gstatic.com). Your browser requests those files directly, so Google sees your IP address and user agent. We send Google nothing else.
Where your lead ends up
The form posts to /api/lead on this site — the one route here that runs on a server rather than being a static file. It checks the submission, then writes it into our CRM, Attio. Your browser never talks to Attio directly; the key that would let it do so stays on our server.
In Attio you become a person record keyed by your email address, with an entry on our leads list holding your question, the stage, the campaign tags, the LinkedIn click id, the page you landed on, and where you came from. If the write to Attio fails, our server logs the failure — the stage and the error, not your email or your question — so we can find out why.
Who else sees it
Three processors, each doing one job:
- Attio — our CRM. Holds the lead itself.
- PostHog — product analytics. Holds pageview and event data, and your email as an identifier once you have submitted.
- LinkedIn — ad measurement. Holds the pageview and conversion signals from its Insight Tag, under its own cookies.
Google sees your IP address incidentally, because the fonts are served from there. That is the whole list. We do not sell your data, and we do not pass it to data brokers, enrichment vendors, or mailing lists.
Cookies and browser storage
cadrian.attribution—sessionStorage, set by us. Ad attribution. Cleared when you close the tab.- PostHog’s entries —
localStorageand a cookie, set by PostHog. An anonymous device id and queued events. Persists until you clear site data. - LinkedIn’s cookies — set by the Insight Tag. Ad measurement. LinkedIn controls how long they last.
We set nothing else. The ?theme= parameter in the URL is read on load and never stored. Clearing site data removes ours and PostHog’s. Blocking third-party scripts stops PostHog and LinkedIn completely — the form still works without them.
How long we keep it
- The lead in Attio — kept while the conversation is live, and afterwards as our record of it. There is no automatic expiry today. If we add one, this page will say so.
- PostHog — held under our PostHog project’s retention setting, which is theirs to enforce and ours to configure.
- LinkedIn — LinkedIn’s own retention. We do not control it and cannot shorten it.
Getting your data deleted
Email hello@cadrian.ai, from the address you gave us or naming it. We will delete the record in Attio, delete the PostHog person and their events — your email is the identifier there, so it is findable — and confirm when it is done. We aim to do that within 30 days.
You can ask for a copy of what we hold, or ask us to correct it, at the same address. What LinkedIn holds about your browser is not ours to delete; LinkedIn’s own ad and cookie settings cover that.
Children
This site is for people working in sales and go-to-market roles. It is not for anyone under 16, and we do not knowingly collect anything from them.
Changes
When what we collect changes, this page changes with it and the date at the top moves. It is meant to describe the code as deployed — if you find a mismatch, that is a bug, and we would like to hear about it.