Privacy notice

This page says what fredriklindstrom.info collects when you use it, who receives it, and how long it is kept. It covers this site only. Beehiiv’s newsletter pages and Cal.com’s booking pages carry their own notices.

Two things first. The AI Governance Game sends your game inputs to Anthropic’s Claude, which writes your scenario and debrief, and the game says so on screen. The Director Edition has a free-text field for a recent incident: do not put confidential or personal information in it (why).

Who is responsible

I am Fredrik Lindstrom, an independent practitioner based in the United States. I run this site myself, and I am the controller for the personal data it collects. Write to fredrik@fredriklindstrom.info with any question about this notice, or to use the rights listed below.

At a glance

What I collect, where, and why

Every page: hosting

IONOS hosts the site. When your browser asks for a page, or downloads one of the PDF guides, the IONOS server receives the standard request data: your IP address, browser type, the page address (including any campaign tags in it), the page you came from, and the time. IONOS keeps server logs under its own retention settings. The server sets no cookies.

Why: to deliver the site and keep the server secure. Legal basis: legitimate interests (GDPR Art. 6(1)(f)). A website cannot reach you without your IP address.

Every page: typefaces

The site’s typefaces are served from this site. No font request goes to Google or to anyone else.

Every page: site analytics

Cloudflare Web Analytics counts page views. A small script sends Cloudflare the page address, the page you came from, browser details and load-time measurements, and the connection itself gives Cloudflare your IP address. Cloudflare states that it uses no cookies or local storage for this and does not fingerprint visitors. The dashboard shows totals, not individual visitors.

Why: to know which pages people read. Legal basis: legitimate interests (Art. 6(1)(f)). Kept: Cloudflare keeps full beacon data for seven days, then an aggregated sample. The dashboard shows the last six months.

Pages with a newsletter form: Beehiiv’s attribution cookie

The homepage, each article and /subscribe/ carry Beehiiv’s sign-up form, and on those pages only a Beehiiv script loads with it. Loading it gives Beehiiv your IP address, browser details and the page you came from.

If you arrive on one of those pages through a link with campaign tags (utm_source and similar), with an ad-click ID, or from another website such as LinkedIn, the script stores a cookie on this site called attribution_data. It holds the campaign tags, the name of the ad network (not the click ID itself), the site and address you came from, the page you landed on, and a timestamp. It expires after 30 days. When you sign up, the script passes these values to Beehiiv with the form, so Beehiiv can record where a sign-up came from.

This is the only cookie set on fredriklindstrom.info. My own code sets none. If you block cookies for this site, the forms still work.

Why: to see which links bring newsletter subscribers.

The newsletter: The Governance Memo

You can subscribe in four places. All of them end at Beehiiv, which holds the subscriber list and sends the Memo.

• The sign-up form on the homepage, under each article, and on /subscribe/. This is Beehiiv’s own form. Your email goes from your browser straight to Beehiiv, with the campaign details described above.
• The “Twelve questions” panel. The guide is a direct download and needs nothing from you. Your email goes to Beehiiv only if you tick the box to subscribe. If you close the panel, your browser stores a date in local storage (fl-corner-offer) so the panel stays hidden for 60 days, or for good after you submit. That item holds no personal data.
• The Column Test result screen. Nothing is sent unless you tick the box. If you do, Beehiiv receives your email, your score (0 to 100) and the name of your weakest dimension. Your individual answers are not sent.
• The Director Edition sign-up. See the Director Edition section.

The last three go through a small service of mine on Cloudflare. It passes your email and a sign-up label to Beehiiv and stores nothing. Beehiiv then sends a confirmation email, and you are subscribed once you confirm.

Why: to send you the Memo, and to know which pages bring subscribers. Legal basis: your consent (Art. 6(1)(a)). Withdraw it at any time with the unsubscribe link in the Memo, or by emailing me. Kept: until you unsubscribe. After that, Beehiiv’s own retention rules apply.

The AI Governance Game

The standard game at /governance-game/ has no free-text fields: you pick a seat and choose between fixed options. The scenarios are written by me. At the end, two things happen.

Your debrief is written by AI. Your seat and your choices, with the game’s own scores and framework notes for each, go through my service on Cloudflare to Anthropic’s Claude (Claude Haiku 4.5). Claude writes the debrief you see, and the game labels it as AI-generated. Nothing that identifies you is sent.

Your score is saved without an identifier. Your seat, your choices and their scores, the time, and whether this is your first time through go to a database on Cloudflare. Your IP address, email and any other identifier are not stored. The results screen uses this database to show how your score compares with everyone else’s first attempt. To tell a first attempt from a replay, the game stores one item in your browser’s local storage (governance-game:finished) holding the date you first finished. It stays until you clear your browser storage.

Why: to write your debrief and show the comparison. Legal basis: legitimate interests (Art. 6(1)(f)) in running the game you chose to play. Kept: Anthropic deletes API inputs and outputs within 30 days by default. Score rows carry no identifier and are kept while the game runs, to compute the averages.

The Director Edition

The Director Edition at /governance-game/director-edition/ writes a scenario around your kind of organisation. It is open to Governance Memo subscribers. Everything you read in it after the sign-up is written by AI, and the game labels it that way.

Sign-up. You enter your email. My service on Cloudflare asks Beehiiv whether that address is subscribed. If it is not, or if you unsubscribed earlier, continuing asks Beehiiv to subscribe you, and Beehiiv sends a confirmation email. You then add your sector, jurisdiction, AI maturity and, if you want, a recent incident. When you press “Start the game”, Beehiiv receives your email again, with your sector, jurisdiction and maturity added to your subscriber record. The incident text is not sent to Beehiiv.

