What SelfBadge is
Each person gets one page at selfbadge.com/<handle>. It holds only facts about the person as a professional: name, roles, employers, education, credentials, awards, languages, the accounts and websites that are really theirs, and their published work. Every fact is marked as self-declared or verified, and every page is also published in the formats machines read: schema.org JSON-LD in the page, a .json version with the verification level of each fact, a .md version for language models, a public lookup API and MCP server, sitemaps and llms.txt.
SelfBadge exists because AI assistants now answer "who is this person?" millions of times a day, and they often guess: they merge namesakes, repeat old roles or miss a person entirely. A verified, structured record gives them one source they can trust and quote.
Who runs it
SelfBadge is operated by Buzz Dealer (Cyprus) Ltd, Agias Filaxeos 122A, Limassol 3087, Cyprus. It was founded in 2026. You can reach us at [email protected] and follow SelfBadge on LinkedIn. The Privacy Policy and Terms of Service set out the rules in full.
How verification works
A fact is verified when the person proves it, not when they type it. Every fact carries one of five levels:
- Seeded (0): imported from an open public source such as Wikidata and not claimed by the person. Treat it as unconfirmed.
- Self-declared (1): added by the person and not independently checked.
- Account-verified (2): proven by signing in to the account (LinkedIn, Google, X, GitHub, ORCID, YouTube and others), a code sent to a work email, a DNS record, or a link back from the person's own website.
- Document-verified (3): a reviewed document or a credential confirmed with its issuer.
- ID-verified (4): an identity document check.
Website and work-email checks are repeated every six months; a check that no longer passes drops the fact back to self-declared. The verification level is shown next to each fact on the page and published in .json. It is not part of the JSON-LD, because schema.org has no clean property for it.
Where the data comes from
- The person: what they enter in the editor, import from their LinkedIn data export, or prove by connecting an account.
- Public sources: some profiles start from public Wikidata information about people who are publicly known for their work. They stay out of search engines until the person claims them. How profiles from public sources work.
- Companies: a company on the company plan can invite its team; each member accepts and owns their profile.
Editorial rules
- Only professional facts that schema.org can describe about a person. No phone numbers, home addresses (a city at most), family members or private documents.
- Nothing is presented as verified unless a check passed. Self-declared facts say so.
- Every visible fact is also in the structured data, and nothing in the structured data is hidden from people.
- Seeded, unclaimed and thin profiles send
noindexand stay out of sitemaps. - No paid placement. Paying for a plan never changes what is shown as verified.
- Anyone can report a profile for impersonation or wrong facts, or ask for an unclaimed profile about them to be removed; a removed profile is not recreated.