> ## Documentation Index
> Fetch the complete documentation index at: https://bkey.id/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# BKey Proof of Me for Zoom

> Add, use and remove the BKey Proof of Me app for Zoom. It shows whether a face scan was completed, for this meeting, on the phone of the BKey account you ask.

> [!NOTE]
>
> **Available after Zoom approves the app listing.** BKey Proof of Me is not in
> the Zoom App Marketplace yet. This page describes the panel as it works today.

BKey Proof of Me is a Zoom app for asking a participant in your meeting to
verify. The phone of the BKey account you ask shows a request for a quick
face scan in the BKey app. When the scan is completed, the panel shows
**Authenticated** next to the name you entered.

Each proof is bound to the meeting you are in. A proof made for a different
meeting is rejected here, even when its signature is valid, so a proof cannot
be forwarded from another call.

## What the badge tells you

An **Authenticated** badge means:

* Someone completed a live facial-biometric scan in the BKey app, on the phone
  registered to the BKey account you asked.
* That phone signed a proof for **this** Zoom meeting. Before showing the
  badge, the panel checked the signature, that the proof names this meeting,
  and that the proof is fresh.

The badge also shows the verification level that the proof states, for example
**Authenticated · SILVER**. If the proof states no level, the badge says
**tier not stated**. For the most recent verification, the panel also shows a
**What was actually proved** section: the BKey identifier that signed the
proof, the meeting it is bound to, the verification level and the device-check
status.

What the badge does **not** tell you:

* **That the person on your screen is the person who scanned.** The scan
  happens on their phone, not in the Zoom video. The badge does not compare the
  face in the video with the face that was scanned, and it does not analyse the
  video for deepfakes. Use it together with what you see and hear.
* **Their legal name or identity documents.** BKey does not check an ID
  document for this badge. It proves control of a BKey account, not a legal
  identity.
* **Their Zoom display name.** The name shown in the panel is not part of the
  proof. Only the BKey account is.
* **That it is still them later.** The badge records one check at one point
  in time. It does not expire or change, and the panel never re-runs a check
  by itself. If you need a current proof, add the person again and ask them
  to verify.
* **That what they ask of you is legitimate.** A verified person can still ask
  for something you should confirm through your usual channels.

## Before you start

You need:

* The **Zoom desktop app** for Windows or macOS. Zoom does not let you add
  apps from the Zoom mobile app.
* **Zoom Apps turned on** for your Zoom account. On a company account, an admin
  may have to turn on Zoom Apps, or approve BKey Proof of Me, before you can
  add it.

You do not need the BKey app to ask someone to verify.

The person you ask needs:

* The **BKey app on their iPhone**, signed in, with their face set up in BKey.
* To tell you their **BKey identifier**. You send the request to it. It starts
  with `did:bkey:` and is shown as **ID** at the bottom of the **Settings**
  screen in the BKey app. Tapping it copies it together with the app version,
  so they should send you only the part that starts with `did:bkey:`.

They do not need to add the Zoom app.

BKey does not accept a request addressed by email address yet. The panel
offers **Use email instead**, but a request sent that way ends in **Couldn't
verify**.

## Add the app

