The privacy page and the "What we keep" page said every account holds an email address and a password hash. On a server that uses the shared FlameNet account service, which relay.flamenet.io does ("accounts":"shared"), that is not true:
the account service table (enclaveSQL/010_accounts.sql) holds a handle, the client KDF salt and settings, a salted verifier derived on the phone, and an optional hashed recovery code. It has no email column;
the relay row is linked by a pseudonym, with the email column empty (AllowNullEmail) and no password hash;
both apps leave the email field out of signup on a shared-account server.
A server that keeps its own accounts still holds a username, an email address and a password hash, and the pages now say that too.
Changed: privacy.leaf (Account information) and metadata.leaf (the account-details list item and table row). English only; the Spanish pages follow after a native speaker checks the wording. The owner approved this wording on 2026-09-28 and okays the deploy separately.
"As this one does" is fixed copy, true for the default relay. Making it follow each server's own setting is a small template change for after the freeze.
The privacy page and the "What we keep" page said every account holds an email address and a password hash. On a server that uses the shared FlameNet account service, which relay.flamenet.io does (`"accounts":"shared"`), that is not true:
- the account service table (`enclave` `SQL/010_accounts.sql`) holds a handle, the client KDF salt and settings, a salted verifier derived on the phone, and an optional hashed recovery code. It has no email column;
- the relay row is linked by a pseudonym, with the email column empty (`AllowNullEmail`) and no password hash;
- both apps leave the email field out of signup on a shared-account server.
A server that keeps its own accounts still holds a username, an email address and a password hash, and the pages now say that too.
Changed: `privacy.leaf` (Account information) and `metadata.leaf` (the account-details list item and table row). English only; the Spanish pages follow after a native speaker checks the wording. The owner approved this wording on 2026-09-28 and okays the deploy separately.
"As this one does" is fixed copy, true for the default relay. Making it follow each server's own setting is a small template change for after the freeze.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The privacy page and the "What we keep" page said every account holds an email address and a password hash. On a server that uses the shared FlameNet account service, which relay.flamenet.io does (
"accounts":"shared"), that is not true:enclaveSQL/010_accounts.sql) holds a handle, the client KDF salt and settings, a salted verifier derived on the phone, and an optional hashed recovery code. It has no email column;AllowNullEmail) and no password hash;A server that keeps its own accounts still holds a username, an email address and a password hash, and the pages now say that too.
Changed:
privacy.leaf(Account information) andmetadata.leaf(the account-details list item and table row). English only; the Spanish pages follow after a native speaker checks the wording. The owner approved this wording on 2026-09-28 and okays the deploy separately."As this one does" is fixed copy, true for the default relay. Making it follow each server's own setting is a small template change for after the freeze.
🤖 Generated with Claude Code
mentioned in commit
ac95f3c355