Privacy Policy

This is a translation provided for convenience. The authoritative version is the German one at Datenschutzerklärung.

This service gets by with very little data. That is deliberate and not an omission – what is not listed here is not collected either.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

Micha Bredemeier
Walwenstraße 4
32425 Minden
Germany
Email: [email protected]

No data protection officer has been appointed; the conditions of § 38 BDSG are not met.

2. What this website does not do

There is no reach measurement, no analysis of usage behaviour and no tracking. No third-party content is embedded – no external fonts, no maps, no videos, no social network buttons. There is no user account and no way to sign in.

Cookies

No cookie is set for recognition or for reach measurement. Exactly one cookie is set, and only while a Zoom account is being authorized: for ten minutes it remembers which authorization is currently in progress, and thereby prevents anyone from substituting someone else's. It contains a random string and the meeting ID, nothing else, and expires when the process completes. No consent is required for this cookie because it is strictly necessary for the service you explicitly requested (§ 25 (2) no. 2 TDDDG).

3. Providing the website

When these pages are opened, connection data is transmitted as a technical necessity, including your IP address, the time of the request, the address requested and details of browser and operating system. Without this the page could not be delivered to your device.

On the web server these requests are not logged; access logging is switched off. Only in the event of an error can technical messages arise that may contain an IP address. These are not evaluated. The volume of such messages is capped; once the cap is reached, the oldest entries are overwritten.

The legal basis is Art. 6 (1) (f) GDPR. The legitimate interest lies in the technical provision and security of the service.

4. Delivery via Cloudflare

This website is delivered through the network of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare handles the encrypted connection to your browser and protects the service against overload and attacks. In doing so, Cloudflare processes the connection data described in section 3 on my behalf.

A data processing agreement under Art. 28 GDPR is in place. Insofar as data is transferred to the USA in the process, the transfer is based on the European Commission's standard contractual clauses under Art. 46 (2) (c) GDPR. The legal basis for the processing is Art. 6 (1) (f) GDPR; the legitimate interest lies in operating the website securely and with little downtime.

5. Contacting me by email

If you write to me, I process your message and the information it contains solely in order to deal with your request. The legal basis is Art. 6 (1) (f) GDPR, or Art. 6 (1) (b) GDPR for contract-related enquiries. I delete the message once it has been dealt with and no statutory retention periods stand in the way.

Emails to [email protected] are forwarded via Cloudflare Email Routing to my personal mailbox at Posteo. What is said in section 4 applies here as well.

6. The display for raised hands

These pages offer an application that joins a Zoom meeting as an ordinary participant in order to show who has raised their hand. To do so it reads the meeting's participant list: display names, whether the microphone is open, and whether someone is host or co-host. It receives nothing more from Zoom – no video, no audio, no conversation content, no chat messages. This information stays in the browser of the display device and does not reach this service's server.

The application can also act within the meeting, provided it has been granted host or co-host rights: tapping a raised hand unmutes that person, and a button lowers all raised hands at once. Without those rights it is display only.

To make all this possible, the Zoom account that owns the meeting authorizes the application once.

What is stored in the process

On the server, only the following is stored per authorization:

• a randomly generated identifier for the authorization,
• the account and user identifiers of the authorizing Zoom account (technical strings from Zoom, not names),
• the numbers of the authorized meetings,
• the access keys issued by Zoom – a short-lived key for the individual request, a key for renewing it, and the expiry time of the first – encrypted together with AES‑256‑GCM,
• the time of authorization, the time of the last renewal and, where applicable, the time of expiry together with a short technical reason (such as „Zoom refused the renewal“).

What is not stored on the server

No name, no email address, no meeting passcode, no participant names, no conversation content. The application records neither video nor audio and makes no recordings. The email address of the authorizing account is shown once during authorization, so that it is clear which account granted it, and is not stored.

The names of participants that appear on the display device come directly from Zoom into that device's browser. They are neither transmitted to this service's server nor stored there, and they disappear as soon as the page is closed.

What stays on the display device

In the entry form, the checkbox Remember these details on this device is ticked by default. If it stays ticked, the browser stores the meeting ID, passcode and display name in its local storage. That is the purpose of the setting: next time the page is opened, the form is already filled in and one tap on Join is enough – nobody has to type the number again every time.

Up to four sets of entry details are kept, not just the last one. Where the same device is used for meetings of different Zoom accounts – which happens when several groups share one device – their meeting IDs and passcodes sit side by side on that device, and tapping one of the numbers fills the form with it. That is intended, because it is what the checkbox is for; anyone who does not want it unticks the box.

To keep that visible, the entry form lists every remembered number – even when there is only one. Each has a cross next to it that forgets it. The gear at the top right has Forget remembered details, which clears everything at once, including the pre-filled form. Anyone handing the device on can hand it on empty, without having to find anything in the browser settings.

On very flat windows – a phone held in landscape – the list is left out so that the join button stays visible. Forgetting is then in the gear at the top right, and only appears there when this device has remembered something.

This information does not leave the device and is not transmitted to this service's server. Anyone who does not want it stored there unticks the box; it can be removed by clearing the website data for meldungen.app in the browser settings. Also stored locally are a running speaking timer and the setting for whether the participant list is shown while idle.

Recipients

For authorization and for joining, data is exchanged with Zoom Communications, Inc., 55 Almaden Blvd, Suite 600, San Jose, CA 95113, USA. Zoom names Workvivo Limited, 4th Floor, City Quarter, Lapps Quay, Cork T12W832, Ireland, as its representative in the European Union. Which data Zoom itself processes is governed by Zoom's own provisions; I have no influence over that processing. There is no disclosure to any further third parties.

Legal basis and storage period

The legal basis is Art. 6 (1) (f) GDPR. The legitimate interest lies in being able to provide the authorized connection to the meeting without signing in again.

The information remains stored for as long as the authorization exists. If it is removed in Zoom, the information is deleted immediately (see section 7).

If an authorization goes unused for 90 days, it loses its validity through lapse of time. The access keys are deleted at that moment. What remains is only the meeting ID, the account identifier and the time – and that only because the display would otherwise report „this meeting is not authorized“ when in truth an authorization existed and merely expired. If you grant the authorization again, the same record is used in full once more.

7. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and the right to object to processing (Art. 21 GDPR). Please write to the address given above.

For erasure (Art. 17 GDPR) you do not need to write to me: remove meldungen.app in your Zoom account, and Zoom notifies this service automatically; everything stored for your account is deleted immediately. The steps are described in the guide.

Independently of this, you may lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The competent authority is the one for your place of residence, or the one responsible for me:

Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen
Postfach 20 04 44
40102 Düsseldorf
Germany
www.ldi.nrw.de

8. Changes

This policy applies to the service in its present scope. If the data processed changes, the policy will be adjusted beforehand.

Version: 9 October 2026