Privacy notice

Who is responsible

This site is published by the Contextual Agentic team, the authors of The Contextual Agentic Enterprise. It is an independent 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 loads no third-party font or embed. There is no advertising network and no cross-site tracking.

Visitor statistics

To see how many people read the site and which pages they read, the site uses Cloudflare Web Analytics, a privacy-first service from the company that hosts it. A small script sends Cloudflare a record of each page view: the page address, the referring page, the browser and device type, the country (derived from your IP address, which is not stored for this purpose), and page-load timings.

It sets no cookies, uses no browser storage, does not fingerprint your device, and does not build a profile of you or follow you across other sites. The team sees only totals, such as page views per article, top countries and top referring sites, never individual visitors. Cloudflare’s own handling of this data is described in its privacy policy. If you block the script, the site works exactly the same.

When you click a share button, copy an article’s link or follow the LinkedIn Page from this site, the site also counts that click: which of those it was, which article, and where on the page. It stores no address, cookie or identifier with the count, so it counts clicks, not people, and it cannot tell whether a click led to a share or a follow. If a counting database is not connected, nothing is kept. Blocking scripts stops it.

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.

Guides and advisory enquiries

When guide requests are open, asking for a guide collects your name, email address, organisation (or that you are an individual), role, industry, main interest and main challenge (both chosen from a list, not typed). Nothing you type is applied to a record until you open the link we email you, which proves the address is yours. The link works once and expires after 30 minutes.

Getting a guide never requires you to receive anything from us. Two optional boxes, both unticked, let you ask for book and resource updates or the general newsletter. Because someone else could type your address, ticking a box is not enough: the page you reach from the emailed link asks you again, unticked, and only what you tick there is recorded. Each choice is recorded separately with its wording version, the time you ticked it, the time you confirmed it and its source, and you can withdraw either at any time. Withdrawing keeps a record that you did, and asking for a guide again does not bring a withdrawn choice back. Asking for an advisory discussion authorises a reply to that one enquiry only. It does not subscribe you to anything, and withdrawing the enquiry or an update choice never changes the other. An enquiry may also collect organisation size, region, use case, adoption stage, desired support, timeframe, your involvement, an optional budget range and how you would like to be contacted. Please do not put confidential architecture, customer records, credentials or security incident details in any form here; ask for a private channel first.

Records are held in a database at Cloudflare. They are not passed to Polymath Signal Press or any other organisation. Counts of steps taken (for example, guide requested, link used, guide downloaded) are kept without names, addresses or free text. A file being served does not show that it was opened or read. Once downloaded, a file can be copied and shared; the sign-in step cannot prevent that.

What the site does not collect

• No advertising trackers, and no analytics that use cookies or identify individual visitors.
• 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. If you request a guide and open the emailed link, one further strictly necessary cookie, __Host-cae_session, keeps you signed in for up to seven days so you can download the guide. Signing in again later from the Sign in page sets the same cookie. It is inaccessible to scripts and removed when you sign out or it expires.
• 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

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.