Privacy policy
This is a translation for your convenience. The German version is legally binding: Datenschutzerklärung.
This page explains what data hör.club processes, why and for how long. First the short version, then the details.
Short version: who hears what?
The demo stores your settings only on your device.
When you speak, your browser turns your speech into text – usually via an online service run by its maker, in Chrome that's Google.
Speech output uses pre-generated AI voices or your device's voice. Some device voices send the text to their maker.
If you join the waitlist, we store your email address and – if you give it – your city until you unsubscribe, for at most two years without renewal. We keep the record of your consent, including your IP address, for three years.
If you sign up with Google or ChatGPT, all we get from them is your confirmed email address.
Our server counts anonymously how often the demo is started and keeps shortened IP addresses for seven days.
Calls and shared rooms are end-to-end encrypted. We record nothing and keep the connection data only as long as the room exists.
Also: no cookies on the public pages and in the demo, no advertising, no third-party analytics.
Who is responsible?
The controller for data processing on hör.club is:
BAISE Systems (Einzelunternehmen)
Owner or authorised representative: Paul Lohrey
Mediapark 5, 50670 Köln, Deutschland
Email: p.l@mail.de
For questions about data protection and for your rights, simply write to this address. Other ways to reach us are in the legal notice.
The mailbox for this address is hosted by the email provider mail.de (Germany). So this provider also processes emails sent to this address, for example questions or unsubscribing by email.
Server and logs
hör.club runs on a rented server from Hostinger International Ltd. (Larnaca, Cyprus (EU)). The server is located in Frankfurt am Main, Germany (EU). Hostinger processes the data on our behalf under a data processing agreement (Art. 28 GDPR).
When you open a page, your browser sends technically necessary data to the server. The web server (nginx) keeps a log with:
- your IP address, shortened: for IPv4 without the last number, for IPv6 only the first 48 bits,
- date and time,
- the address you opened, without anything after the question mark,
- the status of the response,
- the name of the website you came from,
- your browser's identifier (user agent).
We delete this log after 7 days. We need it to run the server securely and to detect attacks. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR).
From this log we also create anonymous statistics with the program GoAccess, for example how often a page was opened. The statistics contain no IP addresses. We consider this additional purpose compatible with the original one (Art. 6(4) GDPR).
The internal web server (Caddy) keeps no access logs. For each request to its interface, our application writes an operations log: the time, which function was called (for example “waitlist”), the status of the response and how long the response took. If an error occurs, the type of error is added. The operations log contains no IP address and no content. Like the server log, we delete it after 7 days. The legal basis is Art. 6(1)(f) GDPR.
To prevent abuse, the server counts how often an IP address submits, for example, the waitlist form. These counters exist only in memory and disappear after 24 hours at the latest. For daily limits the server uses, instead of the IP address, a check value formed with a secret that changes every day. The legal basis is Art. 6(1)(f) GDPR.
Fonts and third-party content
All fonts (Atkinson Hyperlegible and Funnel Display), audio files and scripts are on our own server. When you open hör.club, your browser does not connect to Google or any other provider. We do not embed advertising, social media buttons or third-party analytics. We set no cookies on the public pages and in the demo.
Settings on your device
The demo remembers your settings in your browser's storage (localStorage, entry “hw_mobil3”). It stores: language, how you use it (voice or screen reader), voice, speech rate, read aloud on or off, colour scheme, light or dark, layout, style and colour of the orb, captions, suggestions, how far you got in the introduction, which tips you have already seen, whether you confirmed the note on voice input and your choice on the AI group search.
This data stays on your device. Only the language you set (German or English) is sent along with the anonymous statistics, see “Statistics without cookies”. The data contains no identifier that could recognise you. For automated tests there is also the entry “hw_test”; it contains no personal data either.
The legal basis is Section 25(2) no. 2 of the German TDDDG: storing is necessary so that the demo works the way you set it up.
You can delete the settings at any time in the demo under “Help”, then “Legal & contact”, then “Delete data on this device”. Or delete the website data in your browser settings.
Voice input
You can control the demo with your voice. Speech recognition is not done by hör.club but by your browser. It usually uses an online service run by its maker: Chrome sends the recording to Google, Edge to Microsoft, Safari to Apple. Safari sometimes recognises speech directly on the device. Firefox has no voice input, so there you type. The demo does not request recognition on the device. Whether your browser recognises speech on the device or online is up to the browser.
What is transmitted: the recording of your voice and the recognised text. The makers are mostly based in the US. To our knowledge, Google, Microsoft and Apple are certified under the EU-US Data Privacy Framework. The official Data Privacy Framework list shows the current status.
Before you speak for the first time, the demo explains this and asks you. Speech recognition only starts once you choose “Speak”. That is your consent (Art. 6(1)(a) GDPR). If you choose “I'd rather type”, nothing is recorded.
Because our page starts the speech recognition, we may be jointly responsible with the browser maker for this step (Art. 26 GDPR, CJEU judgment C-40/17). What the maker does with the data afterwards is explained in its privacy policy.
You can withdraw at any time: in the demo under “Help”, then “Legal & contact”, then “Who hears what?”, the button “Reset voice input notice” resets your choice. After that, the demo asks again before it listens. You can always type instead of speaking.
Speech output
Most of the concierge's sentences are ready-made audio files. We created them in advance with the AI speech synthesis Gemini TTS via the service kie.ai. Only the fixed demo sentences were sent, no user data. The audio files come from our own server.
New or free sentences are spoken by your device's voice. The demo prefers voices that run directly on your device. If there are none, it uses an online voice of the browser and tells you once beforehand. Online voices may send the text to be read to the browser maker.
The “Read aloud” button on pages like this one only uses voices that run on your device. If there are none, the button does not appear.
Group search in the demo
If you ask the demo for a matching group, it picks one of the sample groups directly in your browser. It does not send the text of your question to anyone for this.
Waitlist and emails
What data?
If you join the waitlist or sign up in the EarlyBird field on the home page, we store:
- your email address,
- your city or postcode, if you give it (the home page does not ask for it),
- the language of the page (German or English),
- whether you are open to a chat, only if you tick that box,
- the version of the consent text.
How you heard about hör.club, which campaign link you came from and how you signed up (waitlist page, home page, Google or ChatGPT), we only count anonymously per day. We do not store this information with your address.
Whether you used the demo before, we keep with your still unconfirmed entry only until you confirm, for 30 days at most. This lets us count anonymously how many confirmed sign-ups tried the demo first. We delete it as soon as you confirm, or after 30 days at the latest together with an unconfirmed entry. After that it only exists as an anonymous daily count.
We need your email address; without it, it does not work. The city is required on the waitlist page; the home page does not ask for it. Everything else is optional.
You can sign up if you are 16 or older – on the waitlist page and in the EarlyBird field on the home page.
On the home page, the short consent text appears right below the field as soon as you select the field or start typing. You consent by clicking the arrow “Sign up”; there is no box to tick there. On the waitlist page you tick a box instead.
What for?
You get an email when the beta opens for you. Until then we send you updates on the beta launch and project news, at most four emails a month. If you give your city, it helps us decide where the beta starts first.
Legal basis
Your consent (Art. 6(1)(a) GDPR). On the home page you give it by clicking the arrow “Sign up”, on the waitlist page by ticking the box. You can withdraw it at any time (see “Unsubscribing and withdrawing consent”).
The waitlist is open to everyone: blind and visually impaired people, relatives, professionals and anyone interested in hör.club. We do not ask about a disability, and a sign-up alone does not show whether you are blind or visually impaired. That is why we do not treat your sign-up as information about your health (a special category under Art. 9 GDPR) and do not ask for explicit consent under Art. 9 GDPR in the field on the home page.
The more detailed consent text on the waitlist page also covers, as a precaution, the possible indication that you are blind or visually impaired. For sign-ups via that page, your explicit consent under Art. 9(2)(a) GDPR therefore applies as well.
Confirmation by email (double opt-in)
After you submit the form, your sign-up briefly lands in an incoming queue. After processing we delete the entry there, normally within a few seconds, and after 24 hours at the latest if there is a disruption. Then we send you an email with a confirmation link. You are only on the list once you confirm via this link. The link is valid for seven days. If you sign up with Google or ChatGPT, there is no confirmation email, because the provider confirms your address (see “Signing up with Google or ChatGPT”).
So that nobody can flood an address with sign-ups, we send at most 3 confirmation emails to the same address within 24 hours. For this we form a check value from a standardised form of your address, using a secret key. The legal basis is our legitimate interest in preventing abuse (Art. 6(1)(f) GDPR).
To be able to prove your consent (Art. 7(1) GDPR), we record: time of sign-up and of confirmation, IP address, your browser's identifier (user agent), the address of the form, the version of the consent text and a checksum of that text. Instead of your email address, the record only contains a check value that we form with a secret key. The legal basis is our obligation to prove consent (Art. 6(1)(c) GDPR) and our legitimate interest (Art. 6(1)(f) GDPR).
Sending
We send the emails via Brevo (Sendinblue SAS), Paris, France; processing in the EU. The provider processes your email address and the content of the email on our behalf (Art. 28 GDPR). After sending, we immediately delete the address and content of the sending job on our side. We keep the time and status without the address for 7 days so that we stay within our sending limits. If an email cannot be sent even after several attempts, we keep the sending job with your address and the details for the email for at most 30 days, so that we can send it again after a disruption.
We do not measure whether you open an email or click a link. Our emails contain no tracking pixels, and all links lead directly to hör.club, without a detour via the provider.
How long?
- If you do not confirm, we delete your sign-up after 30 days, together with the record of this sign-up.
- If you confirm, you stay on the list until you unsubscribe – for at most 24 months after confirming or after our last email. 30 days before that, we ask you by email whether you want to stay. If you do not click, we delete your entry.
- We keep the record of your consent for 3 years after the last entry, even if you have unsubscribed. This lets us show that you had consented.
Unsubscribing and withdrawing consent
You can withdraw your consent at any time: via the “Unsubscribe” link in every email or by email to p.l@mail.de. We then immediately delete your entry and all emails to you that have not been sent yet. Anything done before the withdrawal remains lawful (Art. 7(3) GDPR).
Backups are overwritten after 8 weeks at the latest. A deletion journal makes sure that your address does not reappear after a restore from a backup. It only contains a check value of your address, formed with a secret key, and the time of deletion. We delete the entry in the deletion journal after 57 days at the latest. By then, all backups that could still contain your address have been overwritten.
Chat (optional)
If you tick that you are open to a chat, we may ask you by email whether you would like to talk about your experience – by phone or Zoom, about 20 minutes. This is a separate consent (Art. 6(1)(a) GDPR) that you can withdraw at any time. We delete the chat flag after 12 months. We only record a conversation if you explicitly agree beforehand. Zoom is a US service; we only use it if you choose Zoom.
Signing up with Google or ChatGPT
On the home page, the buttons “Continue with Google” and “Continue with ChatGPT” appear together with the consent text below the EarlyBird field, if they are set up. You can use them to sign up instead of typing your email address. As long as you do not click one of them, nothing goes to Google or OpenAI: the buttons are plain links, our page loads nothing from these providers and sets no cookies.
How does it work?
After your click, our server sends you to the sign-in page of Google or of OpenAI (ChatGPT). There you sign in and allow the provider to tell us your email address. Then you return to hör.club. Our server asks the provider directly over an encrypted connection and receives your email address together with the information whether the provider has confirmed it. We only request the permissions “openid” and “email” – no name, no picture and no contacts.
What data?
- At the provider: when its sign-in page opens, the provider receives the usual connection data of your browser, for example your IP address, and learns that you want to sign up for hör.club. What else it processes is set out in its privacy policy (Google, OpenAI).
- From the provider to us: your email address, whether it is confirmed, and technical details of the sign-in, for example an identifier of your account with the provider and how long the answer is valid. We only use the confirmed email address and discard the rest immediately.
- Stored by us: your email address on the waitlist – as with signing up by email, but confirmed right away –, the language and the version of the consent text. We do not store the provider's identifiers, names or access keys.
- During the sign-in, for at most 10 minutes and only in our server's memory: random values that secure the sign-in, plus the time, IP address, browser identifier and page address of your click.
- Record of consent: as for the waitlist (time, IP address, browser identifier, page address, version and checksum of the text), plus the route “Google” or “ChatGPT”.
In this case we do not send a confirmation email, because the provider has already confirmed your address. You can unsubscribe at any time, just like on the waitlist: via the link in every email or by emailing us.
Legal basis
Your consent (Art. 6(1)(a) GDPR), as when you sign up with your email address (see “Legal basis” for the waitlist). You give it by clicking “Continue with Google” or “Continue with ChatGPT” right at the consent text. You can withdraw it at any time (see “Unsubscribing and withdrawing consent”). How long we keep the data is set out under “How long?” for the waitlist.
Google and OpenAI
Google and OpenAI process the sign-in on their side under their own responsibility. For users in the EU this is, to our knowledge, Google Ireland Limited and OpenAI Ireland Limited; data may also go to the parent companies Google LLC and OpenAI in the USA. Because our page initiates the sign-in, we may be jointly responsible with the provider for this first step (Art. 26 GDPR).
Where data goes to the USA, the providers rely, to our knowledge, on the adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR) or on standard contractual clauses (Art. 46 GDPR). Whether a company is certified is shown in the official Data Privacy Framework list. If you do not want to give any data to these providers, simply sign up with your email address.
Statistics without cookies
To understand whether the demo is being used, our server counts some events anonymously per day. For example: demo started, introduction finished, first command (spoken, typed or via a suggestion), waitlist opened, sign-up submitted. Along with that we only count the language (German or English) and the campaign from the link, for example “dbsv” for hör.club/dbsv.
The demo takes the language from your settings stored on your device and sends it along: only “de” or “en”, without any identifier. The legal basis for reading it is Section 25(2) no. 2 of the German TDDDG.
For technical errors we count the type of error and the place in the program, without content. If your browser reports a violation of our security rules (Content Security Policy), we only count the rule and the name of the blocked server.
These counters contain no IP address, no identifier and no cookies. They cannot be used to trace who did what. We keep them for 25 months. The legal basis is our legitimate interest in improving the demo (Art. 6(1)(f) GDPR).
Calls and shared rooms
With hör.club you can call another person or enter a shared room with up to six people. People are invited only by a link or a six-digit code that you pass on yourself. There are no public rooms with strangers.
What data?
- Your voice. It travels end-to-end encrypted from device to device (WebRTC with DTLS-SRTP). We cannot listen in and we record nothing.
- Technical connection data so the devices can find each other: IP addresses and ports of the devices involved, details about audio format and encryption (key fingerprints). Our server passes them on to the other side (signalling).
- In the memory of our server, as long as the room exists: a random room identifier, the code, random identifiers of the participants, an optional display name, the shared state of the room (for example which audiobook is playing and where) and signalling messages not yet collected.
- Messages between the devices in the room, for example your position and facing direction in the room. They go directly from device to device or encrypted via our media server.
You share the invitation link yourself, for example via a messenger. The part after the “#” is not sent to our server when the link is opened.
How does the connection work?
If possible, the devices connect directly. The other side then sees your IP address, as with any internet call. If that does not work, the encrypted connection runs via our relay server (TURN) in Frankfurt am Main, Germany (EU). It only forwards encrypted packets and cannot decrypt them.
Shared rooms can run via our media server (LiveKit) in Frankfurt am Main, Germany (EU). The audio is still end-to-end encrypted: the key is only in the invitation link after the “#” and never reaches our server. Anyone who joins with the code receives the key directly from a device in the room over an encrypted connection. If that fails, there is no audio, and hör.club tells you so.
Our servers record nothing and store no conversation content. The relay server and the media server do not keep logs with IP addresses. Requests to the signalling appear in shortened form in the web server log like any page request (see “Server and logs”), without room identifier and without key.
Microphone
hör.club only switches the microphone on once you agree to the call or room and your browser allows it. You can mute at any time. Without the microphone you can still listen in a room. Speech recognition for commands is separate (see “Voice input”).
Legal basis
We process this data because you want to use calls and rooms (Art. 6(1)(b) GDPR) and for secure operation, for example abuse protection (Art. 6(1)(f) GDPR). Access to the microphone and to data in your browser is strictly necessary for the feature (Section 25(2) no. 2 TDDDG).
How long?
Everything stays in memory only, as long as the room exists. A call ends when you hang up. An empty room expires after 10 minutes, every room after 12 hours at the latest. Signalling messages not yet collected are deleted after 60 seconds at most. Relay credentials are valid for one hour. A server restart deletes everything immediately.
Good to know
The other people in the room can hear you. We cannot technically prevent someone from secretly recording. Only share links and codes with people you want to invite.
Whoever creates a room is its host. The host can mute people or ask them to leave and create a new invitation link; the old one then stops working. Who is muted or was asked to leave is kept by our server only as a random identifier in memory, as long as the room exists. If you whisper to someone, your voice technically goes only to that person.
Watch, rings and other companion devices
Watch as a remote: if you pair a watch or a second device, it sends your gestures via our server to your phone. Your phone sends menu entries, vibration patterns and short texts back. The server only forwards this, keeps it in memory for a few seconds at most and stores nothing. The pairing secret is stored only on your two devices (in the browser's storage); during pairing it passes our server once, encrypted, without being stored. Unpairing deletes it on both devices.
Rings and buttons that act as a Bluetooth keyboard, mouse or media key are handled only by your device. Nothing is sent to us.
If you use hör.club in the Even Realities app (G2 glasses, R1 ring), short display texts such as the selected menu item go to the glasses via the manufacturer's app. Even Realities' privacy policy applies to that.
The legal basis is Art. 6(1)(b) GDPR; storing on your devices is strictly necessary for pairing (Section 25(2) no. 2 TDDDG).
Motion sensors and controllers
For your facing direction in rooms, hör.club can use your device's motion sensor (gyroscope) if you switch this on and your browser allows it. The page can also read gamepads and controllers. This data is processed only on your device; it is not sent to our server and not stored. In a shared room your device only sends your position and facing direction in the room to the other devices (see “Calls and shared rooms”). The legal basis for reading the sensors is Section 25(2) no. 2 TDDDG.
Who receives data?
The table shows every place where data arises: what, what for, with whom, on which legal basis and for how long. Articles without a named law refer to the GDPR.
| What | Which data | What for | Who and where | Legal basis | How long |
|---|---|---|---|---|---|
| Web server log (nginx) | shortened IP address, address without additions, time, status, referring website, browser identifier | operation, security, anonymous statistics | Hostinger International Ltd., server in Frankfurt am Main, Germany (EU), processor | Art. 6(1)(f) | 7 days |
| Application operations log | per request: time, function called, status, duration, for errors the type of error; no IP address, no content. The internal web server (Caddy) keeps no access logs. | operation | our server | Art. 6(1)(f) | 7 days |
| Abuse protection | IP address and time; for daily limits only a check value that changes daily | protection against abuse | our server, in memory only | Art. 6(1)(f) | at most 24 hours |
| Limit on confirmation emails | check value from the standardised email address, time of the confirmation emails | protection against mass sign-ups, at most 3 confirmation emails in 24 hours | our server | Art. 6(1)(f) | 24 hours |
| Demo settings | settings in localStorage (“hw_mobil3”) | running the demo | your device only | Section 25(2) no. 2 TDDDG | until you delete them |
| Fonts, audio files, scripts | no additional data; the request is in the web server log | delivering the page | our server | – | – |
| Voice input | recording of your voice, recognised text | voice control | maker of your browser, mostly US | Art. 6(1)(a) | according to the maker |
| Device voice | text to be read | reading aloud | your device; for online voices the browser maker | – | – |
| Waitlist | email address, city or postcode (if given), language, chat flag, version of the consent text | email when the beta starts, news | our server | Art. 6(1)(a); via the waitlist page also Art. 9(2)(a) | unconfirmed 30 days; otherwise until you unsubscribe, at most 24 months without renewal |
| Incoming queue | form data, IP address, browser identifier, address of the form | processing the sign-up | our server | Art. 6(1)(a) and (f) | normally a few seconds, up to 24 hours if there is a disruption |
| Record of consent | check value instead of email address, time, IP address, browser identifier, address of the form, version and checksum of the text; for sign-ups with Google or ChatGPT the route | proof of consent | our server | Art. 6(1)(c) and (f) | 3 years after the last entry |
| Signing up with Google or ChatGPT (only after your click) | at the provider: connection data and your sign-in there; to us: email address with confirmation and technical details that we discard immediately | sign-up with a confirmed address | Google Ireland Limited or OpenAI Ireland Limited under their own responsibility, data may go to the USA | Art. 6(1)(a) | at the provider as set out in its privacy policy; with us as for the waitlist |
| Ongoing sign-in with Google or ChatGPT | random values, time, IP address, browser identifier and page address of your click | completing the sign-in, proving consent | our server, memory only | Art. 6(1)(a), (c) and (f) | at most 10 minutes |
| Sending emails | email address, content of the email | confirmation and info emails | Brevo (Sendinblue SAS), Paris, France; processing in the EU, processor | Art. 6(1)(a) | at the provider as set out in the data processing agreement; on our side sending data without address 7 days, failed sending jobs with address at most 30 days |
| Emails to our contact address | your email address, content of your email | questions, unsubscribing by email, your rights | mail.de (Germany), mailbox of our contact address | Art. 6(1)(c) and (f) | until your request has been dealt with |
| Event counters | event, language, campaign, type of error | statistics | our server | Art. 6(1)(f); reading the language on your device: Section 25(2) no. 2 TDDDG | 25 months |
| Backups on the server | copy of the database, compressed, not encrypted | restoring data | our server | Art. 6(1)(c) and (f) | daily 14 days, weekly 8 weeks; before updates the last 3, at most 14 days |
| Deletion journal | check value of the deleted address (formed with a secret key), time of deletion | deleting removed addresses again after a restore | our server | Art. 6(1)(c) with Art. 17 | at most 57 days (backups at most 8 weeks) |
| Signalling for calls and rooms | room identifier, code, random participant identifiers, optional display name, connection data (IP addresses, ports, key fingerprints), shared room state | setting up the connection | our server, memory only | Art. 6(1)(b) and (f) | as long as the room exists (call until hang-up, empty room 10 minutes, at most 12 hours); pending messages at most 60 seconds |
| Relay server (TURN) | IP address and port, encrypted audio packets (unreadable for us), short-lived credentials | connection when a direct one fails | our server in Frankfurt am Main, Germany (EU), no log | Art. 6(1)(b) and (f) | only during the connection; credentials 1 hour |
| Media server for rooms (LiveKit) | IP address, random identifier, optional display name, end-to-end encrypted audio and encrypted messages | shared rooms | our server in Frankfurt am Main, Germany (EU), no log with IP addresses | Art. 6(1)(b) and (f) | only during the connection |
| Other people in the call or room | your voice, optional display name, position in the room; with a direct connection your IP address | conversation | devices of the people you invite | Art. 6(1)(b) | their responsibility |
| Watch or second device as a remote | gestures, menu entries, vibration patterns, short texts; the pairing secret only on your devices | remote control | our server only forwards (memory, a few seconds at most) | Art. 6(1)(b); storing on the device: Section 25(2) no. 2 TDDDG | until you unpair |
| Motion sensor, controllers, rings | position and rotation of the device, buttons | operation, facing direction | your device only | Section 25(2) no. 2 TDDDG | not stored |
Receive no data about you: kie.ai (creating the fixed demo voices before launch) and Let's Encrypt (certificate for the encrypted connection).
Countries outside the EU
In these cases data may go to a country outside the EU and the European Economic Area:
- Voice input: to the maker of your browser, mostly in the US (see “Voice input”).
- Online voices of your browser, if your device has no voice of its own (see “Speech output”).
- A chat via Zoom, only if you choose it.
- Signing up with Google or ChatGPT, only if you click one of these buttons (see “Signing up with Google or ChatGPT”).
Calls and shared rooms run via our server in Frankfurt am Main, Germany (EU); data only goes to the devices of the people you invite – we do not know where they are.
Where our processors for server, email sending and backups process the data is shown in the table above.
How long do we keep data?
- Server log and application operations log: 7 days.
- Abuse protection counters: at most 24 hours, in memory only.
- Check value for the limit on confirmation emails: 24 hours.
- Incoming queue: normally a few seconds, up to 24 hours if there is a disruption.
- Ongoing sign-in with Google or ChatGPT: at most 10 minutes, memory only.
- Waitlist: unconfirmed 30 days after the last confirmation email; confirmed until you unsubscribe, at most 24 months without renewal.
- Sending jobs: after sending, without address 7 days; failed, with address at most 30 days.
- Record of consent: 3 years after the last entry.
- Anonymous event counters: 25 months.
- Backups on the server: at most 8 weeks.
- Deletion journal: at most 57 days.
- Calls and shared rooms: in memory only, as long as the room exists (call until hang-up, empty room 10 minutes, at most 12 hours).
- Remote control (watch, second device): nothing stored; the pairing secret on your devices until you unpair.
- Settings on your device: until you delete them.
Your rights
You have the right to:
- access your data (Art. 15 GDPR),
- rectification (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- object to processing based on our legitimate interest (Art. 21 GDPR),
- withdraw consent with effect for the future (Art. 7(3) GDPR).
Simply write to p.l@mail.de. So that we do not give data to the wrong person, please write from the address concerned.
You can also lodge a complaint with a data protection supervisory authority. The authority responsible for us is: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf.
Automated decisions
We make no automated decisions about you that have legal effects or affect you in a similarly significant way (Art. 22 GDPR). If the demo suggests a group to you, it is only a suggestion.
Security
- The connection to hör.club is always encrypted (HTTPS with HSTS).
- Calls and shared rooms are end-to-end encrypted (DTLS-SRTP; in rooms via the media server additionally with a key that is only in the invitation link).
- We store confirmation and unsubscribe links only as a checksum, never in plain text.
- Backups on our server are compressed but not encrypted.
- Only the operator has access to the server and the data.
Changes
If hör.club changes, we update this policy. The version on this page applies. Last updated: .