Product

Sign-in and hats

ET verifies your MiniStudios session. It does not create or store accounts.

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

Sign-in in two steps Built

  • Step one: username and key, or continue with Google or a MiniStudios account. The account screens are handled on the MiniStudios side.
  • Step two: choose a hat, but only once the session verifies.
  • Remember-me keeps the verified session token on your computer.

Hats Built

  • Research explores. It cannot post offers.
  • Sell is for posting offers and reporting inaccuracies. Offers are empty and writes are documented as refused, so this is planned. Planned
  • Both combines the two.
  • A hat is a capability preference. It is not a second account or a role in a user table.
QuestionAnswer
What does ET call on the account host?One read-only session check (a GET with a bearer token). A valid session returns the account email; anything else returns no. A session lasts seven days.
What does ET never call?It does not create seats, create sessions or delete anything on the account host.
Does ET have its own user table?No. The account host is the only source of truth.
Does ET store a password?No.
Where does the token live?On your computer, in the shared account file or the process. Threat model and encryption at rest are not verified.
Has anyone audited this?No third-party review is known.

Status labels describe the project files as read on September 30, 2026. “Built” means the code exists and the build notes report tests passing; we have not run it end to end for this site, and no customer has been confirmed.

Reviewing the trust model?

The security pages list what ET verifies, what it stores and what it does not claim.

No public download yet. Ask to be told when access opens.Request access