Skip to content

Legal

Privacy policy

VirtualMeets is a video meeting service with live translation. This policy explains what happens to your data when you use virtualmeets.online or virtualmeets.uz: what we process and why, who helps us, and what we don't keep.

Draft: some details are still to be filled in.To be filled in
  • Meetings are not recorded. Video and sound travel to the other participants in real time.
  • To translate, speech is recognised, translated and voiced by automated services as you talk. VirtualMeets does not store the audio or the text.
  • Chat, subtitles and the transcript exist only in participants' browsers.
  • The AI assistant joins a call only when the host invites it; while it is there, what is said and written in the call goes to OpenAI, or to Yandex when the assistant speaks with one of Yandex's voices (whether the host picked it or it is the server's default), so that it can answer.
  • Nobody needs an account: anyone can start a meeting or join one.
  • We keep usage records (how many meetings, how long, in which languages) without any of their content.
  • For security, we keep the name and IP address of everyone who joins a call for 30 days, and the country, city and type of device they joined from as part of the usage records.
  • We don't sell personal data and don't show ads.

01Who we are

VirtualMeets is operated by To be filled in: legal entity: name and registration number (“VirtualMeets”, “we”). We decide how and why the data described here is processed. For anything about privacy, write to [email protected].

02Where VirtualMeets runs

The site, its database, the call server that carries meetings' video and sound, the translator and the AI assistant run on our own server, which we rent from Hostinger (Hostinger International Ltd.) in a data centre in Frankfurt, Germany. The call server is LiveKit, open-source software that we run ourselves.

Cloudflare protects the site from attacks and delivers it: visits to virtualmeets.online, and to virtualmeets.uz whenever that address is served through Cloudflare, pass through Cloudflare's network on their way to our server.

Connecting to a call. When a call starts, your browser may contact Cloudflare's connection servers (STUN) to find a way through your network. If your network doesn't let it reach our call server directly, the call goes through a Cloudflare relay (TURN) instead. The relay passes the encrypted stream on and can't see or hear what is in it. Both the connection servers and the relay see your IP address.

03During a meeting

Camera and microphone. When you join, your browser sends your video and sound to our call server, which relays them to the other participants. It is a live stream: nobody, VirtualMeets included, makes a recording.

Translation. Every meeting has a translator, a program on our server that joins the call like a participant. While someone speaks, it does the following with the sound of their microphone:

  • sends the speech to a recognition service, which turns it into text in the language the speaker picked: Soniox, or for Uzbek, ElevenLabs. So that it gets names right, Soniox also receives the participants' names, and the meeting code as a reference;
  • sends that text, with the last few sentences of the meeting and the names of who said them for context, to Anthropic's Claude model, which translates it into the languages of the other participants;
  • sends each translation to ElevenLabs, Cartesia or Soniox, which speak it in a synthetic voice, and passes the text on as subtitles.

This happens in real time. VirtualMeets does not store the audio, the recognised text or the translations. The providers receive them only to do this work for us; their own terms say how long they may keep data, for example to prevent abuse.

Voices. Translated speech uses a ready-made synthetic voice assigned to each speaker for the meeting. We don't create a copy of anyone's voice.

Name and language. The name you type in the lobby and the language you pick are shown to the other participants and used by the translator as described above. While you are in a call, its page may also show your name to someone who has opened the link and not yet joined, unless the host has locked the meeting. We keep your name in our database for 30 days, and the language with the usage records: see What we store.

Chat, subtitles and transcript. Messages, subtitles and the transcript reach the participants' browsers over the meeting's connection and exist only there. You can download the transcript during the meeting; once you leave it, all of this is gone from your browser. If the host invites the AI assistant, it receives the chat and the transcript too: see AI assistant.

Background blur. Blur runs in your browser, on your device. When you turn it on, your browser downloads the blur model from jsDelivr (cdn.jsdelivr.net) and Google Cloud Storage (storage.googleapis.com). Like any site your browser loads something from, they receive your IP address and browser details; your video is not sent to them.

04AI assistant

The host can invite an AI assistant into a call. It is a program on our server that joins the call like a participant, listens to the conversation and answers by voice when someone speaks to it. It comes only when the host invites it; everyone in the call sees while it is there, and the host can remove it at any time.

