Privacy

The short version

MSRX Meeting has no accounts and no database. Meetings are not scheduled, attendance is not recorded, and there is no agenda, title or history kept anywhere — a room exists only while people are in it and is gone when the last person leaves.

Audio and video travel directly between participants, encrypted, without passing through a server. Recording, transcription and live captions are all switched off until somebody turns them on, and everyone in the room is told when they do.

What never leaves your device

• The video and audio of the call itself. It is carried peer to peer over encrypted WebRTC, so there is no media server to store it.
• Chat messages, which travel over the same direct connections.
• Recordings. Recording writes a file to your own machine and uploads nothing.
• Your display name, which is typed per meeting and kept only in your own browser.

What is processed when you switch the AI on

Two features send audio away from your device, and both are off until you turn them on.

Live captions use your browser's own speech recogniser. Where the browser can recognise speech on the device, nothing is sent anywhere; where it cannot, the browser sends the audio to its vendor's speech service. MSRX asks for the on-device mode first every time.

The transcript, the in-meeting assistant and the summary send short clips of your microphone, and later the text of the transcript, to Groq. Nothing is stored by MSRX at either end.

In both cases your device processes only your own microphone. No participant's client ever captures another participant's audio for these features, so nobody can transcribe you without your own client doing it.

Who receives what

Everyone that receives anything is listed here, including the services that only ever see a network address. An IP address is personal data, so leaving those out would be a convenient omission rather than an honest summary.

• Groq — transcribes the meeting and generates summaries and answers. Receives: short audio clips of your own microphone while the transcript is running, and the text of the transcript when a summary or a question is requested. Groq states that it does not retain data from inference requests by default, may keep troubleshooting and abuse logs for up to 30 days, and is not permitted to train models on the inputs or outputs. Only reached when you switch the feature on.
• Your browser's speech service — recognises speech for the live captions. Receives: audio from your own microphone while captions are running — unless your browser can recognise speech on the device, in which case nothing is sent at all. Governed by your browser vendor rather than by MSRX. In Chrome this is Google's speech service; Chrome 139 and later can run recognition on the device instead, and MSRX asks for that mode first. Only reached when you switch the feature on.
• PeerJS cloud — introduces two browsers to each other so they can connect directly. Receives: the random room identifier and the network addresses of the people connecting. no audio, video, chat or transcript passes through it. Governed by the PeerJS project rather than by MSRX.
• Google STUN — tells your browser how it appears from the public internet. Receives: your network address. nothing else, and no call content. Governed by Google rather than by MSRX.
• Vercel — serves this website. Receives: the ordinary request information any web server receives, including your network address. Governed by Vercel's own privacy policy.

Recording

A recording is made by your browser and saved to your own disk. It is never uploaded to MSRX.

When anyone starts recording, every other participant is shown a notice and a banner that stays up for as long as it runs, naming who is recording. The host can switch recording off for everybody else.

Whether you may lawfully record a conversation is a question about where you and the other participants are, not about this software. Several countries, and several US states, require the consent of every party. Getting that consent is the responsibility of the person who presses record.

What this website itself collects

No analytics, no advertising, no third-party trackers and no cookies for tracking. The site is served by Vercel, which receives the ordinary request information any web server receives.

The transcription endpoint counts requests per network address in memory, purely to stop one machine flooding it. The count is not written anywhere and disappears when the server instance recycles.

Your rights

If you are in the EU or UK, the GDPR gives you rights of access, correction, erasure, restriction, portability and objection. If you are in India, the Digital Personal Data Protection Act, 2023 gives you comparable rights, including the right to nominate someone to exercise them for you.

In practice there is very little for these rights to reach: with no account and no stored meeting data, MSRX holds nothing that identifies you. Write to mrinalsinghraja@gmail.com and we will tell you honestly what exists, which in almost every case is nothing.

The lawful basis for the optional AI features is your consent, given by switching them on, and you can withdraw it at any time by switching them off.

Where data goes

The services listed above operate outside India and the EEA, including in the United States. Using the optional AI features involves an international transfer of the audio and text described above.

Children

MSRX Meeting is not directed at children. You must be at least 13 to use it, and if the law where you live sets a higher age for consenting to online services on your own — several EU member states set 16 — you need your parent or guardian's permission below that age.

Complaints and contact

The data fiduciary for the purposes of India's Digital Personal Data Protection Act 2023 — and the data controller under the UK and EU GDPR — is Mrinal Singh Raja, an individual publishing under the name "MSRX". MSRX is a brand, not a registered company.

Questions, complaints and privacy requests all go to mrinalsinghraja@gmail.com, which also reaches the grievance contact for the purposes of India's Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021. We aim to acknowledge within 24 hours and resolve within 15 days.

If you are in the EU or UK you may also complain to your national data protection authority; if you are in India, to the Data Protection Board.

Changes

Material changes move the date at the top of this page. Because the site is built from a published source history, what changed and when is verifiable rather than merely asserted.