Data export and emergencies
What is this about?
In short: you can export your projects and your account data and take them with you. The project backup can be imported again and encrypted with your own key. What applies if you lose access is described here, and for everything we cannot promise, we say so openly.
Protection goal
Your work should not be tied to Illumentis. You should be able to back it up, take it with you and restore it, even if something goes wrong.
How it works
- Project backup (JSON): It saves the data of your project, for example books, characters, locations, rules, calendars and notes. A media bundle as a ZIP contains images and audio. You can import it again later. When importing, you see a preview and decide conflicts yourself.
- Data access file (account): A file with your account data, for example profile, messages, support tickets and sessions. Project content is not included; you export that per project.
- Encryption with your key (optional): If you have stored a public GPG key, the backup is encrypted so that only your private key opens it. This option requires an active studio of the project owner.
- Manuscript export: There are separate exports for Word, PDF and e-book, whose scope depends on the permissions in the project.
Measures
- Backup, import and the data access file are free to use. Export should not become a paywall, so that you can take your work with you.
- A backup contains only what you may see as a person. A co-author limited to individual books backs up only those books.
- Every backup is visible to all co-authors in the export history, so that it stays traceable who made a backup.
- When importing, Illumentis checks the file before anything is written, and creates data only in your own project.
- The data access file contains only your own data and none of other people.
What applies if you lose access?
If you lose your password and second factor, the recovery key or an identity check by an admin helps. Your content is not opened in the process. More on this: Sign-in and two-factor authentication.
What we do not promise
- A backup is only as current as the moment you created it. We do not create it for you.
- If you lose the private key of an encrypted file, it is lost for good. Not even an admin can open it.
- When importing, the quantity limits of your plan apply, and references to elements that are not in the file are skipped with a warning.
- Automatic, regular backups of the server are planned for production and are not running in the beta yet. Your own export is the backup you can rely on.
How we check this
Backup, import, encryption and the data access file have automated tests, which the table below names. The statements on restoring access rely on our project documentation.
Evidence tests
| Test | What the test proves |
|---|---|
JsonBackupRoundtripTest |
A project backup can be imported again and gives the same data. |
JsonBackupAccessDataLeakageTest |
A backup contains no access data of other people. |
GpgExportEncryptionTest |
With a stored key, the backup is encrypted so that only the private key opens it. |
UserDataExportTest |
The data access file contains the account data of the person. |
UserDataExportLeakageTest |
The data access file contains no data of other people. |
ManuscriptExportAuthorizationTest |
Exporting a manuscript follows the permissions in the project. |
Change history
- : First version.