Workspace and local data
A workspace is the project folder where Mystilink keeps local records and conversations. Your account manages licensing and online services such as Newton; it does not replace a workspace backup.
Two local locations
| Location | Main contents | Backup considerations |
|---|---|---|
.mystilink/ inside a project folder | Profile cards, conversations, logs, usage, and related working data | To keep history, preserve the whole folder rather than copying one conversation file |
.mystilink/ in your home directory | User settings, model configuration, and similar | May contain keys or other sensitive settings; treat it as private data |
~ means the home directory of the current system user; it is not the same location as the folder of the same name inside a project. settings.json holds interface preferences and similar user settings; you cannot restore all model configuration or workspace records from that file alone.
Why records disappear after switching directories
Different workspaces keep their data separate. When records suddenly vanish, first confirm that the project folder is the same as before, that the hidden directory is still there, and that the disk is readable and writable, before concluding the data was deleted. Signing in to the website account again generally does not download another computer's history.
Do not create a new profile card with the same name to test whether the original data came back; check the original record contents, past conversations, and timestamps instead.
How to keep a reliable backup
Finish or cancel running work and quit the app before copying the directory, so files are not changing during the copy. Keep the backup somewhere you control with restricted access, label it with a date or version, and verify afterwards that the files were actually copied.
Model keys, activation credentials, and private birth records can all appear in local files. A field shown as dots or masked text describes only how it is displayed, not that the backup file is free of sensitive data.
Migration and restore
Install the app on the new computer and activate it, copy the backup into the intended project directory, then open that workspace. Migrate or re-add user settings and model configuration as needed; never treat the old computer's activation state as licensing on the new one.
Save the existing contents of the target directory before restoring. Do not overwrite same-named files between two workspaces; if you are unsure which records belong to which backup, keep both directories intact first. Detailed steps are in Data backup and migration.
Local storage and cloud inference
Files being on your machine is a different question from the transport path of a model request. The profile cards, question, and context you reference may be sent to Newton, a third-party vendor, or your own service with the request. Choose your access path with Privacy and local data in mind.