Privacy
What VUEMesh keeps
Exactly what VUEMesh keeps, where, and for how long. This page describes the site at vuemesh.com. VUEMesh is open source (MIT), so anyone can run their own copy; a copy run by someone else is theirs, and so is what it keeps.
Updated 15 November 2026 (VUEMesh 0.96.0): the two principles (collect as little as possible, keep production on your devices), and that "no trackers" means no third-party ones, beside our own anonymous counts. 0.95.0: shows end when nobody is at the studio, and what the server keeps about a show while it runs. Before that (0.90.0): calls, the relay and when it may be off, captions and face tracking, the logs that can be switched on, and streaming and publishing.
- The short version
- In this browser
- On our server
- Calls
- The relay
- Captions and face tracking
- Logs
- Streaming and publishing
- Other services
- Who's responsible
- Your rights
The short version
Two decisions shape everything below. Collect as little as possible (data minimization): no accounts, no identities, no recordings and no location reach us, only what devices need to find each other, and that deletes itself. Keep production on your own devices (data locality): cameras, the studio, recording, editing and captions all happen on the devices at the show, not on a cloud media platform.
- No cookies, no accounts, no ads, no third-party trackers or analytics. VUEMesh does count its own use, anonymously: page views and daily totals, with no identifier kept that could follow you, nothing shared with ad or analytics companies, and none at all if your browser asks not to be tracked. There's nothing to accept.
- Never your location. VUEMesh doesn't ask where you are, and there's no public list or map of events.
- Your recordings stay on your devices. Video and sound go from device to device. Our server never receives them, and nothing is uploaded to be published (not yet).
- Calls go from device to device, encrypted. Names, pictures, sound and shared screens go straight to the others in the call, never to us. Nobody gets in without the link, or the code and PIN, and someone already in lets each person in.
- When devices can't reach each other, our relay passes on what it can't read. It's encrypted end to end and the relay keeps nothing. It may be switched off at any time.
- Captions and face tracking happen on your own device, with models that run in the browser. No picture or sound is sent anywhere for them, and face tracking isn't face recognition.
- A show's name never reaches our server. It stays on the host's computer and travels between the show's devices over their own links.
- The server keeps an event's code and settings for 30 days (a call's for a day), so devices can find each other, then deletes them by itself.
- Logs are short-lived, and the only one with addresses in it is off unless the maintainer switches it on to fix a problem with the relay, for a day at most.
- You can clear everything VUEMesh keeps in this browser with one button, below.
In this browser
VUEMesh is an app that runs in your browser, and it keeps its work there, on this device only, the way a document editor keeps files. None of this is a cookie and none of it is sent anywhere by itself. It's grouped here by what it's for; every key starts with vm_.
| What | Where | Why |
|---|---|---|
| Your recordings and edits: camera and microphone clips, clips waiting to reach the studio, the recorded program and its captions, break-reel images and videos, the show log | IndexedDB, database vuemesh (clips, outbox, program, reel, showlog) | So footage survives a reload or a dropped connection, and you can export it later. Delete or export it from Your events on this device on the home page, or from My events on a phone. |
| Your events and calls: the ones you made or joined, their names and codes, and your role | Local storage: vm_events, vm_last, vm_ev_… | So you can get back to them. |
| Keys: a host's key for each event it made; a call's key and PIN for a call you started or joined by its link; a TV's key; this device's own signing key | Local storage: vm_host_…, vm_callkey_…, vm_callpin_…, vm_tv_key_…, vm_identity | The host key is what lets you run the studio for your event, and a call's key and PIN let you rejoin it and invite others. The signing key lets a phone sign its clips so the studio can check nothing was changed. Keys never leave the device except to prove who you are to the event or call. |
| Your streaming settings: the service, its address and your stream key | Local storage: vm_stream | So you don't have to paste the key again. It goes only to the streaming service you chose, and only while you stream. |
| Names you typed: your name when joining, a TV's name, a remote's name, a shared screen's name | Local storage: vm_name, vm_tv_name, vm_remote_name, vm_share_name | So you don't have to type it again. |
| Each event's edit and show: the timeline, live cuts, crew, camera angles, the mixer, lower thirds, speakers' numbers and names, rundown, messages, output and recording choices | Local storage: vm_seq_…, vm_cut_…, vm_crew_…, vm_angles_…, vm_livemix_…, vm_lt_…, vm_speakers_…, vm_rundown_…, vm_msgs_… and similar | So the studio comes back as you left it. |
| Settings: light or dark, layouts, camera preferences, a call's microphone, camera and caption choices, which tips you've seen, that you agreed to the Terms, and that you've seen the note about this page | Local storage: vm_theme, vm_layout, vm_camprefs, vm_call_…, vm_terms, vm_privacy_ok, vm_captions, vm_faces and similar | Preferences. |
| This visit only: a phone's clock offset to the QR Beacon, that this tab was let into a call (so a dropped connection comes back without waiting), Admin's key while signed in | Session storage: vm_off_…, vm_callin…, vm_admin | Gone when the tab closes. |
| The app itself: its pages, scripts and pictures | The browser's cache, through a service worker (vm-app-v1) | So the app opens with no internet, for a show on a network of its own. |
Checking…
This removes every recording, edit, key and setting VUEMesh has in this browser, and the saved copy of the app. Export anything you want to keep first, from the home page. It can't be undone, and without its host key you can't run the studio for an event again.
On our server
The server is a small switchboard. It helps devices at an event or in a call find each other, then gets out of the way. It keeps:
- Each event: its code, shape (landscape or portrait), settings, the Terms its people agreed to, a one-way hash of the host's key, when it was made, when the studio was last open, and for its show: when it started, when a person at the studio last said it was still running, whether the studio is recording or streaming and how many devices are connected (a number, not who), and when and why it ended. Not its name: that stays on the devices. A kiosk show keeps only that it has been named. Deleted automatically 30 days after it's made (12 hours for a show started at a kiosk), or sooner when the host deletes it.
- Each call: see Calls. Deleted automatically a day after it's made.
- Who's connected right now: a random ID for each device in the event, the name it joined with (none in a call), and its role (camera, microphone, studio, TV, a call's guest, and whether it's waiting to be let in). Used to pass the handshake between devices. Deleted within a day.
- How many calls each address started in the hour, and how many relay passwords it asked for, each counted under a mark made from the address with that day's random salt, and deleted after the hour, so nobody can start thousands.
- Anonymous counts for each day, which don't expire: events made and run, how many cameras, computer screens (from the Share page), microphones, viewers and TVs joined, recordings made, hours of footage, live cut and streaming, how long TVs watched, calls started, how many people were in them, how many times devices connected to them and how many screens were shared in them (that a screen was shared, never what was on it), and how much the relay passed on. So a phone that rejoins is counted once, the event holds a one-way code made from that phone's random camera ID, deleted with the event; a call does the same for each device let into it and each that shares its screen, deleted with the call after a day. The day's counts name no person, device, place or event. They may be shared, for example with partners or funders.
- Anonymous page views: one count per page load, by page, with the site that linked to it, device type (phone, tablet, desktop), browser name, and country if the network provides it. A visitor is counted once a day using a hash of the day, the address and the browser with a random salt made fresh each day. The hash isn't kept with the counts, and the hash and that day's salt are both deleted after two days, after which nobody, us included, can work out an address from it. With them, how each connection between two devices went (on the same network, straight across the internet, or through our relay), counted once by each device when it connects, so we know how often the relay is needed; nothing about the devices or the show. None of this is sent if your browser asks not to be tracked (Do Not Track or Global Privacy Control).
Recordings, pictures and sound never go to the server.
A show runs only while a person is at its studio. A studio with no phones, screens or TVs in, nothing recording or streaming, and nobody using it for 30 minutes pauses itself. Every 12 hours it asks "Still running this show?"; if nobody answers in 10 minutes, the show ends: recording and streaming stop, every phone stops recording and is told the show has ended, and the studio can't carry on until a person opens it again. The server ends it too, shortly after, if a studio doesn't. So nobody can be recorded for days with no one at the studio. What was already recorded stays on the devices that recorded it. Kiosks (a show that ends when its guests leave) and a TV's own code (nothing recorded) don't ask.
Calls
A call (/call) is up to six people on cameras, microphones and shared screens, everyone connected straight to everyone else.
- Device to device, encrypted. Names, pictures, sound, shared screens (and their sound, when you choose to share it), captions and messages go over each pair of devices' own encrypted link, never to our server. When two devices can't reach each other, that link goes through our relay, still encrypted.
- Getting in. A call's key is in its link after the
#, which browsers never send to a server. Nobody gets in without the link, or the call's code and its PIN, and someone already in the call lets each person in. A name given while waiting goes with the knock to the people in the call, and isn't kept. - What the server keeps for a call, for a day: its code, a one-way hash of a one-way hash of its key, a one-way hash of its PIN and how many wrong PINs were tried, one-way hashes of the passes of devices let in (so a dropped connection comes back without waiting), the random device IDs taken out of it, and whether it's locked. No names, and nothing anyone said or showed.
- Nothing is recorded by the call. A studio can join a call; when one is in it, everyone is told plainly (their picture, sound and screen can be put on its show, recorded or streamed by it) and sees when it's recording or live.
- Captions in a call are made on each person's own device: see Captions and face tracking.
The relay (TURN), and when it may be off
When devices connect, each asks our STUN server (stun.vuemesh.com) for its own public internet address, so they can find a path to each other. Devices on the same network never need more. When two devices can't reach each other directly (a phone on mobile data, a strict office network), their pictures and sound go through our relay instead (TURN), for a show or a call.
- It can't read what it passes on. It's encrypted between the two devices. The relay keeps no recordings and, normally, no logs: its log is only counted as it's written (relays started, data relayed, requests it turned away, such as a wrong password or an address it won't relay to) and then forgotten. The counts, with no addresses, go to our server every minute and are kept with the day's anonymous counts.
- A password for the day. To use it, a device gets a password from our server that's good for a day and has nothing about the device in it. Our server counts how many each address asks for in an hour (as above), so nobody can collect thousands.
- It may be switched off at any time, without notice. The maintainer can turn it off from the admin page, and it switches itself off when the month's data allowance runs out (it stops giving out new passwords at 90%, and closes at 100%). While it's off, devices that can't reach each other directly can't connect: a phone on mobile data may not get into a show or a call. Devices on the same Wi-Fi aren't affected, and nothing is sent through anyone else's relay instead.
- It runs on AWS, like the rest. A copy of VUEMesh run by someone else uses their relay, or none.
Captions and face tracking
Both run on your own device, in the browser, and both are off until someone turns them on.
Captions
- In the studio, live captions of the program are made on the studio's computer by the browser's own on-device speech model, with "on this device only" asked for. If the browser can't promise that, there are no captions: there's no fallback to a server. The captions are kept with the program's recording in this browser, and downloaded beside it.
- In a call, each device that can recognise its own microphone's speech that way does, when anyone in the call turns Captions on, and sends the words to the others over the call's encrypted links. Nothing is kept: the words are shown and gone. A device that can't make captions (an iPhone, Safari or Firefox, for now: only Chrome and Edge on a computer can) still shows the words of anyone whose device makes them, and says so.
- The speech model. The first time, the browser downloads its speech model from its maker (Chrome from Google, Edge from Microsoft) and keeps it. That download is between your browser and its maker; no sound goes with it, and VUEMesh sends nothing to them.
Face tracking
- On the studio's computer, and not face recognition. When a host turns it on, the studio finds faces (and where people are, by their pose) in its cameras' pictures to frame the shot and see who's talking. Nothing describing what anyone looks like is made or kept, and no picture is sent anywhere.
- Speakers, not identities. People are told apart by who's talking when, and where they are in each shot; the studio keeps only "Speaker 1, Speaker 2…", any names the host types, and where each was last seen in each camera's picture, in this browser (
vm_speakers_…). - The models come from vuemesh.com. The face finder and pose finder (Google's MediaPipe, Apache-2.0 licensed) and their models are served from vuemesh.com itself and run in the browser. MediaPipe normally reports its own usage to Google; VUEMesh's copy has that taken out, so it has nowhere to send anything.
Logs, and the ones that can be switched on
- The server's own logs: errors and timings, no page contents, no recordings. Kept for 14 days, then deleted.
- The relay's troubleshooting log: off unless there's a problem to fix. If the relay misbehaves, the maintainer can switch on its log from the admin page, for an hour or a day at most. While it's on, the relay writes down what it does, including the internet addresses of the devices it relays (not what they send, which it can't read), so a fault or an attack can be traced. That log is kept only in the relay's memory (never on its disk, never sent anywhere), only the maintainer can read it, and it's deleted when the time's up or the relay restarts. Admin shows when it's on.
- The show log, in the studio's browser. While a show runs, the studio keeps a second-by-second record of how it went (frame rate, sound levels, what was on air, devices connecting and dropping) in this browser, so a problem can be traced afterwards. It stays here: it's sent only if you choose Save show log and send the file to someone. It holds no recordings.
- Diagnostics, when you ask for them. Help → Copy diagnostics (or Something wrong? on a phone) makes a short report of this browser's version, what it can record and play, and recent messages and errors, for you to read and paste where you choose. Nothing is sent by itself.
- Mail to info@: see If you email us.
Streaming and publishing
- Publishing isn't here yet. Uploading a finished film to a VUEMesh watch page is planned as a future feature of the platform. It's built but switched off on vuemesh.com, so nothing you make is uploaded to us. If it's turned on, it will be something a host chooses for each film, and this page will say first what it keeps and for how long.
- For now, share a show through a streaming service. The studio streams the program straight from your computer to the service you choose (YouTube, Twitch, Facebook and the like): directly from the browser, or, for services that need RTMP, through the VUEMesh relay program running on your own computer. It goes to that service only while you're streaming, never through our server, and that service's own privacy terms apply to it. You can also export your recordings and upload them anywhere yourself.
If you email us
Mail to info@vuemesh.com is received by Amazon's email service, checked for viruses and spam, and forwarded to the maintainer's inbox. A copy is kept encrypted on AWS for 30 days, then deleted automatically; the forwarding keeps a one-line record that a message was passed on (its ID, not its contents) for 14 days. Nobody else reads it, and the address isn't added to any list.
Other services your browser talks to
- Amazon Web Services hosts the site, the server, the STUN server and relay, and mail to info@. Like any host, it handles your requests. AWS acts for us as a processor under its data processing terms; the servers are in the United States (Ohio), and transfers from the EU and UK rely on the EU–US Data Privacy Framework and the standard contractual clauses in those terms.
- Your browser's maker, only if you turn on captions: the one-time download of its speech model (above).
- Nothing else. No fonts, scripts or images come from anyone else; the typefaces and the face-tracking models are served from vuemesh.com itself.
- Only when you set them up: a streaming service you stream to, and Patreon or email if you follow those links.
Who's responsible, and on what basis
vuemesh.com is run by Joshua Allen Talbott (Ohio, United States), who decides what is kept and is responsible for it (the "controller" under the GDPR and UK GDPR). Contact: info@vuemesh.com.
- Running your event or call (the event or call record, who's connected, the handshake between devices, the relay when it's needed): because you asked for it. It's needed to provide the service (GDPR Art. 6(1)(b)).
- What's kept in your browser: it's strictly necessary for the app you're using to work, so it doesn't need a consent banner (ePrivacy Directive Art. 5(3)). You can clear it at any time, above.
- Anonymous counts and page views, server logs: our legitimate interest in keeping the service working, secure, and knowing whether it's used (Art. 6(1)(f)). You can opt out of page views with Do Not Track or Global Privacy Control.
- The relay's troubleshooting log, when it's switched on: our legitimate interest in finding and fixing a fault or an attack on the relay (Art. 6(1)(f)). It's kept for a day at most.
- Mail you send: our legitimate interest in answering you (Art. 6(1)(f)).
Nothing is sold or shared for advertising, and nothing is used for automated decisions about you.
Your choices and rights
- Delete or export a single event's recordings from the home page, or a phone's from My events.
- Clear everything with the button above, or with your browser's own "clear site data".
- Turn on Do Not Track or Global Privacy Control and no page views are counted.
- A host can delete an event from the server at any time from the studio; it deletes itself after 30 days anyway. A call deletes itself after a day.
- Leave captions and face tracking off, and nothing runs for them.
- Run your own copy: it's MIT licensed, and your copy keeps only what you choose.
- Your rights: you can ask to see, correct, or delete what we hold about you, to restrict or object to its use, or to get a copy of it. Write to info@vuemesh.com. With no accounts, the server usually can't tell which records are yours, so tell us the event or call code, or the message you sent, and we'll answer within a month.
- You can also complain to a data protection authority, for example the one where you live (in the UK, the ICO).
Changes and questions
If what VUEMesh keeps changes, this page changes with it, in the same release (it's in the public repository, so every change is visible). Questions: get in touch, or open an issue.