While it is in the call, it sends OpenAI (OpenAI, L.L.C., USA), or Yandex Cloud (Yandex.Cloud LLC, Russia) when it speaks with one of Yandex's voices (whether the host picked it or it is the server's default), what it needs to follow the conversation and answer:

  • the sound of everyone's microphones in the call;
  • the call's chat messages and the text sent to its shared clipboard, and the names of those in it;
  • the transcript of what was said before it came, as the browser of the person who invited it holds it;
  • the meeting context the host may give it: notes, an agenda or a chat (pasted, or a chat export such as a Telegram one), which it reads, retells and draws on.

The host's browser keeps that context for the meeting and hands it to the assistant whenever it is in the call; it is not stored on our servers. Only the assistant receives it, though it may retell it to everyone in the call.

VirtualMeets keeps none of this. By default, OpenAI does not use what it receives through its API to train its models, and it may keep it for up to 30 days to detect and prevent abuse. With a Yandex voice, Yandex Cloud receives the same and processes it in Russia; VirtualMeets turns off Yandex's logging of these requests. The assistant's answers are translated for the other participants like anyone's speech.

05Your account

At the moment nobody signs in: hosts and guests alike use VirtualMeets without an account, and we don't ask anyone for an email address.

06What we store

Our database holds:

  • for each meeting: its code, its host, when it was created and when its link expires (24 hours later), whether the host locked it, and when they ended it if they did;
  • for each call: when it started and ended, and the largest number of people in it at once;
  • for each time someone joins: whether they were the host, a guest, the translator or the AI assistant (and for the assistant, which voice it spoke with), the language they chose, when they joined and left, and a random identifier for their browser in that meeting;
  • for each request to join a call: when it was made and for which meeting, the name the person entered, their IP address, the rough place that address points to (country, region and city, with the city's coordinates), the text their browser sends about itself (its User-Agent) and what it tells: which browser (or which version of the VirtualMeets app) and system, and whether it is a computer, phone or tablet;
  • people a host removed from a meeting, by that random identifier, so they can't come back to it.

None of this contains what was said, shown or written in a meeting. We use it to run the service, apply the free plan, stop abuse and understand how VirtualMeets is used: for example, how many meetings take place, how long they last and which languages are spoken.

We keep the details of each request to join (the name, IP address, place and device) to protect the service from abuse, to look into problems and help people who write to us, and to understand where and on what devices VirtualMeets is used. We find the place on our own server, in a local copy of DB-IP's free database (db-ip.com) that the server downloads once a month: nobody else learns your address for this. Only we see these details, in an internal panel; we don't show them to other participants or pass them to anyone else. The panel also shows who is in each call right now: their names as shown in the call, roughly where they are and on what device.

We process these details because we have a legitimate interest in keeping the service safe and working. You can object to this: write to [email protected].

We keep account data while the account exists, and usage records for 12 months, after which we delete them. We delete the name, IP address and User-Agent of each request to join after 30 days; its place (country, region, city) and the type of browser, system and device stay with the usage records.

We keep copies of the database (backups) on the same server, to recover from a failure, and delete each one within 14 days. So whatever we delete, a deleted account included, is also gone from the backups within that time.

We also use your IP address to limit how often one address can create meetings, join calls, look up who is in a meeting, use the in-call and host controls, or ask for and try sign-in codes. Our server keeps a log of requests to the site for up to 7 days: the IP address, the browser, the address of the page and the time. We use that log only to find errors and stop abuse. For virtualmeets.online (and virtualmeets.uz when it is served through Cloudflare), Cloudflare also processes IP addresses and request details, to deliver and protect the site.

07Cookies and browser storage

We use only the cookies the service needs to work. There are no advertising or cross-site tracking cookies.

Cookie
vm_session
What it's for
Keeps a host signed in
How long
30 days
Cookie
vm_oauth_state, vm_oauth_verifier, vm_oauth_next, vm_oauth_desktop
What it's for
Protect the Google sign-in and remember where to return after it (or that the VirtualMeets app started it)
How long
10 minutes
Cookie
vm_apple_state, vm_apple_nonce, vm_apple_next, vm_apple_desktop
What it's for
Protect the Apple sign-in and remember where to return after it (or that the VirtualMeets app started it)
How long
10 minutes
Cookie
vm_desktop_code
What it's for
Hands a sign-in started in the VirtualMeets app for Windows or Mac back to the app
How long
5 minutes
Cookie
vmh_<code>
What it's for
Shows that this browser created the meeting, so it can manage it
How long
Until the meeting link expires
Cookie
vm_pid
What it's for
Keeps you the same participant when you reload a meeting page
How long
30 days, or the meeting's lifetime if longer
Cookie
vm-locale
What it's for
Remembers the site language you chose
How long
1 year

Your browser also keeps a few settings in its local storage: the name and language you last used in the lobby, and display preferences such as layout, subtitles, voice volume and background. If a host removes you from a meeting, it also keeps a note of that, so the meeting's page can tell you why you can't rejoin. If you are a host and give the AI assistant context for a meeting, your browser keeps that too, for that meeting. All of this stays on your device, and you can clear it in the browser's settings.

If we turn on Cloudflare Web Analytics, it counts page views without cookies and without identifying you.

08Who processes data for us

These providers help us run VirtualMeets. Each receives only what its job needs.

Provider
Hostinger (Hostinger International Ltd.)
What it does
Rents us the server the service runs on, in a data centre in Frankfurt, Germany
What it receives
Everything on that server: the database, the request log and backups; calls' video, sound and messages as they pass through
Provider
Soniox
What it does
Speech recognition, except for Uzbek; synthetic voices, for languages where we use it
What it receives
Speech audio, participants' names and the meeting code; text to be spoken, where it voices it
Provider
Anthropic (Claude)
What it does
Translation
What it receives
Recognised text, with recent sentences and the names of who said them for context
Provider
ElevenLabs
What it does
Speech recognition for Uzbek; synthetic voices
What it receives
Speech audio of people who speak Uzbek; text to be spoken
Provider
Cartesia
What it does
Synthetic voices, for languages where we use it
What it receives
Text to be spoken
Provider
OpenAI (OpenAI, L.L.C.)
What it does
The AI assistant, in calls where it speaks with one of OpenAI's voices
What it receives
While it is in a call: the sound of the participants' microphones, the chat, text sent to the shared clipboard, names, the transcript from before it came, and the meeting context the host gives it
Provider
Yandex Cloud (Yandex.Cloud LLC)
What it does
The AI assistant, in calls where it speaks with one of Yandex's voices
What it receives
While it is in a call with a Yandex voice: the sound of the participants' microphones, the chat, text sent to the shared clipboard, names, the transcript from before it came, and the meeting context the host gives it
Provider
Cloudflare
What it does
Network protection and delivery of the site (virtualmeets.online, and virtualmeets.uz when it is served through Cloudflare); connection servers and relays for calls; page analytics, if turned on
What it receives
Requests to the site that pass through Cloudflare, and IP addresses; the encrypted stream of the calls it relays, which it can't read
Provider
Google
What it does
Sign-in for hosts who choose it
What it receives
Your sign-in request
Provider
Apple
What it does
Sign-in for hosts who choose it
What it receives
Your sign-in request
Provider
Resend
What it does
Sends sign-in codes by email
What it receives
Your email address and the code

Our server is in Germany. The other providers may process data outside your country, including in the United States. Where the law requires safeguards for such transfers, they are covered by the providers' data processing terms, including standard contractual clauses.

09Your choices and rights

You can ask us to show, correct or delete the personal data we hold about you, or object to how we use it: write to [email protected].

You can stop using VirtualMeets at any time. Depending on where you live, you may also have the right to complain to a data protection authority.

10Age

VirtualMeets is for people aged 16 and over. If you believe someone younger has given us personal data, write to us and we'll delete it.

11Security

Connections to the site and to meetings are encrypted in transit. Session cookies are signed and can't be read by scripts on the page. Anyone who has a meeting's link can join it while it is open, so share it only with the people you invite; the host can lock the meeting and remove participants.

No system is perfectly secure. If we learn of a breach that affects you, we'll tell you as the law requires.

12Changes to this policy

When we change this policy, we update the date at the top. If a change matters, we'll also announce it on the site before it takes effect.

13Contact

Questions and requests: [email protected]. Postal address: To be filled in: postal address of the legal entity.

Terms of use