everything the policy office asks for.
Before a university can let students build on a tool, someone has to answer for it — the data-protection officer, the security reviewer, the sustainability lead. This is where MakeMode answers, plainly: where your data lives, how it's protected, whose software it really is, and what it costs the planet.
four questions, answered honestly.
We'd rather tell you what's true today and what's still in progress than polish a guarantee we can't yet sign. Each page is written for the person who has to sign off.
privacy & data residency
The institution is the controller, MakeMode the processor. What little data exists, how it flows, the EU-only model hop, sub-processors, and your GDPR rights.
security
Encryption in transit and at rest, least-privilege access, secrets management, incident response — and open source you can read instead of trust.
sovereignty & open models
What sovereignty really means, and the models we run: EU-provenance by default (Mistral, Devstral), open weights optional — all hosted on French soil. You choose.
environmental impact
France's low-carbon grid (~10× cleaner than the EU average), ADEME-audited per-model carbon, and CSRD-ready reporting — clean by the same accident that makes it sovereign.
what the checklist usually asks.
Need something specific for a procurement file or a DPIA? Email hello@makemode.eu — we'll send the detail.
honest about what's signed and what's in progress.
MakeMode is early-stage. The architecture is sovereign by design and running today, and that's most of the story. But the EU-only, no-retention, no-training commitments become fully contractual as each data-processing agreement is signed — so we describe them as our operating commitment and design intent, not as settled guarantees. We'd rather you trust the page because it's careful than because it's confident.
the one you're allowed to say yes to.
See it running, or get the detail your reviewers need.