Local data and secrets
Projects, models, settings and logs are stored locally. API keys and account tokens are separate from regular settings.
Main data groups
Data locations depend on the platform, installation method, and selected paths. Feedback and external coding tools may store data in their own directories. Include these locations when planning backups and cleanup.
| Data | Where are they located? | How to delete |
|---|---|---|
| Projects and attached materials | In the directory selected by the user when saving. | Manually after creating a backup. |
| Settings | In the current user’s Screph data directory. | By resetting the settings or deleting the corresponding files while the program is closed. |
| API Keys and Account Tokens | In the system credential store (Windows Credential Manager on Windows). | By disconnecting the account or removing the key from the connection profile, using the system credential store if needed. |
| Models and options | In selected or managed model and dependency catalogs. | From the corresponding settings section or manually after checking the path. |
| Logs and crash reports | In the Screph data directory. | From the diagnostics section or manually when the program is closed. |
| Temporary computer vision results | In the Screph data directory and, for attached results, next to the project. | Unattached results are cleared separately; attached ones are deleted along with the corresponding project materials. |
Projects and portability
The main project file can reference images, method results, and other files near it. To migrate, copy the entire project directory, not just the single JSON file.
After copying, open the project from its new location and check the source images, annotations and attached results.
Secrets
If the system credential store is unavailable, saving or reading a key may fail. Restore access to the store; do not move the key into a project or a regular settings file, or save it as plain text.
- Do not store keys and passwords in the project, file name, diagnostic note, or network stream URL.
- Please check attachments, logs, and service addresses before submitting a project or diagnostic archive.
- Disabling the LLM profile should be accompanied by deleting the unnecessary key from the system storage.
Backup
A settings backup does not automatically transfer keys from the system credential store, models from other directories, or external-service accounts. Check those connections and paths separately on the new computer.
- Close Screph or finish recording and saving the project.
- Copy the entire project directory.
- If necessary, save settings and local models separately.
- Test the copy on a different path before deleting the original data.
Full cleanup
Use “Tools → Data and privacy” to inspect supported groups of local data. Only some groups can be deleted there; others are listed for inspection and require their own removal tool. Check the file list and size before cleanup; there is no universal undo for deletion.
Uninstalling the program does not guarantee the removal of projects, models, settings, keys, logs, the FakerInput system driver, or Voice2Text data. These groups need to be checked separately. There is no single automatic cleanup deadline for all local data.