Cookies

Acttuary does not use advertising cookies or cross-site tracking. We use necessary sign-in technology and a small amount of local or session storage for specific site features, all described below.

Our analytics are cookieless and do not store an analytics identifier on your device.

What is set on your device

• Sign-in cookies. If you create or use an account, Clerk sets first-party cookies required to authenticate you, maintain your session and protect the sign-in process. These are used only when necessary to provide account and security functionality. They appear once you sign in and go when you sign out.
• The names those cookies currently use. They may include cookies beginning __session, __client, __refresh or __clerk. The exact set depends on your browser and on where you are in the sign-in flow.
• What Clerk keeps in local storage. Clerk may also store configuration information locally in your browser, under __clerk_environment, so its sign-in interface can function correctly. This does not contain a record of which Acttuary content you have viewed.
• One key of ours, for the tab you are in. We write acttuary-within-site to session storage on lesson pages. It holds the value 1, meaning this tab has already visited the site, which is what shows the small “back to where you were” control after you click a defined term. No identifier, no record of what you read; it goes when you close the tab.
• A second, only while you are sitting an exam. While an exam paper is open we write acttuary-exam-answers to session storage: the reference of the paper, the list of questions it drew, the answers you have typed so far, and the working you have done in the exam’s own tools, each filed under the question it belongs to. A phone reloads a tab at the smallest excuse, and this is what brings you back to your own answers and workings rather than to empty boxes. It holds nothing about whether an answer is right: marking happens on our server after you submit. It is deleted the moment the paper is marked, and it never leaves your device.
• The bot check on the sign-in form. Clerk’s sign-in and sign-up forms can embed a Cloudflare Turnstile challenge in a frame served by Cloudflare. Whatever that frame needs is stored against Cloudflare’s own domain under their notice, not against acttuary.com, and it is there to tell a person from a script.
• Nothing else of ours. We set no cookies of our own, and those two session-storage keys are the whole of what we write. Your lesson progress, quiz scores and certificates live in your account on our server, which is why they follow you between computers. The Python and R exercises download a WebAssembly interpreter from a public CDN when you press Run; that runtime sets no cookie and writes nothing to local or session storage.

Analytics

Acttuary uses Plausible for aggregate website analytics. Our current Plausible setup does not set analytics cookies or write an analytics identifier to local storage.

Plausible receives information needed to generate aggregate statistics, including the page being viewed. We therefore do not load analytics on private booking or CV-upload pages.

When you pay

Checkout and billing management happen on Stripe’s own pages, and no Stripe script runs on acttuary.com. Stripe uses its own technologies on its own domain for payment security and fraud prevention, and is responsible for them; their notice is on the page you land on.

What we don’t use

• No advertising or retargeting pixels.
• No cross-site tracking.
• No session-recording or heatmap tools.
• No advertising profiles.
• No third-party fonts loaded for tracking purposes.

Consent

We do not currently use storage or access technologies for which our current setup requires a cookie-consent banner. The technologies described above are used for account and security functionality, the site features you have asked for, or the limited purposes described in this notice.

If our use of cookies or similar technologies changes, we will update this page and introduce a consent mechanism before using anything that requires one. Questions: hello@acttuary.com.