Sign-in, accounts and security
Signing in
How the two-step login works.
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
C0477 How do I sign in?
In two steps: enter a username and key, or continue with Google or a MiniStudios account; then choose a hat. Account screens are served by the MiniStudios side.
C0478 Does ET store my password?
No. Sign-in creates or uses MiniStudios accounts on their host, and ET holds no password.
C0479 What does ET send to check my session?
One read-only request with a bearer token. A valid session returns the account email; any other answer means no.
C0480 What does ET never call?
It does not create seats, create sessions or delete anything on the account host. Its only use is the read-only check.
C0481 What is remember-me?
A setting that stores the verified session token locally so you are not asked again. The token stays on your computer.
C0482 Where is the token stored?
In the shared MiniStudios account file under your Windows profile, or carried in the running process. Encryption at rest of that file is not verified.
C0483 Is the token encrypted at rest?
We do not know. The project does not document a threat model or encryption-at-rest for it, so make no assumption beyond your Windows account protections.
C0484 Can ET create an account for me?
No. You create one on the account side, through Google or a MiniStudios account. ET never creates users.
C0485 Does ET have a user table?
No. The account host is the only source of truth, and hats are capability flags, not database rows.
C0486 Why are hats chosen after sign-in?
So a hat is only ever applied to a verified session. You cannot pick Sell before the session is proven.
C0487 Can I change my hat later?
Hats are capability preferences. We have not documented the change flow, so check your build.
C0488 What happens if my session expires?
The session check fails and you are asked to sign in again. We have not described exact behaviour beyond that.
C0489 Does sign-in support two-factor authentication?
That is handled, if at all, by the account provider, such as Google. ET does not implement its own second factor, and we claim none.
C0490 Can my organisation use single sign-on?
No SSO is documented. Sign-in uses Google or a MiniStudios account, so we do not claim enterprise identity integrations.
C0491 What if I forget my key?
Key recovery would be on the account side, not in ET. ET has no password reset of its own.
C0492 Can two people share one sign-in?
The account host governs accounts. Sharing credentials is a matter for your agreement with that host, and ET does not check for it.