This policy explains what TSRB Meeting Producer collects, what it does not, and what we do with the difference. It covers the desktop application, this website, and the account and licensing services behind them.
The short version: your meeting audio and video never reach us. The desktop application sends captured media out as NDI on your own local network and, if you choose to record, writes files to your own disk. It is not uploaded to us, relayed through us, or stored by us. We cannot see it, and we could not produce it if we were asked to.
1. Who we are
TSRB Systems LLC, of Pensacola, Florida, United States, is responsible for the personal data described here. Contact us at info@tsrbsys.com.
2. Your recordings and live output
This is the part most people want to know about, so it comes first.
- Captured audio, video, and screen share go to two places and no others: NDI output on your local network, and, when you enable recording, Matroska files written under the application's own captures folder on your machine.
- Those files are yours. We do not hold a copy, a key, or any way to reach them.
- We do not collect meeting content, participant lists, chat, or meeting metadata.
The only requests the desktop application makes to our servers are to sign you in and to check your licence. Those carry a session identifier and an access token — no media, and nothing about the meeting.
3. What we collect
| Data | Where it comes from | Where it lives | Why |
|---|---|---|---|
| Email address and password hash | You, at sign-up | Our database | To sign you in |
| Display name | You | Our database | To show who is signed in |
| Zoom user id, account id, and email | Zoom, when you install the app | Our database — the email is erased when you remove the app | To match the installation to your account |
| Zoom OAuth refresh token | Zoom, after you consent | Your machine only | To sign you back in without asking again |
| Zoom per-meeting join token | Zoom, per join | Memory only, used once | To join a meeting as you |
| Stripe customer and subscription ids | Stripe | Our database | To bill you and track your plan |
| Billing name and address | You | Stripe | Invoicing and tax |
| Seat and session usage | Our services | Our database | To enforce how many sessions may run at once |
| IP address and browser user agent | You, at the moment you accept our terms | Our database | Evidence of which version of the terms you accepted, and when |
| Email address of someone you invite to a seat | You, when you send the invitation | Our database | To deliver the invitation and let them claim the seat |
| Application logs | Our services | Files on our servers | To keep the service running and diagnose faults |
| Captured meeting media | The meeting | Your machine only | The product's purpose |
We never see your card number. Card details go from your browser straight to Stripe. We receive an identifier and the last four digits, and nothing else.
4. Zoom data in detail
- We request two Zoom scopes and no others:
user:readanduser:read:token. They let us confirm who you are and obtain a token to join a meeting on your behalf. - Your Zoom refresh token is stored only in your own profile on your own machine. It is never sent to our servers.
- When you install the app from the Zoom Marketplace we store an installation record: your Zoom user id, Zoom account id, Zoom email, the time of installation, and which TSRB account it is linked to. The email is erased automatically when you remove the app — see below.
When you remove the app
Removing the app in Zoom invalidates the token immediately, and the application treats the next refusal as a sign-out. Zoom also notifies us, and on that notification we:
- erase your Zoom email address from our database;
- unlink the installation from your TSRB account; and
- record the time the app was removed.
What remains is the Zoom user id, the Zoom account id, and the install and removal timestamps — an unlinked record that the app was installed and then removed, with the one piece of personal data taken out of it. If you would like that remainder erased too, email us and we will delete it.
5. Who else processes your data
We use a small number of providers. We do not sell personal data, and we do not share it for advertising.
| Provider | What for | What they receive |
|---|---|---|
| Zoom | The integration itself | OAuth tokens, your Zoom display name and email |
| Stripe | Payments | Billing details and payment methods |
| Akamai (Linode) | Hosting | Everything stored on our servers |
| Microsoft | Transactional email, code signing, source hosting | Your email address, for the mail we send you |
6. How long we keep things
| Data | Kept for |
|---|---|
| Account records | As long as the account exists, then 30 days after you ask us to delete it |
| Billing and invoice records | Seven years, as tax and accounting law requires |
| Application logs | Reset each time we deploy a service — in practice days, not months |
| Zoom email address | Erased automatically when you remove the app |
| Zoom user id and account id | Until you ask us to erase them |
| Terms acceptance record, including IP address | While your account exists, then six years as evidence of the agreement |
| Seat invitations you send | Until you ask us to erase them |
| Zoom refresh token | Until you sign out or remove the app — and only on your machine |
| Your recordings | Entirely up to you; they are on your disk |
7. Your rights
Depending on where you live — including under the GDPR and UK GDPR in Europe and the United Kingdom, and under the CCPA and CPRA in California — you may have the right to ask us for a copy of your personal data, to correct it, to delete it, to receive it in a portable form, or to restrict or object to how we use it. You may also withdraw consent to the Zoom integration at any time by removing the app in Zoom.
To exercise any of these, email info@tsrbsys.com. We answer within 30 days. We will not charge you for it, and we will not treat you differently for asking. Note that deleting your account ends your subscription; we cannot keep one without the other.
8. How we protect it
- Every public endpoint is served over TLS.
- The servers holding your data use encrypted disks. The encryption is applied and the keys are held by our hosting provider, Akamai (Linode), not by us.
- Passwords are stored as salted hashes and cannot be reversed. We cannot tell you your password — only help you set a new one.
- Sign-in uses OAuth 2.0 Authorization Code with PKCE, with per-attempt CSRF protection. There is no implicit flow.
- Released applications and installers are Authenticode-signed and timestamped, and the build fails rather than shipping anything unsigned. The signing keys are held by Microsoft Azure, never by us.
- Our code is scanned for insecure patterns and for committed credentials on every change, and no change reaches production without review.
- Access to production systems is limited to the engineers who operate them.
No system is perfectly secure and we will not pretend otherwise. If you believe you have found a vulnerability, please write to info@tsrbsys.com. We will acknowledge you, and we will not pursue good-faith research.
9. Children
This is a professional broadcast tool. It is not directed at children and we do not knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, contact us and we will delete it.
10. Where your data is processed
Our servers are in the United States, and our providers may process data there and elsewhere. If you are in the European Economic Area or the United Kingdom, that means your personal data is transferred outside it; we rely on the European Commission's Standard Contractual Clauses, or an equivalent safeguard, for those transfers.
11. Changes to this policy
If we change this policy in a way that materially affects you, we will tell account holders by email before it takes effect, and update the date at the top of this page. The current version always lives at meetingproducer.tsrbsys.com/privacy.
12. Contact
TSRB Systems LLC
Pensacola, Florida, United States
info@tsrbsys.com