QivunaDevelopers

Verification (the blue check)

A blue check tells people that Qivuna knows who runs a bot. It is earned, it is tied to the owner's verified identity, and it goes away when the bot changes hands.

What the check gives#

Requirements#

RequirementHard
The bot is published (out of development mode)yes
It has a descriptionyes
The owner uses an authenticator app or a 2-step passwordyes
Encrypted bots: an active keyyes
The bot is at least 30 days old
At least 500 people started it, or it belongs to a notable organisation
No content strike in the last 90 days
No open reports

You can submit a request only when every hard requirement is met; the others are weighed by the reviewer. QivBot shows the list with ✓ and ✗ for your bot.

Asking for it#

  1. In QivBot open the bot and tap Blue check (or send /verify).
  2. QivBot asks for a link to your privacy policy (https://, up to 300 characters) and a support contact (an e-mail address, an https:// link or an @handle, up to 190 characters). These are public information about your bot.
  3. The Qivuna team reviews the request and contacts you to verify your identity, outside the chat. Never send identity documents to QivBot or any bot: QivBot chats are not end-to-end encrypted, and the team will never ask you to.
  4. You get the decision in QivBot. While the request is pending you can withdraw it.

After a rejection you can ask again after 30 days. One request per bot can be pending at a time.

How identity is handled#

Details are in the Privacy Policy.

When the check is removed#