Lumbus Live Privacy Notice

This notice explains what Lumbus Live collects and why, and adds to the Lumbus Privacy Policy, which covers every Lumbus product and your rights. Lumbus Technologies Limited is the controller for both.

Read together with the Lumbus Privacy Policy. Last updated 14 October 2026.

1. What Lumbus Live collects

Your account — email, name and sign-in method, shared with the rest of Lumbus.
Your phone number, only if you turn on text alerts. Only you can see it, and switching alerts off removes it.
Stream keys for the destinations you add — encrypted at rest with a key specific to your studio, decrypted only for your studio machine (which keeps a copy of its current settings on its own disk so it can keep streaming without us), and shown to you only as the last four characters.
Your studio set-up: scenes, overlays and media you upload, destinations, automation settings, schedule, team members (including the email address of anyone you invite) and the audit log of who did what.
Studio telemetry: bitrate, round-trip time, dropped frames, scene switches, engine status, what the machine reports as degraded, and region — what the dashboard shows you, kept as session history.
From the device that is your studio's camera, while it sends (your phone with the Lumbus Live app, or this site's camera page): its heat state as the operating system reports it, battery level and charging, the battery's temperature where the phone reports it, the network type and mobile radio, and how its connection is doing (bitrate and frame rate sent, frames dropped, round trip, loss), every 15 seconds — so its picture steps down only when it must, your dashboard can say how it is doing, and a hot device can raise an alert. Never its location, and nothing of the picture.
Recordings, only when you switch recording on.
From a recorded stream, to find your moments: a transcript of the recording's audio, the timing of chat messages (not their text beyond what your chat overlay already keeps), audio-level peaks as numbers, scene switches and the moments you mark; the moments we suggest, the clips you export, and your thumbs up and down on them (your own learning profile, which you can clear).
Your brand kits (logo, colours) and saved shows; your spend limit and extra-time ledger.
On Studio Max: the hashed form of each API key you create (never the key itself, which is shown to you once), its name and when it was last used; the web addresses, chosen events and secrets of your webhooks, and a 30-day log of what was delivered to them.
From a guest who adds their own platform to your broadcast: that guest's stream key, sealed for your studio; from a guest or host who records locally: the recording they upload.
From the Lumbus Live app: a push-notification token and basic device details, so alerts reach you.
For hardware bought before 6 October 2026, or Lumbus SIMs bought before 13 October 2026: your delivery address and the purchase details, and a SIM allowance's usage while it runs. For a Lumbus Connect bonding allowance bought before 6 October 2026, the traffic volumes the bonding provider measured while it ran.
If you pay a founding reservation deposit: the amount and currency, the date, the prices held for you, and our payment provider’s references for the payment and any refund (reservations made before 6 October 2026 may also record the hardware you then said you planned on). Your card details go to the payment provider directly and never reach us.
Your country, taken from your IP address on the website only to show prices in your currency. It is not stored. A currency you choose yourself is remembered on your own device, not by us.
Support conversations with us.
On the public watch page: a random token the viewer’s browser keeps, and how long that browser stayed on the page. It counts the host’s viewer hours and applies the host’s seat limit; it is never an identity, and it is deleted after the month it belongs to and the next.

2. What we don’t collect

We don’t keep your video. Your stream passes through your studio to the platforms; nothing of it is stored unless you turn recording on. We don’t watch your stream. When recording is on, after the stream the recording's audio is transcribed and its chat timing and telemetry are read, by software, to suggest moments; no person at Lumbus watches it. Chat commands are acted on by your studio, not stored beyond the audit entry.

3. Why we use it

To provide the service you asked for — running your studio and delivering your stream (performance of a contract).
To keep you streaming — alerts when your signal drops or an allowance runs low, fraud and abuse prevention, service health (our legitimate interests, balanced against yours).
With your consent — text alerts, and any marketing about Lumbus Live, which you can withdraw at any time.
To meet legal obligations — records we must keep as a UK company.

4. Who handles it for us

We use a small number of providers under contract, each only for the purpose named:

Supabase — accounts and database.
Vercel — hosting of the website, dashboard and the API the app uses.
Cloudflare — recordings storage (R2), delivery of the public watch page’s video to viewers, and the bot check on our forms.
Twilio — text alerts, if you turn them on.
Expo — push notifications to the Lumbus Live app.
Resend — email.
The studio machines in the region you choose, run for us by our hosting providers there.
Our former connectivity supplier — only for a Lumbus SIM allowance bought before 13 October 2026 and still running: connection identifiers and usage, so that allowance works and is billed correctly until it ends.
Our former bonding provider — only for a Lumbus Connect allowance bought before 6 October 2026 and still running: the sign-in, connection identifiers and traffic volumes, so that allowance works and is metered until it ends.
Stripe — payments: your card is held by Stripe, never by us; we keep its references for your subscription, the trial, add-ons and refunds.
Deepgram — transcription of recorded audio (live captions and, after a stream, the transcript the moments are found from), and of nothing else.
Anthropic — ranking the candidate moments from the transcript excerpts and your learning profile, and translating subtitles, as text; no video goes to it.
Twelve Labs — a short-listed moment's video, only on accounts where it is switched on, to confirm the moment; we tell you on the moments page when it is.
The web addresses you add as webhooks receive the events you pick; those addresses are your choice and outside this notice.

We don’t sell your data and we don’t share it for anyone else’s marketing.

5. Where it’s kept

Accounts and studio data are held in the UK and the EU. Your studio itself, and any recordings, live in the area you picked for it, because that’s what keeps your stream fast: London (UK), Frankfurt (Germany) for Europe, New Jersey (USA) for the United States, or Mumbai (India) for the Middle East. A Lumbus Connect allowance bought before 6 October 2026 still passes through that provider’s servers until it ends, at the location confirmed with you when it started. Where data leaves the UK or EU we rely on adequacy decisions or standard contractual clauses.

6. How long we keep it

Recordings, and the transcripts, moments and clips made from them: while your subscription is active, up to your storage; 7 days after a studio ends, all of its recordings are deleted, and the transcript, moments and clips go with the recording they came from.
Watch-page viewer tokens and time watched: the month they belong to and the next, then deleted.
Stream keys: until you remove the destination or destroy the studio.
Phone number: until you switch text alerts off.
Session history, telemetry and the audit log: while your studio exists.
Moments telemetry (chat timing, audio peaks, scene switches, marks): 30 days, then deleted.
Camera device readings (heat, battery, connection): the latest while it sends; the history 30 days, then deleted.
Your moments learning profile: until you clear it or close your account.
API keys: until you revoke them; webhook delivery logs: 30 days.
Extra-time ledger and spend-limit settings: as billing records.
Push tokens: until you sign out of the app, or 30 days after the app last checked in.
For a SIM allowance bought before 13 October 2026, its traffic volumes (and, for a Lumbus Connect allowance bought before 6 October 2026, its bonding traffic volumes): for the life of the allowance they belong to, then as billing records.
Account, billing and hardware records: as set out in the Lumbus Privacy Policy and as UK law requires.

7. Your rights

You can ask to see, correct, export or delete your data, object to how we use it, or withdraw consent, as described in the Lumbus Privacy Policy. Write to live@getlumbus.com and we answer within 30 days. You can also complain to the UK Information Commissioner’s Office (ico.org.uk).

8. Security

Everything travels encrypted. Stream keys are encrypted at rest with a per-studio key. Access inside Lumbus is role-based and logged, and your studio’s own audit log shows every action taken on it.

9. Changes and contact

We update this notice when Lumbus Live changes; the date below tells you when. Questions: live@getlumbus.com. Last updated 14 October 2026.