Reversibility
If it stops
It is the careful manager's question, and almost nobody answers it before the signature. There are two ways this stops: you leave, or we stop. Both deserve an answer in writing.
What you take with you, in four numbers
- 10 sets of data — everything the school has entered
- 4 open formats, which open without us
- 0 € extra to pay, and no permission to ask for
- 1 restore of the backup checked every morning
If you leave
You take back all of your data from your settings, without telling us, without asking permission, with no delay and no extra charge. The download is reserved to the manager, and every export is logged with its date, its author and the number of rows it took out.
What comes out
Ten sets, meaning everything the school has entered: learners, contracts, invoices, quotes, payments, schedule and lessons, vehicles, instructors, packages, expenses. The technical authentication columns stay behind: they are no use to you and they should not be lying around anywhere.
In which formats
A ZIP archive, one CSV per data set
One table per set, separated by semicolons, with accented characters that display properly when you open it. A manifest comes with the archive and lists what it holds.
An Excel workbook, one tab per data set
The same content, ready to open in a spreadsheet, with no conversion and no import settings to work out.
The full detail in JSON
A single file, readable by any spreadsheet and by a human being: it is the one that keeps the links between a learner, their contract, their payments and their lessons.
A learner's whole file, as one PDF
Everything about them in a single document — for the learner moving elsewhere, for a parent raising a dispute, for someone asking for their data.
These formats are open: they open without us, today and in ten years. That is the only useful definition of reversibility.
If the support stops
Access does not close and nothing is erased. It stops accepting changes and carries on letting itself be read : the schedule, the records, the invoices, everything stays there to consult. An export is a read — so it carries on working, including when nothing is being paid any more.
That is deliberate. Cutting off access to your own files the day the assignment stops would turn a disagreement into a business problem. It will not happen here.
The rule holds to the end: when the assignment finishes, the account turns read-only, and the way to the export stays explicitly open.
If we stop
The honest answer is not a promise to last forever: nobody can keep that one, and a one-person business least of all. The answer is the export you already hold, in formats nobody controls.
The contract goes further: when the service ends, your data is returned or deleted, whichever you choose, in a structured and commonly used format. The deletion can be certified in writing, on request.
Until then, a backup of the database is taken every night, and an automatic check reloads it every morning into a throwaway database to make sure it really does restore. A backup that has never been restored is not a backup; it is a file you are hoping something of.
What does not exist yet
Better to read it here than to find out later.
Reloading an export into another installation
The mechanism is written and checked internally, it is not yet opened up on screen. As long as it is not, we do not promise it.
Fetching your data from another provider
Claiming your export is down to you: it is your right, and it cannot be delegated. If your current tool cannot produce one, write to me and we will look at it together.
Coming in costs something too
The journey the other way is described just as plainly: what you hand over, what is picked up on its own, and how much of your time it takes.