Trust
Security and Trust Center
We describe controls that exist in the code and list, separately and at more length, what nobody has documented or tested. We claim no certification, audit or compliance.
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
Design principles we build to
Principles, not certifications.
Verify, do not hold
ET checks a session with a read-only call. It does not create accounts and stores no password.
Local by default
Desk state stays on your computer. There is no ET server that stores user data.
Say the limits first
Every capability is labelled Live, Built, In progress, Planned, Open or No claim.
No invention
Names, prices and contacts are not invented. Empty stays empty.
Read from the project files on September 30, 2026. None of this is audited.
Controls that exist in code
| Control | Detail | Status |
|---|---|---|
| Verify-only authentication | One read-only session check with a bearer token. A valid session returns the account email; anything else is refused. A session lasts seven days. The app never creates seats or sessions and never deletes. | Built |
| No ET user table | The account host is the only source of truth. Hats are capability flags. | Built |
| No stored password | Sign-in uses Google or a MiniStudios account on the account host. | Built |
| Project locks hold no secrets | A lock is tagged with a verified email only if a token already exists. | Built |
| Research hat cannot post offers | A code-level gate. Sell-side writes need a verified session. | Built |
| Honesty locks | Build checks record that invented names, prices, contacts and GPS are zero and that the globe is not a legal survey. | Built |
| Collection rules | Public sources only, no invented contacts, no paid lists, blocked pages skipped. | Built |
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
What is not documented or done
This is the longer list, and it is the honest baseline. See the full not-claimed page.
- No certification, penetration test or independent audit is known.
- No code-signing certificate is documented for the installer.
- The token is kept on the user’s computer; the threat model and encryption at rest are not verified.
- The product had no automated build pipeline or formal change control, as of late August 2026. Tests run locally.
- No published privacy policy or terms have been approved.
- No vulnerability disclosure programme or bug bounty is offered.
Reporting a problem
There is no formal disclosure programme and no dedicated security mailbox. If you find a problem, write to [email protected]. That address is a placeholder until the owner confirms a mailbox, so the request-access page also lets you copy the text and send it from any account.
security.txt carries the same contact.
Running a security review?
Start with the not-claimed page, then the trust model.