Crash reports and privacy
What Celas Studio records when it crashes, what the report contains, and exactly what you send when you choose to report it.
Celas Studio installs a crash handler before anything else starts, on Windows and on every POSIX platform. If the app crashes, that handler writes a small plain-text report to disk (never a memory dump) and gets out of the way; nothing is sent automatically at the moment of the crash.
What a report contains
| Field | What it is |
|---|---|
| App version, platform, OS version, CPU architecture | Identifies the build, not you |
| Reason and fault address | Which kind of crash it was and where in memory it happened |
| Stack trace | Up to 64 stack frames, symbolised where possible |
| Layer count, current frame, total frames | Rough shape of the project open at the time: no names, no content |
| Active tool | Which tool was selected when it crashed |
No file names, no file paths and no artwork are ever part of a crash report. There is no document content in it at all: only the counts above.
What happens next time you open the app
If a report is waiting, the next launch shows a dialog: "Celas Studio closed unexpectedly", with the same privacy summary shown above and two choices: Send Report or Not Now.
- Send Report uploads the report on a background thread and, once it succeeds, deletes the local file.
- Not Now leaves the report on disk and closes the dialog. Nothing is sent. The same dialog appears again the next time you launch, until a report is actually sent.
What leaves the machine
A sent report goes to celas.studio over HTTPS. Home directory paths inside the stack trace are scrubbed (anything after /Users/, /home/ or C:\Users\ is replaced with [user] before the request leaves your machine) and the stack trace is capped in length. An anonymous install id travels with the report so repeat crashes from the same install can be grouped; it is generated locally and is not a hardware fingerprint. If you happen to be signed in to your celas.studio account, the report is attributed to you, but signing in is never required to send one.
Where reports are kept
An unsent report sits as crash-report.txt in the app data folder, next to your other settings: see Where Celas Studio keeps its files. An anonymous client-id.txt sits beside it. If the crash happens too early for the app to know its normal folder, the report falls back to a file next to the executable on Windows, or to the system temp folder on macOS and Linux.