Contextual Agentic

Privacy notice

What this site collects, why, how long it is kept, and how to have it removed.

Who is responsible

This site is published by the author of The Contextual Agentic Enterprise. It is a personal publishing site, not a company product. Contact details are on the contact page.

What the site collects

The site is static. Browsing it does not create an account, does not set any cookie, and does not load any third-party script, font or embed. There is no advertising network and no cross-site tracking.

Four things you can choose to do send information to the server:

Launch and course updates

If you submit the updates form, the server records your email address, the interests you ticked, the page you submitted from, the time you consented, and the version of this notice that was current at that moment. It then sends one message asking you to confirm.

Nothing is stored against your address until you confirm. If you do not confirm, the pending record expires and is deleted. Every message includes a one-click unsubscribe link. Unsubscribing is permanent: an address that has unsubscribed is not silently re-subscribed if the form is submitted again.

Contact messages

If you submit the contact form, the server records your name, email address, chosen topic and message, so that it can be answered. It is kept only as long as it takes to deal with the enquiry and any follow-up.

Corrections to the book

If you report a correction, the server records the edition, the location, your description, and — only if you supply one — an email address so a follow-up question can be asked. Corrections enter a moderation queue. Nothing you submit is published automatically, and your email address is never published.

Companion-code access

If you choose to get the companion code, you sign in with GitHub. GitHub tells this site your public GitHub account number and username — nothing else: no email address, no repositories, no permission to act on your account. The sign-in token GitHub issues is used once, to learn those two facts, and is then discarded.

When you answer the question correctly, the server records your account number, username, the time and which question you answered, and asks GitHub to invite that username to the private companion repository with read-only access. That record is what lets access be restored if the invitation expires, or removed if you ask.

If you answer incorrectly, a counter of wrong answers is kept against your account number for up to 36 hours, to limit guessing. Your answers themselves are not stored.

What the site does not collect

  • No analytics or advertising trackers are loaded.
  • No tracking or advertising cookies. Browsing sets no cookie at all. Only if you use companion-code access are two strictly necessary cookies set: ca_oauth, for up to 10 minutes, which protects the GitHub sign-in against forgery; and ca_reader, for up to an hour, which remembers that you are signed in while you answer. Both are inaccessible to scripts and are removed when you sign out or they expire.
  • The only other browser storage is a single localStorage entry recording whether you chose the light or dark theme, which stays in your browser and is never sent anywhere.
  • No purchase receipts, order numbers or proof-of-purchase documents are collected.

Retention

What Kept for
Unconfirmed subscription Until the confirmation link expires, then deleted
Confirmed subscription Until you unsubscribe
Unsubscribe record Kept indefinitely, so you are not re-subscribed by mistake
Contact message Until the enquiry is closed, and no more than 24 months
Correction report Until the correction is published or rejected, and no more than 24 months
Companion-code access record Until you ask for it to be removed, or the companion repository is retired
Wrong-answer counter Up to 36 hours

Processors

Requests are served by Cloudflare, which processes connection data (including IP address) to deliver the site and to apply rate limiting. Email is sent by the configured email provider recorded in the deployment configuration. Companion-code sign-in and invitations are handled by GitHub, Inc.; what GitHub does with your account is governed by GitHub’s own privacy statement. Addresses and tokens are redacted from application logs.

Your rights

You can ask for a copy of what is held about you, ask for it to be corrected, or ask for it to be deleted. Use the contact form and choose “Something else”, or use the unsubscribe link in any message. Requests are actioned within 30 days.

Depending on where you live you may also have a right to complain to a data protection authority.

Last updated 22 September 2026.