Trust
Trust model: what is verified, stored and called
Who you trust when you use ET, for what, and where the gaps are.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
Where things live
| Thing | Where it lives | Who can read it | Status |
|---|---|---|---|
| Your account and password | The MiniStudios account host, or Google | The account provider, not ET | Built |
| Session token | On your computer, in the shared account file or the running process; remember-me keeps it locally | Anyone with access to your Windows profile; encryption at rest is not verified | Open |
| Desk state and project locks | On your computer, inside the application’s local data | Anyone with access to your Windows profile | Built |
| Graph, overlays, pictures | Inside the application | Anyone who has the application | Built |
| An ET user database | Does not exist | — | No claim |
Project files list these calls only. A network trace has not been independently performed.
Read from the project files on September 30, 2026. None of this is audited.
What you are trusting
- The account provider to keep your credentials.
- Your own Windows profile to protect the local token and desk state.
- The build you received, which is unsigned as far as documentation shows.
- Our own statements on this site, which come from project files and have not been independently audited.
Need detail for a questionnaire?
The help center holds 1,000 answered concerns.