Cookies and tracking.

The conference pages and the Studio sales page do not write a cookie to recognize you on a later visit. The Studio form and the submission form do not store a cookie in your browser. The short-lived rate limit on those forms is kept on the server, and it is described in the privacy notice.

Signing in at /portal is different. Firebase Authentication keeps that sign-in in this browser’s storage so you stay signed in on this device. It is the session for an invited client account. It is not an analytics cookie, and the conference pages do not set it. You can sign out in the portal, or clear the site’s data in the browser.

The repository contains a script that can save progress for a small on-site exercise in the browser’s local storage, and only after a person opts in. That script is not loaded by any page on this site. If we turn it on, it will ask first, and this page will say so before it runs.

Register Now opens a form on Jotform. Jotform sets its own cookies. GitHub, LinkedIn, and cohorts.algorithmacy.org do the same when you follow those links. Their notices apply on their sites, not this one.

Paying in the portal opens a page on Stripe. Stripe sets its own cookies there. Stripe’s notice applies on that page.

Your browser, a password manager, or a security tool may store something of its own. That is the browser, not a tag we installed.

If we add analytics or any other cookie that is not strictly required to answer a form you submitted, we will describe it on this page before it runs, and the date at the top will change. Questions: rhunt@bentley.edu.