Privacy: what you can see
Players choose how much of each linked account third parties can see. The setting is per account, on their account page:
| Visibility | What you see in lookups |
|---|---|
| Public (default) | the account's identifier |
| Hint | only that an account on that platform is linked: {"hint": true} |
| Hidden | nothing; the platform is left out |
A player's Minecraft account can be Public or Hint, but never Hidden, because it's how servers recognise players.
The rules that follow from this:
- Looking up by an account requires that account to be visible. A lookup by a Hint or Hidden account answers
404, exactly like an unlinked one, so a known Discord ID can't be used to reveal a player's other accounts. The exception is Minecraft: looking up by Minecraft UUID always works, because servers already know their players' UUIDs. The UUID itself is still shown only as a hint if the player chose Hint. - Membership checks work for Public and Hint accounts. They also work for Hidden accounts by default, unless the
player turned off "Still let communities I belong to check…" for that account, in which case they answer
404(as if not linked). - Grants override visibility. When a player approves your application in an access request, your application sees the approved accounts in full, and can run membership checks with them, whatever their visibility, until the player revokes access. Revoking takes effect immediately, and unlinking an account removes it from every grant. A one-off check hands over the token only and grants nothing.
| Account visibility | Anonymous / server token | Application with a grant for the platform |
|---|---|---|
| Public | identifier | identifier |
| Hint | {"hint": true}, can't be looked up by |
identifier, can be looked up by |
| Hidden | left out, can't be looked up by, checks allowed unless the player turned them off | identifier, can be looked up by, checks allowed |
Design for missing data: a platform missing from a lookup may be unlinked, hidden, or excluded by include.