What we keep about you

Last updated: 10 October 2026.

Who is responsible

Chalkenso is run by Boštjan Cigan, who decides what happens to the data described here. Questions and requests: info@chalkenso.com.

The waitlist

• What we keep: your email address, what describes you if you chose it, where you came from (a link's ref, or the site that sent you), the date, and a scrambled form of your internet address. The scrambled address only stops the same visitor joining over and over; it can't be turned back into the address.
• Why: to write to you once when Chalkenso opens. You ask for that by joining, and you can change your mind at any time.
• How long: until Chalkenso has opened and you have had that email. Then the list is deleted, except for the people who go on to create an account.

Pilot and license requests, and emails

When you ask for a pilot or a license, we keep what you write in the form (your name, email, organisation, role, team size and message) to answer you and set things up. Emails you send us stay in our mailbox for the same reason. We delete them when the conversation is over, unless it led to an agreement: then we keep what the agreement and accounting rules require.

Using Chalkenso

• Accounts: your name, email, password (stored only in a form that can't be read back), profile picture if you add one, and two-factor settings if you turn them on. We need them to run the service for you and your organisation, and keep them while your account exists.
• Courses and everything your team writes belong to your organisation. We keep them while it uses Chalkenso and delete them when it leaves, or earlier when it asks.
• Learners read through a private link from their school or company, which adds their names to a group. Their feedback, notes and questions belong to that organisation: it decides what happens to them, and we handle them on its behalf. Learners with a question about their data should ask their organisation first; if you write to us, we pass it on.
• Learner answers: at the end of a lesson learners may answer one question ("Could you explain this lesson to someone else?", or a short check question), and at the middle or end of a course a short survey. Their organisation's instructors see these answers in aggregate, never one learner's answers by name; a learner can add their name to a written answer, and a quote is shown publicly only if they allowed it, and never with their name. The organisation can turn each of these off for a course or a group.
• Reading statistics: on learner pages we count, per section of a lesson, how long it was read, how far readers got, where they went back, and how often they copied code or asked an AI assistant. These counts carry no name, no learner link and no internet address, only the day: they describe the lesson, not the person. Learners can switch them off with "Don't count my reading" on the page, and browsers that send Global Privacy Control are never counted. We keep these counts for up to 25 months.
• AI: when your team uses an AI feature inside the app (revising a lesson, drafting a plan), the text that request needs is sent to Anthropic, which runs the Claude models, with your organisation's own API key (or ours, where we agreed to include AI). Its commercial terms don't let it train models on that text. We record each call's size and cost, not its text, so you can see what your key spends. When a learner sends a passage to an AI assistant, their own browser opens that assistant (ChatGPT, Claude and others); nothing goes through us.
• Your own Claude ("Use with Claude"): if someone on your team connects their Claude account, Claude can read what they can read in Chalkenso and send drafts back. What it reads is then handled by Anthropic under that person's own Claude account and its terms. It never receives learner names, private notes or reading data. We keep a log of what each connection did for 90 days, visible to the person and to your owners and admins; disconnecting ends a connection at once.

Cookies

Only the ones that keep you signed in to the app; visitors who don't sign in get none. Your browser also remembers whether you chose the light or the dark look. No advertising, no third-party analytics and no tracking across sites. The reading statistics on learner pages use no cookies and store nothing in the browser: each page visit sends its own anonymous counts, described above.

Who else handles the data

Companies that run parts of Chalkenso for us, each only for that part:

• Vercel: hosting the website and the app (its servers log visitors' internet addresses for security).
• A managed PostgreSQL provider: the database.
• Cloudflare: storing images used in courses.
• Anthropic: the AI features.
• Our email provider: the info@chalkenso.com mailbox.

Some of them are based in the United States. Those transfers are covered by the EU–US Data Privacy Framework or the European Commission's standard contractual clauses. We don't sell data, and we don't share it with anyone else unless the law requires it.

Your rights

You can ask to see what we keep about you, correct it, delete it, take a copy, or object to how we use it, and you can withdraw your consent to the waitlist at any time. Write to info@chalkenso.com; we answer within a month. If you think we got something wrong, you can also complain to a data protection authority, for example in the country where you live.