VUEMesh

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

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.

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_.

WhatWhereWhy
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 logIndexedDB, 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 roleLocal 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 keyLocal storage: vm_host_…, vm_callkey_…, vm_callpin_…, vm_tv_key_…, vm_identityThe 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 keyLocal storage: vm_streamSo 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 nameLocal storage: vm_name, vm_tv_name, vm_remote_name, vm_share_nameSo 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 choicesLocal storage: vm_seq_…, vm_cut_…, vm_crew_…, vm_angles_…, vm_livemix_…, vm_lt_…, vm_speakers_…, vm_rundown_…, vm_msgs_… and similarSo 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 pageLocal storage: vm_theme, vm_layout, vm_camprefs, vm_call_…, vm_terms, vm_privacy_ok, vm_captions, vm_faces and similarPreferences.
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 inSession storage: vm_off_…, vm_callin…, vm_adminGone when the tab closes.
The app itself: its pages, scripts and picturesThe 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.
What this browser has now

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:

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.

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.

Captions and face tracking

Both run on your own device, in the browser, and both are off until someone turns them on.

Captions

Face tracking

Logs, and the ones that can be switched on

Streaming and publishing

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

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.

Nothing is sold or shared for advertising, and nothing is used for automated decisions about you.

Your choices and rights

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.