everything you make here, you can take.
A term's work on MakeMode is a set of projects, conversations, documents and boards. This page says exactly what you can download, in which formats, and how to erase all of it. It is written to be read in five minutes by the person whose work it is, and to survive being forwarded to a procurement office.
the test this had to pass.
Sovereignty is easy to claim and hard to leave. A tool that keeps your data in Europe while making it awkward to retrieve has moved the problem, not solved it. So we wrote the test down, and built until it passed.
A person who has used every part of MakeMode can get one archive of everything they made, in formats that open in software we do not control, and can read this page before they sign up. Every claim below is something you can check yourself today.
This is a shipping condition in our own engineering handbook, not an aspiration. A new part of MakeMode is unfinished until the work it holds can leave it. Where a piece of that promise is still being built, this page names it.
the workspace archive.
Sign in at account.makemode.eu and choose Download my workspace. You get a single .zip. Here is what is inside it.
your projects, as folders
Each project is a real source tree with an index.html you can open by double-clicking. Drag the folder onto any static host and it runs. This is the same folder the Export button in the app produces, assembled by the same code.
the conversation that made it
PROMPTS.md holds the brief in your own words. It is the closest thing to a specification your project has, and it is what lets you or a colleague pick the work up months later.
the work order
AGENTS.md lists what the build declared it could not do and what would finish it. Open the folder in a coding assistant and that file is the first thing it reads.
your rooms
Every chat conversation you were part of, as Markdown, including the build cards with the live links to what those conversations produced.
your pages
Every document you made at pages.makemode.eu, each as the single HTML file it already was, pictures inside it. Documents other people shared with you stay theirs, and the README says so.
your boards
Each board twice: as Markdown in reading order, and as JSON that imports back into an empty board and reproduces it. Boards you own — the shared board belongs to everyone who works on it, so it stays out.
account.json
The structured record: profile, full message history, saved versions, research reports, sign-in methods, payments and usage. This is the GDPR Article 15 and 20 answer, and it is machine-readable.
a README that tells the truth
The archive explains its own contents, names anything a size limit left out, and says which parts of your workspace are not in it yet. It does the same job this page does, from inside the file.
take one piece at a time.
You talk an idea through in chat, spread it out on a board, write it up in docs, lay a document out in pages, and build it in the app. Each of those has a Download in its own header, so you can take one thing without taking everything.
the app
A project as a .zip folder: source, README, work order, conversation. makemode open writes the identical folder straight into a terminal. Word and CSV exports where the content is a document or a table.
docs
A document as Markdown, as a Word-openable file, or as one self-contained HTML page that keeps the colours showing who wrote which words. That last one opens offline, with the authorship intact.
the board
A board as Markdown in reading order, with each prompt card carrying both the instruction and the result. Or as JSON, which imports back into an empty board and reproduces it exactly.
chat
A room as Markdown or JSON. Attachments are linked rather than embedded, and the file says so in its own header, so what you are holding is always clear.
pages
A document as the HTML file it already is, pictures inlined. There is no conversion step, because the thing you were editing was a web page the whole time.
One part of the archive is still being built: a document in docs is downloadable one at a time, and is not yet folded into the single workspace zip. The reason is worth stating plainly. Docs is shared by design, and until it records whose work is whose, an automatic archive would either miss your material or hand you a colleague's. We would rather ship the honest gap and close it properly. Pages and boards each joined the zip the moment they could answer that question; docs will the same way.
the formats, and why these.
An export is only portable if the thing that opens it is ordinary. Every format here is either a plain text file or an open standard with decades of readers.
Markdown opens in any editor and renders anywhere. The HTML is self-contained and needs no network. The Word file opens in Word, Pages and LibreOffice. The zip is an ordinary archive, uncompressed and readable by the tool already on your computer.
Structured JSON for the account record, the boards and the rooms. Project folders are real files at real paths, so a build tool, a static host or another AI assistant can pick them up with no adapter and no knowledge of MakeMode.
There is one thing here that is ours alone, and it is worth understanding: a MakeMode export carries how the work was made, alongside the work. The prompts that produced a build, the gaps that build declared about itself, and in a document the record of which sentences a person wrote and which the model did. Portability of bytes is the floor. Portability of provenance is what makes a downloaded artifact something you, a colleague, or another assistant can genuinely continue.
how to make it stop existing.
Data you can take is worth something only if you can also make it go away. On the same account page as the download, Delete my account erases your projects, conversations, memory, interview profile and API keys, and signs you out. It is immediate and it cannot be undone, so it asks you to type DELETE first.
what goes
Projects, messages, saved versions, research reports, your memory and interview profile, API keys, sign-in methods and sessions. Gone from the database in one transaction, so a partial failure cannot leave your identity stranded.
what stays, and why
Billing and usage records are kept in de-identified form, because accounting law requires the transaction record. Once your account is gone the remaining rows no longer resolve to a person.
published pages
Anything you chose to publish has a public web address. Unpublish it from the app before deleting your account, or write to us and we will remove it.
Take the archive first. Deletion is immediate, and we keep no copy for you afterwards.
how this maps to the gdpr.
MakeMode is the processor; the institution is the controller. Data-subject requests come to the institution, and these mechanisms are how they are answered without a support ticket.
article 15 · access
account.json in the archive, and the JSON download on its own, contain every category of personal data held: profile, prompts and replies, versions, sign-in method metadata, payments and usage. Available to the data subject directly, at any hour.
article 20 · portability
Structured, commonly used, machine-readable, and transmissible without hindrance. Project folders are the same artifact the person could have authored by hand, so there is no re-keying and no vendor adapter in the way.
article 17 · erasure
Self-service, immediate, in one database transaction, with per-table counts written to an audit trail. Financial records retained in de-identified form under the usual accounting-law exception.
All of it runs on Scaleway in France, so a single GDPR data-processing agreement covers the whole path. Depth in privacy & data residency, security, and sovereignty & models. For the DPA and a completed vendor-assessment pack, write to hello@makemode.eu.