History

Each document carries the date of its last change. This page says what changed, newest first. A change that is unfavourable to you, or that widens what we collect, is also announced by email to active accounts, as the terms and the privacy policy provide.

2 October 2026

• Privacy: a new section says in plain words where your data goes: everything the platform keeps — account, organisation, machine metadata, heartbeats, emails, logs — is stored and processed by Cloudflare, a United States company, with the database and the files in Eastern North America. This is a transfer outside Morocco and outside the European Union; it rests on your explicit consent, asked when you create your account, recorded with its date and the version of the text, and withdrawn by deleting the account. GitHub and Google receive something only when you sign in through them; Stripe receives nothing.
• Privacy, cookies and sub-processors: PostHog is gone. The site and the console count their visits with Cloudflare Web Analytics, which writes nothing to your browser and carries no identifier, so the consent banner, its pupitre_analytics value and the footer link that reopened it are gone too. Cloudflare is now the only sub-processor that receives personal data.
• Data processing: the members’ consent as the basis of the transfer to Cloudflare, alongside the standard contractual clauses.
• Security: PostHog leaves the list of third parties whose vulnerabilities are reported to them, Google joins it.

1 October 2026

• All documents: Pupitre is now published by React Consulting SARL AU, a company established in Morocco, represented by its manager Jordan Monier, which also pays for the hosting of the platform. It becomes the data controller and the processor in place of Jordan Monier as a natural person.
• Licence: rewritten. The source code is public under the Apache License 2.0 with the Commons Clause: you may use, modify and run it, including a platform of your own, but not sell Pupitre or a service built mainly on it. The ban on decompiling goes with the closed code.
• Terms of service: the free launch ends and is replaced by free servers: every organisation enrols up to a fixed number of machines for free, with no time limit, and needs a licence beyond them, granted on request, at no charge today. The launch seat kept for good, the trial and the prices are gone. The public source code and how its licence relates to these terms.
• Subscription terms become free servers and licences: no payment is taken; licences beyond the free servers are granted on request; refunds, renewal and withdrawal, which applied to payments, are gone.
• Privacy and cookies: the licence of your organisation in place of the subscription; no payment data and no payment provider today; an affiliate link is read when you create your account, and counts the machines enrolled by the organisations it brought, with no offer attached.
• Sub-processors: Stripe stays listed only for the day licences beyond the free servers would be sold; nothing is sent to it today.
• Data processing, third-party software and legal notice: the new publisher, and the app and the agent as source-available software.

25 September 2026

• Terms of service: the platform can no longer give access to a machine on its own. It relays your devices’ keys and the approvals they sign, and the agent adds a key only if it already trusts it or a device it trusts approved it; it never removes the last key. The heartbeat carries the fingerprints of the keys the agent trusts and of those waiting for an approval.
• Privacy: the key approvals your devices sign, and those fingerprints in what we receive from your machines.
• Data processing: key approvals and those fingerprints within the scope and the categories of data.
• Privacy, cookies, sub-processors and third-party software: the site and the console serve their fonts themselves, and your browser no longer contacts Google Fonts; JetBrains Mono joins the app’s third-party software.

24 September 2026

• New documents: the subscription terms, which will apply the day billing opens; the cookie policy; the list of sub-processors; the security policy and its security.txt file; the third-party software; the legal notice; and this history.
• Terms of service: encrypted backups to your own storage — what the platform receives about them, and what it never receives, neither the backup, nor its passphrase, nor the access key to your storage; the agent version, sent with each heartbeat as well; the capacity to contract; the pointers to the subscription terms and to the legal notice.
• Privacy: backup references; the basis of each processing; the answer to the audience measurement banner, the only value the measurement writes to your browser, and the link to change your mind; the fonts served by Google Fonts; the visit count of an affiliate link; the right to restrict a processing and to withdraw a consent; the CNDP and the rights of California residents.
• Data processing: backup references within the scope, the backups themselves outside it, and the details of the processing.
• Licence: what the law lets you do in spite of the ban on decompiling, and the pointer to the third-party software.
• Acceptable use: infringement of the rights of others and how to report it to us, vulnerability research under the security policy, and backups in what we can see.

20 September 2026

First publication of the five launch documents: terms of service, licence, acceptable use, privacy and data processing, published by Jordan Monier, a natural person residing in Morocco, with the free launch and the seat it gives for good.