Last updated
Verified privacy policy
Verified is run by Bhanu Kowshik Papineni ("Verified", "we"). You can reach us at [email protected]. This policy explains what Verified collects, why, who sees it, and how long we keep it. It covers the Verified Chrome extension for interviewers, the Verified app for Mac and Windows, the check pages candidates open, the Verified server, and this website.
1. The short version
- An interviewer turns on a Verified check for a Google Meet call. Each invited guest runs a short check in the Verified app on their own computer, in front of their own camera, and the app keeps checking during the call.
- The interviewer sees the results inside Google Meet. A result is information. It is not a decision about a person.
- We do not record calls. We do not store video or audio from a check or a call. Face samples are compared in memory and dropped.
- Stills are shown to the interviewer when a check finds a problem with a guest's camera or face during the call: the latest pair of small stills side by side, one from the guest's own camera and one of their video in the call, refreshed about every 30 seconds while the problem lasts. When the problem ends, the last pair of that problem stays in the interviewer's panel under "Earlier in this call". They are held in memory only and deleted when the call ends, or after 2 hours at the latest.
- We do not sell data, show ads or build advertising profiles. We use your data only to run the check.
- We keep check data for 7 days after the interview's last activity, then delete it. This includes the numbers about the candidate's voice and mouth movement from the check and the call (never sound, never pictures), which are deleted after about 7 days.
- You can ask us to delete your data or send you a copy (section 8).
2. Who uses Verified, and what each person sees
- Interviewers install the Verified Chrome extension. They turn on a check in Google Calendar and see the results in Google Meet and in the extension's toolbar menu.
- Candidates (anyone an interviewer invites) get a personal check link, by email from Verified or from the interviewer. Verified's invite emails come from [email protected]: an address on a sending domain that belongs to an earlier project of Verified's founder, used to send on behalf of Verified. They open it, read a consent screen, and run the check in the Verified app. A candidate can decline and still join the meeting. Nobody is kept out of the call. The interviewer sees that the check was not done.
- The interviewer who set up an interview, and their team, can see that interview's results. We do not show results to anyone else.
3. What we collect, and why
From interviewers (the Chrome extension)
| What | When | Why |
|---|---|---|
| The access code we give your company | You paste it into the extension once | So the server accepts checks from your team only |
| Your name and email, as shown on the Google Calendar event | When you save a Google Meet event with "Verify attendees" on. For a new Google Meet event the switch starts on; you can turn it off for the event or for any guest | To show candidates who asked for the check, and to link the call to your team |
| The event's title, start and end time, time zone and Google Meet link, and your Google Workspace name when Calendar shows one and you are the organiser | Same | To set up the check, link the call to it, and show guests which company invited them |
| The names and email addresses of the guests you leave switched on | Same | To make each guest's check link (and email it to them, when email is on), and to show their results next to their name |
| Frame-timing numbers about each invited guest's video tile in Meet: how many frames arrived and whether the picture changed. These are numbers, not pictures | During the call, only for calls you set up with the extension | To tell whether the guest's video is moving the way their own camera would show it |
| Short samples of each invited guest's video tile in Meet, as your browser receives it: a burst of 30 pictures every few seconds | During the call, only for calls you set up, while that guest's check is running | For the face match: to compare the face in the call with the face their own camera sees. They are used in the server's memory and then dropped. They are never saved |
| When an invited guest leaves the call or comes back, and when your own call ends, with the Google account address Meet shows for you | During the call, only for calls you set up | So a guest's checks stop when they leave or the call ends, and so only your own account can report the end of your call |
| The Meet code, title and your address of a deleted event | When you delete an event in Google Calendar that you set up with the extension | To cancel that Verified call |
| A reduced diagnostic log | While the extension runs | To help find problems. See below |
During a call, while the panel shows an amber finding about a guest's camera or face, it shows the latest pair of stills side by side, refreshed about every 30 seconds while the finding stays on. When a finding ends, the last pair of that finding stays in the panel under "Earlier in this call". "In the call" is drawn in your own browser from the guest's video tile and never leaves your browser. "Their camera" comes from the guest's Verified app through our server. Only the latest pair of each finding is kept, shown only to you, and held in memory only. Our server deletes its copy when the call ends, when the guest leaves, or after 2 hours at the latest.
The extension runs only on Google Calendar and Google Meet. It does not read your email, your chat, your files, your passwords, your cookies or any other website, and it has no access to your Google account.
The extension talks to our server about a Google Meet call only if you set that call up with the extension (or opened it with a host link we gave you). For every other call you open, nothing about that call is sent to us. The extension does send short diagnostic lines (a time and a fixed message, with no names, codes or addresses) while it runs, also before an access code is saved (see the reduced log below).
On your computer the extension keeps, in this Chrome profile only: your access code; the key for each call you set up; your last 20 calls with their guests' check links, so you can copy a link again; your on or off choice for each guest's email address in the Calendar switches (the newest 500); the Google account address Meet shows, only while an access code is saved; a short list of deleted events still waiting to be cancelled (30 minutes at most); a 12-hour record of which in-call notices were already shown, as salted hashes with no names; and a log of the last 300 lines of what the extension did. That log can contain event titles, guests' names and email addresses and page addresses. It stays on your computer. The Diagnostics section under Help in the extension's menu has a Clear button, and "Copy log" copies it only when you click it. A reduced copy of the log goes to our server: times, fixed messages, numbers and short status words only, with no names, email addresses, titles, page addresses or error texts. None of this is synced to your Google account. Removing your access code removes the code and the saved account address only; clicking Clear removes the log only. The call keys, your last 20 calls and the guest switch choices stay until you remove the extension (section 6).
From candidates (the Verified app and check page)
Before anything is collected, the candidate sees a consent screen that says what happens, and can decline.
| What | Where it happens | What we keep |
|---|---|---|
| Your name and email address | The interviewer added them to the Calendar event | Kept with the interview, so the interviewer can see your results |
| A short check before the call, in front of your own camera: a screen light test, reading a few sentences aloud, and a step with your hands and head | In the Verified app, on your computer. Your face and hands are tracked on your computer | Only the outcome of each step (passed or not, how many tries) and a few measured numbers |
| What you read aloud, as speech turned into text | The reading step. The audio goes from your computer to Deepgram, our speech-to-text service, which we ask not to keep it | The text we compare with the sentences. No recording |
| The short video of you reading the sentences | Recorded and checked on your computer by the Verified app, then deleted there, usually within a minute | Nothing. It is never sent to us or anyone else. Only the result is sent |
| Which camera your video comes from: a physical camera or camera software, other cameras connected, other apps using your camera, and the camera name your computer reports when it looks like camera software | The app asks your operating system for the list of cameras and which apps use them. It does not open another camera for this | The answer and, when it looks like camera software or another app is using your camera, that name |
| Face measurements from your own camera: numbers made from your face, every few seconds, before and during the call | In the Verified app, on your computer, from your own camera | The numbers are sent to our server, held in memory to compare with the face in the call, and dropped. We keep the result of each comparison (a score and a status) for 7 days, and the mouth-openness numbers described two rows below for about 7 days |
| Small stills from your own camera, when a check finds a problem with your camera or face during the call | Taken by the Verified app while the problem lasts, about one every 30 seconds, each small (320 pixels wide at most) | Only the latest one of each problem is kept (the last one stays available to your interviewer under "Earlier in this call" after the problem ends), in our server's memory only, and shown only to your interviewer. Deleted when the call ends, when you leave, or after 2 hours at the latest. Never written to disk. A short signed record of each still (its time, size and fingerprint, no picture) is kept with your check records |
| Numbers about your voice and mouth, during the check steps and during the call: how likely it is that someone is speaking, how loud, and how open your mouth is (from your camera's face measurements), with their times and the step's name | In the Verified app, on your computer. For these numbers, no sound and no pictures are saved or sent | These numbers, for about 7 days, then deleted. No audio, no images, no names. They are not shown to the interviewer. We delete them sooner with your other data if you ask |
| Hidden helper windows: whether any window on your screen is hidden from screen sharing. It names an app only if it is on our list of known AI interview helper apps | In the Verified app. This check is advisory and is tested on Windows. On a Mac it asks for the Screen Recording permission, and without it the result says "Can't confirm". Nothing records your screen: the app only reads which windows exist and whether they are hidden from capture | Whether a hidden window was found, where it sat on the screen, and the name only of a known helper app. Never another app's name, a window title, a screenshot or window contents |
| Your computer's settings the check needs: screen brightness, whether the computer can sleep, low power mode, the clock, and your camera's resolution. The app sets what it needs for the check and puts it back afterwards | In the Verified app | Whether each setting was fine, and when it changed during the check |
| Your operating system and the app version | In the Verified app | Kept with the check results |
| A key made on your computer for this app (we receive the public half only), so the server can tell that results come from the same app | In the Verified app | The public key |
| Your video in the call, as seen by the interviewer's browser | During the call | See the interviewer table above. We compare your face in the call with the face your own camera sees. We do not record the call |
We do not ask for or read ID documents or photo IDs. We do not use your face or voice to build a profile, or to recognise you in another interview. Every interview starts fresh: nothing about you is carried from one interview to the next.
From everyone who uses the server
Like any website, our server sees the IP address of each request, the time, and the address that was asked for. Our web server's access log shortens each IP address and removes the secret part of each check link and every access code. Candidate links contain a secret code. We keep the code out of our logs.
4. What we do not do
- We do not record calls, and we do not store video or audio from a check or a call.
- We do not sell your data or share it with advertisers, data brokers or anyone who would use it for marketing or credit decisions.
- We do not use your data for anything except running the check you or your interviewer asked for.
- We do not make hiring decisions. We do not say that a person did something wrong. "Can't confirm" means a check could not be done right now. It is not an accusation, and the interviewer decides what it means.
5. Who we share data with
Only the services below, and only to run Verified. Each handles the data under its own terms of service.
| Who | What for | What they get |
|---|---|---|
| Amazon Web Services, in Oregon, United States | Hosts our server and its disk | The data in sections 3 and 6, stored on our server |
| Resend (only when email is on) | Sends the check link email and the call notices (check open, time changed, call cancelled) on behalf of Verified, from [email protected] | The guest's email address and first name, the interviewer's name and email (as reply-to), the interviewer's company name when known, the meeting title and time, and the link. Resend keeps its own records of the emails it sends, under its terms |
| Deepgram | Turns your spoken sentences into text | The audio of you reading, in a live stream, for the moment you read |
| jsDelivr and Google (storage.googleapis.com) | Serve the open-source hand and face tracking program and its models to the check steps | Your IP address and browser details, like any website you visit. No video or personal data |
| Google (Sheets and Apps Script) | Stores the waitlist form on this website | What you typed into the waitlist form (section 13) |
| Microsoft Clarity | Shows us how people use this website | Clicks, scrolling and mouse movement on this website (section 13) |
| Law enforcement or a court | Only if the law requires it | What the law requires. We tell the person concerned where the law allows it |
| A buyer of the business | Only if Verified is sold or merged | The data stays covered by this policy until you are told of a change |
The interviewer who set up an interview sees its results. That is the purpose of the service.
6. How long we keep data
Video and audio are not stored at all. Face samples from the call are dropped after the comparison. Face measurements from your own camera are dropped after the comparison too, except the mouth-openness numbers kept with the voice numbers (section 3). What we do keep, and for how long:
| What | How long |
|---|---|
| Interview details: the meeting title, time, Meet code, the interviewer's name and email, each guest's name and email, and their check link | 7 days after the interview's last activity, then deleted |
| Check results and the signed records of each check: step outcomes, camera answers, face-comparison scores and statuses, hidden-window answers, the app's setting records | 7 days after the interview's last activity, then deleted |
| The stills shown to the interviewer for a finding, while it lasts and after it ends (only the latest pair of each finding is kept) | Memory only. Deleted when the call ends, when the guest leaves, or after 2 hours |
| Voice and mouth-movement numbers from the check steps and the call (no sound, no pictures, no names) | About 7 days, then deleted |
| Each beta company's name and a fingerprint of its access code (never the code) | While the company is in the beta; deleted when the company asks |
| Diagnostic logs kept by the Verified server, and its records of which results were viewed (no names, emails or pictures) | 7 days, then deleted |
| The server's system log and the web server's access log | Up to 30 days, then deleted |
| On the interviewer's own computer: the access code, and the Google account address Meet shows | Until the interviewer removes the access code (Help, then Remove code); that removes both |
| On the interviewer's own computer: the diagnostic log | Until the interviewer clicks Clear in Diagnostics |
| On the interviewer's own computer: call keys, the last 20 calls with their guests' check links, and the guest switch choices | Until the interviewer removes the extension. A call also drops out sooner when 20 newer calls push it out, when its key expires, or when our server no longer has it. Removing the access code or clicking Clear does not delete these |
| On the candidate's computer: the app's own settings and records of the check | Until the candidate removes the app. The reading video is deleted as soon as it is checked |
We delete sooner if you ask (section 8). We do not keep separate backup copies of this data.
Some research records follow separate rules; ask us for details.
7. How we keep it safe
- Everything between your browser or app and our server travels over HTTPS. The extension refuses to talk to a server that does not use HTTPS. Invite emails go from our server to Resend over HTTPS, and from Resend to the guest as ordinary email.
- Our server is reachable from the internet only through HTTPS. Access to the server itself is limited to one named person, with a key, from one network address. Service keys are kept in a protected settings file on the server, not in our code.
- Each check link is a long secret, meant for one person. Each team's access code and each interview's key are long random codes. The server stores only a fingerprint of a team's access code, never the code.
- Our staff do not read your data, except to fix a problem you or your interviewer asked us to look at, to protect the service from abuse, or when the law requires it.
- If we learn of a data breach that affects you, we will tell you and the people the law requires without undue delay.
8. Your choices and rights
- Candidates: you can decline on the consent screen and still join the meeting. You can close the app at any time; your interviewer then sees that the check stopped. You can ask us to delete your data from any interview, or to send you a copy, by writing to [email protected]. Tell us the email address the check link was sent to. We answer within 30 days.
- Interviewers: you can remove your access code or the extension at any time. You can click Clear in Diagnostics. You can ask us to delete an interview you set up, or all of your team's data, by writing to us.
- Everyone: you can ask us to correct data about you. If you live where the law gives you more rights (for example in the European Economic Area, the United Kingdom or California), write to us and we will tell you how we apply them. You can also complain to your local data protection authority.
9. Children
Verified is for professional calls. It is not meant for anyone under 16, and we do not knowingly collect data from them.
10. Chrome Web Store user data policy
The use of information received by the Verified extension, including information read from Google Calendar and Google Meet pages, will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
11. Changes to this policy
If we change what we collect or why, we will change the date at the top and, for anything that matters to you, tell interviewers in the extension's store listing and candidates on the consent screen before the change applies to them. Older versions are available on request.
12. Contact
Bhanu Kowshik Papineni, [email protected]
13. This website and the beta waitlist
The beta form on this website asks for your full name, company, role and work email. We also record when you sent the form and which button you used to open it. Your answers go from your browser to a Google Sheet owned by the Verified founder, through Google Apps Script. Google stores this data for us as a service provider. The company that hosts this website handles standard technical data, such as your IP address, only to deliver the page. We use them only to review beta requests and to contact you about the beta, and keep them until the beta selection is complete or until you ask us to delete them, whichever comes first.
We use Microsoft Clarity to understand how people use this website. It records interactions such as clicks, scrolling and mouse movement, can replay a visit, and sets cookies to recognise repeat visits. Anything you type into the beta form is masked and never recorded. Microsoft processes this data as described in the Microsoft Privacy Statement. We do not use it for advertising. If you pause the page's animations, the page saves that choice in your browser. It does not identify you and is never sent to us.