Desktop settings and licensing

The panels only the desktop app has: activating and moving a licence, backing up and restoring data, migrating from the cloud, privacy, language, updates.

1. Desktop settings, at a glanceDesktop settings is the panel the desktop app has and the browser does not — License, AI, Privacy & diagnostics, Data backup and About. Four ways in, and how it differs from the Setting entry in the sidebar.
2. Activating a license, moving computers, and every error messageAfter paying you get a license key and activate it in Desktop settings. One key is bound to one computer at a time, and moving is self-service. What each status and each error means, and what to do about it.
3. Backups: exporting and restoring a .tdbkOne encrypted file holding every table, workspace, dashboard and setting — free, with no row limit. Exporting, restoring, the detection on launch, where the data folder is, and what happens when you uninstall or change machines.
4. Moving from the cloud edition to the desktop appDownload a .tdbk from the cloud edition, install the desktop app, and it detects and imports the file on launch. Tables, dashboards, formulas and relations all survive, and the data ends up on your own computer.
5. Privacy and diagnosticsOne switch — anonymous crash reports. On, crashes and internal errors are reported anonymously with no business data; off whenever you like, fully in effect at the next launch. Plus every other thing the desktop app touches the network for.
6. LanguageThe interface follows your system language — Chinese on a Chinese system, English everywhere else. Switch it by hand from the workspace-avatar drawer, and the menu bar, native dialogs and the language the AI answers in all follow.
7. About and updatesThe About tab shows the current version and when it last checked, and checks on demand. A new version is announced in the main window, downloads in the background and installs when you quit. Updating does not touch the data folder.
8. 30-day version history30-day version history is on the paid feature list but has no self-service interface yet. The engine does keep a write log and periodic snapshots, and recovery goes through support. Day to day, exporting a .tdbk regularly is still the protection that works.