Privacy

What this site collects

No email addresses, for now. Seeing the Unseen is published on LinkedIn and in the archive on this site. There is no subscribe form until an email service is connected. When there is, it will take an email address and nothing else, and this page will say so before the form goes live.

Ordinary server logs. Like every site on the internet, requests reach a server that records that they happened: the page requested, a timestamp, an IP address, a user agent. This is how a web server works rather than a decision anyone made about you, and it is not joined to anything else.

Aggregate page counts. Vercel Analytics is cookieless and does not build a profile — it can tell me that a post was read four hundred times, not who read it. Google Tag Manager (container GTM-NJHPG32J) loads measurement tags from this site, including Google Analytics if it is connected through that container. Those tags record page views, the referring site, device and browser, and an approximate location, so I can see which articles are read. It is not used for ads or remarketing on this site.

What it does not collect

• No advertising pixels. No Meta pixel, no LinkedIn Insight tag, no Google Ads remarketing.
• No cross-site tracking, no fingerprinting, no session recording, no heatmaps.
• No data brokers, no enrichment services, no reverse-IP company lookup.
• No contact form. Booking goes through a calendar and email goes to my inbox.
• Nothing is sold, rented, or traded. There is no list to sell — see below.

Why, and on what basis

Once email signups open, the address will exist for one purpose: to send you Seeing the Unseen. It will not be passed to Zerentro’s CRM and it will not trigger anyone following up with you.

The lawful basis will be your consent, given by submitting the form and confirming the address, and you will be able to withdraw it at any time. Server logs rest on legitimate interest: a site that cannot log requests cannot be kept online or secure.

Who else touches it

A short, complete list. Each of these has its own privacy policy, and where they handle anything on my behalf they do so as a processor.

• Vercel — hosting and, in production, cookieless analytics. All traffic to this site passes through them.
• Google Tag Manager — the container that loads measurement tags on this site. Tags fired through it (including Google Analytics, if connected) send page URL, referrer and device data to Google, under Google’s privacy policy.
• Calendly — the booking calendar on the work with me page. If you book a call, the name, email and anything you type go to Calendly and then to my calendar. If you never open that page, Calendly never sees you.
• LinkedIn — where a newsletter edition is embedded on the editions page, LinkedIn serves that post in a frame and will see the request. Nothing on this site is embedded from LinkedIn anywhere else.
• An email provider — none yet. This page will name the service before any signup form goes live.

Cookies and tracking

Google Tag Manager itself is a loader. Tags fired through it — including Google Analytics, if connected — may set first-party cookies (_ga, _ga_*) so repeat visits can be counted. This site sets no other cookies of its own. The Calendly embed on the work with me page may set its own cookies when you interact with it, and so may a LinkedIn embed; both are third parties in a frame and both are covered by their own policies.

How long it is kept

Your email address is kept until you unsubscribe or ask for it to be removed, whichever comes first. There is no reactivation campaign and no dormant-subscriber archive. Server logs roll off on the host’s own schedule, measured in weeks, and nobody reads them unless something is broken.

Your rights

Depending on where you live you may have a formal right to access the data held about you, correct it, delete it, take a copy elsewhere, or object to it being processed. Rather than route that through a form: write to me and I will do it.

In practice, on a list this size, “what do you have on me” is answered in a sentence — an email address and the date you gave it — and “delete me” takes about a minute. I will confirm when it is done. You do not have to explain why, and asking will not get you a retention offer.

Where the data sits

The services above operate globally, so data may be processed outside the country you are reading from — most likely in the United States or the European Union, depending on the provider’s own routing. If cross-border processing is a problem for you, do not subscribe; the entire archive is public on this site and no email is required to read any of it.

Children

This site is written for people who run enterprise finance, operations and data functions. It is not directed at children, and I do not knowingly collect anything from anyone under 16. If you believe a child has subscribed, tell me and I will remove the address.

Changes to this page

When the practices change, this page changes and the date at the top moves. If a change is material — a new processor, a new purpose, anything that alters what happens to your address — subscribers get told in an issue rather than being left to notice a silent edit.

Contact

Everything above runs through one channel: a LinkedIn message. Deletion requests, questions about a processor, or an argument that something here is wrong — all the same place, and I answer them myself.