1. Sign in to the [Zoom App Marketplace](https://marketplace.zoom.us/) with
   your Zoom account.
2. Search for **BKey Proof of Me** and open its listing.
3. Click **Add**.
4. Review the permissions Zoom shows you, and authorize the app.

If you see **Request** instead of **Add**, your Zoom account's owner or admin
has to approve the app first. Click **Request** to send them a request.

You can also add the app from the **Marketplace** tab of the Zoom desktop app,
or during a meeting from **Apps** in the meeting controls.

Having trouble? See [Troubleshooting](#troubleshooting).

## Open it in a meeting

1. Start or join a meeting in the Zoom desktop app.
2. In the meeting controls, click **Apps**. If you do not see it, look under
   **More**.
3. Click **My Apps**, then **BKey Proof of Me**. It opens in the side panel.

The panel reads the meeting's ID from Zoom and binds your requests to it. If
Zoom cannot tell the panel which meeting it is in, the panel blocks
verification rather than guess.

## Ask someone to verify

1. In the panel, enter the participant's name and their BKey identifier, then
   click **Add**. The name is a label for you: it stays in your panel and is
   not sent to BKey.
2. On their row, click **Ask to verify**.
3. Tell them in the meeting that you have just sent the request. The BKey app
   on their phone says that a verification partner is asking, and shows a
   technical ID for the requesting app, an internal ID for the meeting, and
   **Presence only** under what is shared. It does not show which participant
   asked, so telling them yourself is how they know the request is yours.
4. They tap **Begin verification** and complete the face scan. They have under
   a minute to do this before the request lapses on their phone.
5. The row shows **Authenticated** a few seconds after the scan.

### What each state means

| State | What it means | What to do |
| - | - | - |
| **Not verified yet** | You have added this person and have not asked them yet. | Click **Ask to verify**. |
| **Requested** | The request was sent and the panel is waiting for a result. You cannot ask again while a row is in this state. | Ask them to open the BKey app and answer within a minute. If no result arrives, the row changes to **Couldn't verify** after about ten minutes. |
| **Authenticated**, with the verification level | Someone completed the face scan on the phone of the BKey account you asked, and the proof checked out for this meeting. The row shows a check mark instead of a button. | Nothing. To ask again later, add the person again. |
| **Couldn't verify** | No result arrived within about ten minutes (the request was declined, not answered in time, or could not be delivered); a proof came back but failed a check (for example, it was made for a different meeting); the request was addressed to an email address; the panel could not reach BKey; or too many requests were sent. Hold the pointer over the badge to see the reason, when there is one. | Check the BKey identifier. If it is wrong or is an email address, add the person again with their BKey identifier, because **Retry** sends the request to the same one. Otherwise, tell them you are asking again, and click **Retry**. If requests to this person keep failing, see [Troubleshooting](#troubleshooting) before you retry. |

These requests all look the same in the panel: one that is declined, one that
is not answered in time, and one sent to an identifier that has no BKey
account. Each stays at **Requested** and then changes to **Couldn't verify**.
The panel does not tell you why a request got no answer.

### For the person being asked

The request appears in the BKey app as coming from a verification partner, with
an ID for the meeting and **Presence only** under what is shared. It does not
say which participant sent it. Verify only when the person you are talking to
has just asked you to, in this meeting.

**Begin verification** starts a short face scan. **Not now** declines, and no
proof is shared.

Despite the **Presence only** label, a proof you share identifies your BKey
account to the person and the app that asked: it is signed under a permanent
identifier for your account, which is the same in every proof you make. It
contains no image of your face and no liveness or face-match scores. It does
say which kind of biometric check was used, when the scan happened, and a value
that identifies your current BKey enrollment. See
[How your data is handled](#how-your-data-is-handled).

## Remove the app

1. Sign in to the [Zoom App Marketplace](https://marketplace.zoom.us/).
2. In the bottom-left corner, click **My Library**.
3. Find **BKey Proof of Me**.
4. In the **Actions** column, click the **More** icon, then click **Remove**.
5. Optionally choose a reason, then click **Remove** to confirm.

In the Zoom desktop app, the same steps start from the **Marketplace** tab
(under **More** if you do not see it).

If your Marketplace shows **Manage** in the top-right corner instead, click
**Manage**, then **Added Apps**, find BKey Proof of Me, and click **Remove**.

If a Zoom admin added the app for your whole account, ask the admin to remove
it.

Zoom's own instructions:
[Adding and removing Marketplace Apps for personal use](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0062865).

### What removing the app does

* It deauthorizes the app for your Zoom account. Zoom revokes the access you
  granted when you added the app. BKey is not notified of the removal.
* The panel no longer opens in your meetings, and you cannot ask anyone to
  verify through it.
* Nothing changes for the people you asked. Their BKey accounts and the BKey
  app are not affected.
* Verifications that were already completed are not undone or deleted. See
  [How your data is handled](#how-your-data-is-handled).
* You can add the app again at any time.

## How your data is handled

The app asks Zoom for the meeting's unique ID, to bind each proof to this
meeting, and for the meeting's topic, to show which meeting the panel is in. It
does not ask Zoom for your meeting's audio, video, chat or participant list.

The name you type for each person stays in your panel and is not sent to BKey.
The BKey identifier you type is sent to BKey with the request. An email
address entered with **Use email instead** is also sent to BKey, which
rejects it. The list of
people and their results is kept only while the panel is open. To limit
repeated requests, the app's server holds your IP address and the identifiers
you ask, in memory.

The face scan runs in the BKey app on the other person's phone. The proof your
panel receives contains no image of their face and no liveness or face-match
scores. It does say which kind of biometric check was used, when the scan
happened, and a value that identifies their current BKey enrollment.

The proof does identify the BKey account that answered. It is signed under a
permanent identifier for that account, which is the same in every proof the
account makes. So a proof is more than a presence signal: two proofs from the
same account can be linked to each other, including proofs given to different
requesters.

When you ask someone to verify, BKey records the request and its result: the
BKey account that was asked, the meeting the proof is bound to, the time, and
the signed proof. BKey keeps the same kind of record for other approvals made
in the BKey app.

Removing the Zoom app does not delete the records of verifications that were
already completed, because each one is an approval the other person signed on
their own phone. The
[privacy policy](https://bkey.id/privacy#meeting-attestation) explains what
BKey keeps for these checks and how to exercise your data rights.

## Troubleshooting

**I don't see Apps in the meeting controls.** Look under **More**. If it is
not there, Zoom Apps may be turned off for your account. Ask your Zoom admin to
turn them on.

**The app won't open in a meeting.** The meeting host can suspend Zoom Apps
for the whole meeting from Zoom's in-meeting security controls. Ask the host
whether apps are allowed in this meeting.

**I see Request instead of Add.** Your Zoom account's owner or admin has to
approve the app. Click **Request** and wait for their approval.

**I can't add the app on my phone.** Zoom does not let you add apps from the
Zoom mobile app. Add it from the Marketplace website or the Zoom desktop app.

**The panel says verification is blocked.** The panel verifies only when Zoom
tells it which meeting it is in. Close the panel and open it again from
**Apps** inside the meeting.

**The badge stays on Requested.** The panel waits about ten minutes for a
result, and you cannot ask again until then. Check that you entered their BKey
identifier, and ask them to open the BKey app: they have under a minute to
answer. If the time runs out, the badge changes to **Couldn't verify**, and you
can click **Retry**.

**Requests to one person keep ending in Couldn't verify.** Check that you
entered their BKey identifier and not an email address: BKey does not accept
requests addressed by email yet. **Retry** sends the request to the same
identifier or address again, so if that was wrong, add the person again with
their BKey identifier. The panel also limits how many requests you can send,
and how many one person can receive, in a ten-minute window, and BKey limits
how many requests the app can send in total (60 a minute across all users of
the app). When the panel's limit is
reached, **Couldn't verify** appears straight away, and holding the pointer
over it shows the reason. Each **Retry** counts as a new request. Wait ten
minutes before asking that person again.

**A proof keeps failing its checks.** If **Couldn't verify** comes back after
the person has completed the face scan, and **Retry** gives the same result,
[contact support](#contact-support) and include the approximate time of the
request.

## Contact support

Email [support@bkey.id](mailto:support@bkey.id) or visit
[bkey.id/support](https://bkey.id/support).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.