Informativa sulla privacy
Questa pagina è disponibile in inglese e in tedesco. Deutsche Fassung
This privacy policy applies to ROOMS: the website rooms.golem.de, the customer console at rooms.golem.de/app, and the ROOMS app in which meetings take place (at an address such as name.getrooms.app or a customer’s own address). Other services of 4Players GmbH are covered by the privacy policy on 4players.io.
1. At a glance
- ROOMS app: audio and video are relayed in real time and not recorded. We do not store chat histories on our servers. Rooms with a password are end-to-end encrypted for audio, chat, profiles, whiteboards, notes and (by default) files; video is not.
- AI transcription is off until someone with the corresponding permission starts it. Your microphone stays muted until you agree. Speech recognition runs in the EU.
- No tracking: the website, the console and the app use no analytics, advertising or tracking services and load no content from third parties.
- Who is responsible: 4Players GmbH is responsible for operating ROOMS, for the website and for your contract. The organisation that invited you is responsible for the content of a meeting (section 3).
2. Controller and data protection officer
4Players GmbH
Paul-Stritter-Weg 2
22297 Hamburg, Germany
Phone: +49 40 607742610
Email: datenschutz@4players.de
We have appointed a data protection officer. You can reach them at the address above, marked “Data Protection Officer”, or at datenschutz@4players.de.
3. Who is responsible for what
- The organisation that runs a ROOMS instance (our customer) decides who is invited and whether transcription may be used. It is the controller for the content of meetings – what is said, written, shared or transcribed. We process this data on its behalf under Art. 28 GDPR, based on a data processing agreement.
- 4Players GmbH is the controller for operating the service (connection data, security, abuse prevention), for the website and the console, and for our customers’ contract and billing data.
- Golem brokers ROOMS in the German-speaking region and is the first point of contact for questions there (section 6). The contracting party is always 4Players GmbH.
If you have questions about a specific meeting as a participant, for example about a transcript, please contact the organisation that invited you. We forward requests we receive to them.
4. The website rooms.golem.de
Server log files. When you visit the website, our web server processes technically necessary data: IP address, date and time, requested address, amount of data transferred, referrer and browser identifier. We use it to deliver the website and to detect attacks, and delete it after 10 days. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is operating the website securely.
Hosting. The website, the console and the ROOMS server run on servers in the EU: servers we rent from OVH and our own hardware in the WIIT data centre in Düsseldorf. Audio, video and chat run through media servers in the region the organisation chose when it set up its instance (section 7).
No cookies, no tracking. The website sets no cookies and uses no analytics or advertising services. Fonts and all other content are loaded from our own server.
Storage in your browser. When you choose a language or a colour scheme, the website saves that choice in your browser’s local storage (rooms-console.locale, rooms-theme). This information does not leave your device. It is strictly necessary for the function you asked for (§ 25(2) no. 2 TDDDG). You can delete it in your browser at any time.
Sign-up. When you enter your email address in the form on the home page, it is passed to the console, which sends you a sign-in code (section 5).
Contact by email. The contact address rooms@golem.de and the enterprise form (which prepares an email in your own mail program) lead to Golem (section 6).
5. Customer console, contract and payment
Sign-in. You sign in to the console with your email address and a one-time code that we send you by email. After you sign in, the console stores a session identifier in your browser’s local storage so that you stay signed in. It is deleted when you sign out.
Customer account and instances. We process the data of your customer account (name, email address, company, billing address, VAT ID), your ROOMS instances and their addresses, your plan, usage (for example transcription minutes), orders and invoices. The data is held in the customer system of 4Players GmbH on servers in the EU.
Payment. For payment we redirect you to our payment service provider Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland). You enter your payment details, billing address and VAT ID there. Stripe sends us the billing details and the payment status; we do not receive full card details. Stripe is itself responsible for parts of the processing (for example fraud prevention) and may transfer data to Stripe, Inc. in the USA, which is certified under the EU-US Data Privacy Framework. Details: stripe.com/privacy.
VAT ID check. We check a VAT ID you provide through the European Commission’s VAT Information Exchange System (VIES).
Emails. We send sign-in codes, order confirmations and invoices from our own mail servers; for delivery we use Mailjet (Sinch Mailjet SAS, France).
Legal bases and retention. We process this data to perform the contract with you (Art. 6(1)(b) GDPR) and to meet legal obligations (Art. 6(1)(c) GDPR). We keep contract and billing data for as long as commercial and tax law requires (up to ten years).
6. Brokerage and support by Golem
In the German-speaking region, ROOMS is brokered by Golem (Golem Media GmbH, Wilhelmine-Gemberg-Weg 5–7, 10179 Berlin, Germany). Golem presents ROOMS, advises prospective customers and is the first point of contact for support (rooms@golem.de). Golem forwards technical questions it cannot answer itself to us.
Golem acts on our behalf (Art. 28 GDPR), both for enquiries from prospective customers (for example through the enterprise form) and for support requests from customers. For communication with customers we use a shared mailbox in Microsoft 365. If you send us meeting content in a support request (for example participants’ names), Golem processes it as a sub-processor.
Customers usually order ROOMS themselves on this website. Only customers of an on-premise installation are set up by us on their instruction.
7. The ROOMS app
What the ROOMS app processes when you take part in a meeting – including as a guest without an account:
| Data | Purpose and how | Where and for how long |
|---|---|---|
| Display name, avatar, presence in a room | Shared live with the other participants; end-to-end encrypted in rooms with a password | Server: temporary participant records, deleted about 3 minutes after you leave. The avatar is stored only on your device. |
| Audio and video | Relayed in real time through media servers of 4Players GmbH (edge servers) in the region the organisation chose for its instance, and not recorded (for transcription, see section 9) | Not stored |
| Chat messages | Delivered through the media servers, end-to-end encrypted in rooms with a password. Our servers store no chat history. | Only on your device, if you turn this on in the settings (off, 7, 30 or 365 days; default: off) |
| Shared files and images | Uploaded; in rooms with a password encrypted in the browser by default (AES-256-GCM). File name, type and size are visible to the server. | In file storage (S3) at OVH in the EU, for as long as the uploader chooses: 1 hour after the room empties, 1 day, 1 week, or until the room is deleted |
| Whiteboards, notes, room documents | Stored so that they persist; encrypted in rooms with a password | Until the room is deleted |
| Member record (role, last visit) | So that returning users keep their role | 90 days after the last visit |
| Access proof for rooms with a password | The server stores only a hash of a key derived from the password, never the password | For as long as the room exists |
| Bans and moderation events (display name, user ID, room, moderator) | Moderation and abuse prevention | Bans until they expire; moderation events in server logs, 10 days |
| IP address | Needed for the connection. For rate limiting (abuse prevention) we use only a keyed hash. | In server logs, 10 days |
| Link previews | For the first link in a chat message, the ROOMS server fetches the page and creates a preview. This also happens in encrypted rooms; our server and the linked website see the address. | Not stored |
| Activity log (names, join and leave times) | Shown to participants and can be exported as an attendance list | Only on your device, 2 days |
Media region. The organisation that runs an instance chooses a gateway, and with it the region of the media servers, when it sets up the instance. If it chooses a region in the EU, your data is processed exclusively in the EU. If it chooses a region outside the EU, for example in the USA, audio, video and chat are relayed through servers in that region, but not stored there. In rooms with a password, audio, chat and profile data remain end-to-end encrypted; video is encrypted in transit (section 8). Transcription and all stored data stay in the EU in every case: the transcription service runs in the EU and connects to the media server from there.
Cookie and storage on your device. The ROOMS app sets one cookie: andorUUID, a signed session identifier (HttpOnly, Secure, valid for one year). In your browser it stores your settings (name, avatar, language, media), the passwords of rooms you have joined, the chat history (only if you turn it on), copies of your last three transcripts, the activity log of the last two days and an image cache. All of this is strictly necessary for the service you are using (§ 25(2) no. 2 TDDDG), which is why there is no cookie banner. The app uses no analytics, advertising or tracking services.
Legal bases. For the content of meetings we process data on behalf of the organisation that runs the instance; its legal basis is usually Art. 6(1)(b) or (f) GDPR. For secure operation and abuse prevention we rely on Art. 6(1)(f) GDPR.
8. End-to-end encryption
New rooms are created with a password by default. The password is part of the invite link after the # and is never sent to our server by your browser.
End-to-end encrypted in rooms with a password: audio, chat, profile data (names, avatars), whiteboards, notes and – by default – files. Only participants who have the password can read them.
Not end-to-end encrypted:
- Video. Like every connection it is protected in transit (TLS), but it is relayed without the room’s key.
- Metadata: file names, sizes and types, connection data, and who is in which room when.
- Addresses of links shown with a preview (section 7).
- Audio during a transcription: the transcription service receives a key for this (section 9).
- Rooms without a password, for example when a room is opened directly by its name or through a link without a password. They are not encrypted.
9. AI transcription
Participants with the “Start recording” permission can start an AI transcription in the main room (not in breakout rooms).
Your consent. Everyone in the room sees a notice saying who started the recording. Your microphone stays muted until you choose “I understand”; “Stay muted” is a real choice. Anyone who joins during a running recording sees the same notice. The person who starts the recording consents by starting it. The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by muting your microphone or leaving the room. Your name still appears in the join and leave entries while you are in the room – even if you stay muted.
What happens. A transcription service of 4Players GmbH (operated in Limburg an der Lahn, Germany) joins the room like a participant and receives each speaker’s audio separately. Short utterances are buffered in memory only and sent for speech recognition to our sub-processor OVH, on servers in the EU (Gravelines, France). Audio is not stored.
What is produced. The transcript contains what was said, with the speaker’s display name and the time, plus entries for when participants joined or left the room. We do not identify anyone by their voice and do not create AI summaries. Your speech and your transcripts are not transferred to OpenAI or any other provider outside the EU and are not used to train AI models.
Who sees the transcript. Everyone in the room, including people who join later (they receive the earlier part). Everyone in the room can download the transcript. Each device keeps copies of its last three transcripts.
How long it is kept. During the recording, the transcript is held in the transcription service’s database at Supabase in the EU (Ireland). We delete it there about 11 minutes after the recording ends; if deletion fails, we retry for up to a day. Downloaded transcripts and copies on participants’ devices are their own responsibility.
Encrypted rooms. To transcribe an end-to-end encrypted room, the transcription service receives a key that lets it decrypt the room’s audio for the duration of the recording. A new key is used when the recording starts and when it ends, so the service cannot listen before or after.
10. Recipients and transfers to third countries
We pass data only to service providers that we have selected carefully and bound by contract. Which ones ROOMS uses, for what and where, is shown in the list of sub-processors. We use media servers outside the EU only if the organisation has chosen such a region for its instance (section 7). Where a provider is based outside the EU (for example in the USA or Canada), we base the transfer on an adequacy decision of the European Commission (for the USA, the EU-US Data Privacy Framework) or on the Commission’s standard contractual clauses, even if the data is processed in a data centre in the EU.
11. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You have these rights as a guest in a meeting, too.
Right to object. Where we process data on the basis of Art. 6(1)(f) GDPR, you may object at any time on grounds relating to your particular situation (Art. 21 GDPR).
Withdrawing consent. You can withdraw consent at any time with effect for the future; for transcription, muting your microphone or leaving the room is enough.
Complaints. You can lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Hamburg Commissioner for Data Protection and Freedom of Information (Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit), Ludwig-Erhard-Straße 22, 20459 Hamburg, Germany.
For any data protection matter you can reach us at datenschutz@4players.de. If it concerns the content of a meeting, please contact the organisation that invited you first (section 3).
12. Obligation to provide data, no automated decisions
For the contract and the console we need your email address and your billing details. In the ROOMS app you do not need to use your real name; you can choose any display name. We make no automated decisions within the meaning of Art. 22 GDPR and do not create profiles.
13. Changes
We update this privacy policy when ROOMS or the law changes. The version published here applies; its date is shown at the top.