TruAnon Identity
You have profiles. This lets members bring their own confidence of identity to them, and choose how others see and share it. It amplifies a profile. When identity carries weight, members do more of whatever they came to do — and do it more safely. It is voluntary. Members use it because the platform
You have profiles. This lets members bring their own confidence of identity to them, and choose how others see and share it.
It amplifies a profile. When identity carries weight, members do more of whatever they came to do — and do it more safely.
It is voluntary. Members use it because the platform makes it worth using. What shows is theirs to set, and theirs to withdraw at any time, everywhere at once.
Confidence of identity is built from a public history that cannot be assembled on demand. Where it is visible, a fraudster gains nothing and carries more risk, and moves on to a less trusted platform. The community sorts itself, without rules or moderation.
It is automatic and continuous. Members keep it current by being who they are.
The site stores nothing that identifies anyone — a rank, a score, an image address. Everything else is read live when viewed and never written down.
Where badges appear
- Beside member names on comments and post bylines — classic and block themes
- On the member’s profile (the author page): badge, title, and granted details
- On UsersWP member profiles and in the members directory — no code
- Anywhere else via the [truanon] shortcode, the [truanon_card] profile card, or the Badge block
- [truanon_settings] places the member panel on any front-end page for membership sites
What it costs your server
Badges render from cached rank and score; no page waits on an API. Styling is self-contained — no Bootstrap, no icon fonts — and every color is a CSS custom property ( --truanon-* ) a theme can override.
Using it with a membership plugin
Community plugins render their own profile pages and member directories. WordPress core never fires its author or comment hooks there, so TruAnon reaches them either natively (UsersWP) or with a one-line snippet (everything else).
UsersWP — nothing to add. The badge places itself on member profiles and in the members directory (there as a compact rank-colored check, rendered from cache with no per-member API call). On their own profile the owner also sees a Verify / Manage bar that opens their identity panel (anchor + privacy switches). It is on as soon as you enter your key; the setting on the TruAnon admin screen turns the member control off if you’d rather place it yourself. If you ran an earlier version with a [truanon_verification] profile snippet, remove it after updating so the badge isn’t drawn twice.