Privacy and security
Local writing, privacy, and backups you understand
Learn what stays on the computer, when a network may be used, and how history, exports, and backups serve different risks.
Inkthar · Published · Updated · 7 min read
Local-first does not mean no network at all
Inkthar books stay on the device, without an Inkthar remote server synchronizing projects. Core writing uses that local copy. Activation, updates, online research, and AI services may need a connection depending on the action.
AI is optional: content reaches a provider only after you configure it and run an assisted function. Review settings and provider policy before using sensitive material.
Separate versions, exports, and backups
Versions return to an editorial state. Exports create files for reading or exchange. Backups protect the data set from loss or failure. None replaces the others.
In Settings, choose Backup destination and enable Automatic backups. The app creates at most one verified backup per day while idle; check Last safe backup and Last backup attempt, or use Create backup now.
- Working copy on the computer
- Backup on another device or location
- Identifiable export in a common format
- Periodic restoration test
Build a routine proportional to risk
After an important session, wait for saving and confirm that a recent safe backup exists. Before restoring data, updating the system, or changing the book substantially, use Create backup now and verify the result.
Protect the environment too: update the operating system, use a password, and enable disk encryption when available. Local control works best with a verifiable backup routine.