Your browser. Your email, answers and incident text are held in your browser’s session storage. That carries them from the sign-up page to the game, and to the contact page if you go there. Session storage clears when you close the tab.

The scenario. The game makes up to four calls to Anthropic’s Claude through my service on Cloudflare: an opening, two decision points and a debrief. Each call sends the seat and theme for your game, your sector, jurisdiction and maturity, and your incident text word for word (up to 500 characters). The later calls also send the story so far and the options you chose. Claude is told to build your incident into the scenario, so what it writes can repeat what you typed. Your email is never sent to Anthropic.

Error logs. If Claude’s reply cannot be read, my service logs its first 500 characters so I can fix the fault. That extract can contain your incident as Claude retold it. Cloudflare keeps these logs for no more than seven days.

Why: to check your subscription, write the scenario you asked for, and know which sectors and jurisdictions the game reaches. Legal basis: consent (Art. 6(1)(a)) for the newsletter subscription; legitimate interests (Art. 6(1)(f)) for the subscription check and for writing your scenario. Kept: Beehiiv until you unsubscribe. Anthropic deletes inputs and outputs within 30 days by default; if its automated systems flag a conversation as breaking its usage policy, Anthropic keeps it for up to two years. My service stores nothing.

Security and abuse controls

Each of my three services on Cloudflare uses your IP address to cap how many requests one visitor can make per minute. Those counters last 60 seconds and are not stored. The subscription-check service also counts checks per IP address per hour, so no one can test lists of email addresses against my subscriber list. Those counters are kept for two hours. If one IP address makes too many checks, the service logs an alert that includes the address. The services also log error messages from Beehiiv and Anthropic. Cloudflare keeps these logs for no more than seven days.

Why: to stop abuse, and to cap what the AI calls cost. Legal basis: legitimate interests (Art. 6(1)(f)).

Booking a call

The /advisory/ page embeds Cal.com’s booking calendar. It loads when you open the page, which gives Cal.com your IP address, browser details and the page address. If you book, Cal.com collects what its form asks for (your name, your email, the time you pick and any notes you add) and adds the meeting to my Microsoft 365 calendar with a Teams link.

Why: to arrange the call you asked for. Legal basis: steps taken at your request before a possible contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) for showing the calendar on the page. Kept: in Cal.com and my Microsoft 365 calendar and mailbox for as long as I need them to arrange and follow up the call.

Emailing me

The email links on the site, and the contact form on the Director Edition’s /talk/ page, open your own email program. The /talk/ form posts nothing to any server: it builds an email from your name, email, company, role and topic, and you decide whether to send it. Email reaches my Microsoft 365 mailbox.

Why: to reply to you. Legal basis: legitimate interests (Art. 6(1)(f)) in answering correspondence; steps at your request before a contract (Art. 6(1)(b)) when you ask about working together.

Do you have to give me anything?

No. Reading the site needs nothing beyond what your browser sends. The newsletter and the Director Edition need an email address. A booking needs what Cal.com asks for.

Who receives data, and where

Most of these providers are in the United States, so your data leaves the EU and EEA when it reaches them. Ask me which transfer safeguard covers a given provider and I will send you the details. I do not sell personal data, and it goes to no one outside this table unless the law requires it.

How long data is kept

What the site does not do

• My own code sets no cookies. The one cookie comes from Beehiiv’s script, and only on pages with a newsletter form.
• No advertising or retargeting tags. No Google Analytics, no Meta pixel, no LinkedIn Insight tag.
• No third-party fonts, and no embedded YouTube or social media players.
• No accounts, logins or passwords. No payments.
• My own code puts no personal details in page addresses.
• Your email is never sent to Anthropic. The incident text is not sent to Beehiiv, and no database of mine stores it.
• No automated decisions about you. Claude writes commentary on your game choices. It decides nothing about you, and nothing it writes has a legal or similar effect on you. It can be wrong, and it is a training exercise, not advice.

Do not put confidential or personal information into the game

Whatever you type into the Director Edition’s incident field goes to Anthropic, a US company, up to four times in one game. Claude is told to build it into your scenario, and an error log can capture it. Describe the kind of event and leave out the specifics:

• No names of people, clients, suppliers or your own organisation.
• No confidential audit findings, legal advice, or anything under a non-disclosure agreement.
• No inside information or unpublished financial results.
• No health data or other special-category data about anyone.

Write “a vendor chatbot gave customers the wrong refund terms”. Leave out the vendor, the customers and the amount. The standard game has no free-text field.

Your rights

Under the GDPR you can ask me to:

• Access: tell you what I hold about you, and give you a copy.
• Rectify: correct it.
• Erase: delete it.
• Restrict: stop using it while we settle a dispute about it.
• Object: stop any processing I base on legitimate interests. I stop unless I have compelling grounds that override your interests.
• Port: give you the data you provided, where I rely on consent or a contract, in a machine-readable format.

You can also withdraw consent at any time, for example by unsubscribing; that does not affect what happened before. And you can complain to a supervisory authority, in particular in the EU country where you live, where you work, or where the problem happened. The European Data Protection Board lists them at edpb.europa.eu. You do not have to contact me first, though I would like the chance to fix it.

To use any of these rights, email fredrik@fredriklindstrom.info. I reply within one month. For a complex request I may extend that by up to two more months, and I will tell you why. I may ask you to show that the email address is yours.

One limit, stated plainly. Game scores and game text carry no name or email, so I cannot find them by your name or email. Your subscriber record, bookings and emails I can find.

Changes to this notice

When the site changes what it collects, or who receives it, I update this page and the date at the top.