Privacy Policy

Last updated: 07.11.2026 · applies to the ab|takt app, the web app and this website. The German version (Datenschutzerklärung) is authoritative.

In short: you can view the example and record rehearsals without an account; the recordings then stay on your device. To transfer recordings and scores you need an account (18 and over, section 2 d). Recordings and scores reach us only if you choose this in the app; we store and process them in the EU. The recording itself goes to no AI service provider, only texts (such as the transcript of the remarks) and images of single score pages. Whoever records tells the choir beforehand and obtains its consent (section 4). No tracking, no advertising and only one cookie: the web app's strictly necessary sign-in cookie, so that you stay signed in on your browser (2 h). In a choir, only the conductors and administrators see who accepts or declines a date; we delete the replies on the day after the date and keep no statistics on them, except a count of acceptances per member, which only the conductor sees before a concert and which we delete after the concert (2 e4). No one but you sees whether you opened a message from your choir (2 e5). You only get notifications if you turn them on; they never contain the text of a message; we do not insert names of people, only the choir's name and a date's place appear as they were entered (2 h2). With Apple Watch we record movements of your conducting hand only if you allow it; they stay on your iPhone unless you provide them for research (2 n). You export and delete your data on our servers yourself in the app under Settings → Data on our servers; you can also write to us (section 5). The full text below is binding.

1. Controller

Peachnote GmbH, Büchnerstr. 7, 86161 Augsburg (Germany), represented by its managing director (see Imprint). In this policy "we".
Email: datenschutz@abtakt.com

We have not appointed a data protection officer because there is no legal obligation to do so.

2. What data we process and why

a) Installation

On its first contact with our server the app receives a random installation ID and a secret key; we also store the platform and app version. We use them to assign your uploads and results to you. If you are signed in in the app, we link the installation to your account (2 d). Where the app offers it, you can move the installation to another device with a one-time transfer code. The app shows the installation ID under Settings → About ab|takt. The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

b) Recordings and scores you upload

You can transfer only while signed in (2 d). A recording is transferred only if you chose this in the app ("Transfer rehearsals to your score automatically" or "Transfer to score"). With automatic transfer this can already happen during the recording. A score without a recording is transferred only if you choose "Prepare the score" or "Read the score" for it, or if you have turned on "Read scores automatically" in Settings (off by default). Then we transfer your own scores (PDF) as soon as you add or open them in the app, without a further tap, and read them as with "Read the score". This applies only on the device or in the browser where you turned it on; you can turn it off there at any time. With "Prepare the score" we create the pronunciation from it and, for recognised works, the meaning of the words; with "Read the score" we recognise title, composer, movements and voices so that you can add practice tracks for the right voices. "Prepare the score" also recognises the title, composer, movements and voices of the score. The result is a suggestion that you can change. We store the files and their details (for example file name, time, recording date, work) and the version and time of your choice as proof. With each upload we also store the account ID against whose monthly limit it counts (Terms 2). We analyse the uploads to create rehearsal notes (the conductor's remarks in the score, pronunciation, lyrics). The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

Recordings also contain the voices of other people (choir members, the conductor) and sometimes names mentioned in the rehearsal. We receive these data from the person who uploads the recording. We do not recognise anyone by their voice; no biometric data within the meaning of Art. 9 GDPR are created in the process. In a rehearsal, however, something personal may be said in passing, for example about a choir member's health; it may then appear in the transcript. We do not specifically analyse such information. The legal basis is the consent of these people (Art. 6(1)(a) GDPR) and, for special categories of personal data mentioned in passing, their explicit consent (Art. 9(2)(a) GDPR). The person recording obtains it beforehand (section 4).

c) Choir spaces

If you enter the invite code of a choir space we set up, we store that your installation belongs to it (Art. 6(1)(b) GDPR).

d) Account (18 and over; needed to transfer)

You can use the example and record on your device without an account. To transfer recordings or scores you need an account; it is only for people aged 18 and over. With the account we count the monthly limit (Terms 2) and show you your results on every device where you are signed in. You sign in with a code by email; where the app offers it, also with "Sign in with Apple" or "Sign in with Google". The app's sign-in page shows which ways are available. We process:

With "Sign in with Google" and "Sign in with Apple" in the web app, your browser takes you to the Google or Apple sign-in page only after your click; before that, the web app loads nothing from Google or Apple. Google and Apple process the sign-in to your Google account or Apple ID as separate controllers (section 3); they may use cookies on their own pages. We receive only the details above, never your password.

The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR); when you create the account you accept the Terms and confirm that you are 18 or over. The consents in 2 j–2 n are separate from this (2 i). Recordings and results still belong to the installation you transferred them from; through the link you see and manage them on every device where you are signed in to this account. Nobody else sees them, except what you share with your choir (2 e).

e) Choirs and sharing with the choir

With an account you can create a choir, invite members or join a choir. We process the choir's name, invites and, per membership, the display name, voice part and role, and since when and how (for example as founder or through an invitation) someone belongs to the choir. The roles are member, conductor (conducts the choir) and administrator (manages the choir); one person can be conductor and administrator at the same time. Whoever creates a choir manages it and chooses whether they also conduct it. Administrators invite members and conductors, assign and remove the conductor and administrator roles, change the choir's settings and can delete it. Conductors and administrators can enter members' voice parts; we store who entered a voice part (the member, a conductor or an administrator) and when. Under "My role" you can give up your own role as conductor or administrator; the last administrator cannot, and cannot leave the choir either, until someone else takes over. Conductors and administrators see members' display names, voice parts and roles, since when someone has belonged to the choir and who entered their voice part, never email addresses. Members see the choir's name, the conductors' display names and the number of members.

The conductor decides which remarks of an analysed rehearsal to share with the choir. Shared are the wording of the selected remarks, the conductor's audio excerpts and sung passages for them, and the score pages; never the whole recording. Only the members and conductors of that choir receive shared content. The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR); for choir members' voices in shared excerpts, their consent applies (Art. 6(1)(a) GDPR, section 4).

e2) Practice tracks

As a conductor you can upload practice tracks for a piece or sing them in the app, one track per voice. We store the audio files, the voice, length and tempo, the piece's title and composer, your name in the choir, and the version and time of your confirmation that you may share the recordings. The tracks belong to your account. If you share them with a choir, its members and conductors can listen to them in the app; they don't get a file to download. This can't fully stop someone from recording what they hear. Members hear only the marked track per voice; when they listen, we store only the usual technical details. If others sing on your recordings, ask them first. Legal basis: performance of the contract (Art. 6(1)(b) GDPR).

e3) Rehearsal plan, dates and programme

Where the app offers it, conductors keep their rehearsal plan in their account so that all their devices show it: weekly series and single dates with title, date, time, duration, time zone, place and kind of date (such as rehearsal or concert), exceptions (moved, cancelled), holidays and, per rehearsal, the programme with pieces (title, composer, movements), planned durations and short notes.

If a rehearsal plan belongs to a choir, its dates become the choir's dates. Conductors and administrators can also add single dates of the choir, in the calendar several at once, move and cancel them and change their place. For a choir date we store date, time, duration, time zone, title, kind, status (planned, moved, cancelled) and place. The place is free text up to 120 characters, optionally with a map link; we read the coordinates from the link. A place can be an address. Enter a private address only if the person who lives there agrees. If the place contains the address of a person who did not enter the date themselves, the legal basis is the choir's and our legitimate interest in organising rehearsals at that place (Art. 6(1)(f) GDPR); that person can object (section 6). We store who added a date, but show it to no one.

Only conductors send the programme of a rehearsal to the choir. Members see its items, for pieces the title, composer, movements and bars, but not the planned durations or the notes. We store who sent the programme, but show it to no one. All members of the choir see the dates with their place and the programme sent in the app and, if they turn it on, in notifications (2 h2). The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

e4) Accepting and declining dates

Where the app offers it, as a member you reply to a date of your choir: "I can come", "Not sure" (optionally with the day by which you will know, at the latest the day before) or "Cannot come" (optionally with a reason – private, work, holiday or other – and a note of up to 140 characters). We store your reply with its time and the way you gave it (for example the app or a notification). You can reply and change your reply until the date starts. For weekly rehearsals the choir usually asks only for declines: if you do not reply, you are planned in as "coming (without a reply)". Conductors and administrators can set a series or a date so that everyone is asked to reply. If a date is moved and you had said you are coming or were not sure, we ask you to confirm your reply.

The conductors and administrators of your choir see for each upcoming date ("Who is coming?"), by name and by voice part, who is coming, who is planned in without a reply, who is not sure, who cannot come, who has not yet confirmed a moved date and who has not replied yet, with the day by which someone will know, the reason and the note. Other members do not see your reply; a reminder tells them at most how many are coming. Conductors or administrators can enter a reply on your behalf, for example if you tell them in person that you cannot come, without a reason or note. The reply is then marked "entered by a conductor" or "entered by an administrator", without the person's name, and you can change it. Conductors and administrators can set automatic reminders for a series or a date and send a manual reminder for a date at most once a day.

We delete all replies, reasons, notes and know-by days at 4:00 am (local time of the date) on the day after the date; from then on, the conductors no longer see them either. We do not build attendance statistics from them.

Exception: before a concert. Before a concert, the conductor can turn on a count; administrators cannot. ab|takt then counts, for each member, how many of the last rehearsals before the concert (the conductor chooses 1 to 12) they accepted. For rehearsals where only declines are asked for, a missing reply counts as accepting. Only rehearsals after the count was turned on are counted. For these rehearsals the app shows all members that the conductor is counting acceptances before the concert. The conductor sees the numbers per member with display name and voice part. They count replies, not who was actually there. Other members and administrators do not see the numbers. We delete them at 4:00 am on the day after the concert, and your number also when you leave the choir or delete your account. If the conductor turns the count off, or the concert is cancelled or moved, the count ends and we delete the numbers.

There is deliberately no "ill" reason; please do not write anything about your health in the note. Whether and how you reply is up to you. The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

e5) Messages from conductors and administrators

Where the app offers it, conductors and administrators write messages to the members of their choir: a text of up to 2,000 characters, optionally referring to a date. We store the text, the sender's account ID and role (conductor or administrator), the time, the date referred to, the number of recipients and whether a confirmation is requested. Members see only the sender's role, not their name. The message goes to all members of the choir with an account who belong to it when it is sent. Someone who joins later sees a message while it is current: if it refers to a date, until the end of the day on which the date ends (local time of the date), otherwise for 30 days after it was sent; they get no notification about it.

We store whether and when you opened a message only in your account, so that your devices know what is new, and for the number on the app icon (2 h2). No one but you sees this; conductors and administrators do not learn who opened a message and get no count of it either.

If the sender asks for a confirmation, you see the button "Read, thanks". Only when you tap it yourself, in the app or in the notification, do the conductors and administrators of your choir see your display name, your voice part and the time of the confirmation, and, per voice part, how many of the recipients have confirmed; there is no list of who has not confirmed. Without such a request there is no confirmation. Whether you confirm is up to you.

The sender decides the text of a message. Senders should not write anything about the health or other very personal matters of individual members (section 4). The text stays in ab|takt; notifications never contain it. We delete a message with all read and confirmation marks 180 days after it was sent. The sender or an administrator can delete it earlier for everyone; if the sender deletes their account, we delete their messages too. The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

e6) Linking a recording to a date

Where the app offers it, you can link a rehearsal you recorded and transferred to a date of a choir you conduct or manage. The app suggests the dates of these choirs from the seven days before and after the recording, the one matching the recording time first; you make the link yourself. We store the link with your recording, together with the date's date, time, time zone, title, kind and place, so that it remains when the date itself is deleted after its period; as long as the date exists, we apply its changes. If you share remarks from a rehearsal with the choir (2 e), we store with the shared content the linked date or, without a link, the choir's date whose period includes the recording time (from one hour before the start to two hours after the end). We do not show it to members. Only you see the link itself; it makes the recording visible to no one. For the recording, sharing and the choir's consent, 2 b, 2 e and section 4 still apply. The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR).

f) Reports

If you report content, we process the report, the content concerned and your contact details if you give them. The legal basis is Art. 6(1)(c) GDPR in conjunction with Art. 16 of the Digital Services Act (DSA) and Art. 6(1)(f) GDPR; our legitimate interest is being able to remove illegal content.

f2) Feedback

If you send us feedback on a remark ("Remark not right?") or, where the app offers it, on the app ("Give feedback"), we store it with the time, language, platform and app version. For a remark, that is your choice, your optional note and which remark you mean (package, remark, bars and parts shown, where you saw it); for the app, your message, the page of the app on which you wrote it and, if you give it, your email address for our reply. Recordings and the text of the remarks are not part of it.

If your app already has an installation ID, we link the feedback to the installation and, if you are signed in, to your account, so that we can export and delete it with your data. Only our team sees feedback. We use it to find and fix errors and to improve ab|takt and, if you give an email address, to reply to you. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is an error-free service and answering your feedback.

g) Security and troubleshooting

Your IP address is processed on every connection to answer the request. Our server logs technical details of each request (for example time, function, result, app version) without content and without IP addresses. To protect against abuse (for example guessing codes) we briefly process pseudonymised details such as check values of the IP address or email address. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is a secure, working service. If you send us a diagnostic log from the app yourself, we use it only for your request.

h) Storage on your device

The app and the web app store on your device what the service needs (for example recordings, scores, your choices, the installation key and your sign-in); this is permitted without consent under Section 25(2) no. 2 TDDDG. After you sign in, the web app (abtakt.app) sets a single cookie, "__Host-abt_restore"; it is strictly necessary and therefore also permitted without consent under Section 25(2) no. 2 TDDDG. It contains the installation ID and a random identifier with which your browser keeps you signed in even when it deletes the site's other storage (Safari, for example, after seven days without a visit). It lasts at most 400 days, becomes invalid after 180 days without use and is removed when you sign out, delete the data in this browser or delete your account. We store only a check value of the identifier, never the identifier itself; "Sign out everywhere" in the account settings ends the sign-in on all devices and makes all these cookies useless. Apart from that we set no cookies and use no tracking and no advertising. If you use iCloud Keychain, Apple syncs the installation key to your other devices. On devices at our trade-fair stand your data are deleted from the device and the server after your visit, unless you take your result with you using a transfer code. Motion data from Apple Watch (2 n) are kept on the iPhone in a folder of their own that is excluded from iCloud backups, and on the watch only until they have been transferred. Reminders to start a recording are scheduled by the app on your device; nothing is sent to us, Apple or Google for this. Notifications about your rehearsals and your choir, including reminders to accept or decline a date, by contrast come from our server (2 h2). If you have turned notifications on, the app or the browser stores a device ID and the address at which the notification service reaches your device.

h2) Notifications and the number on the app icon (optional)

Where the app or the web app offers it, it lets you know when a rehearsal you sent for processing is ready or could not be processed completely. As a member of a choir, you can also be told when the conductor sends or changes a programme, a date you accepted or were not sure about is moved, you are asked to accept or decline, or a conductor or administrator writes a message. You turn each kind on and off separately under Settings → Notifications. The kinds about your choir are off until you turn them on. Your device or browser asks for your permission first.

When this is on, we store for that device:

So that no one gets the same notification twice, we keep which notifications a device has already received and to which members a reminder about a date has already been sent.

Notifications contain only short texts:

We never include the text of a message, titles of works, the wording of remarks or reasons and notes for declining. We do not insert names of people; only what is in the choir's name or in a date's place appears as it was entered. Requests to accept or decline and messages asking for a confirmation carry a signed code. It is valid only for you and that date or that message and lets you reply directly from the notification.

Between 9 pm and 8 am (your device's time) we send no notification; it comes at 8 am instead. We send reminders to accept or decline only between 9 am and 8 pm (local time of the date). If a notification cannot be delivered in time, it is dropped: about a ready rehearsal after 36 hours, about a date at the latest on the day after the date, about a message after 7 days or as soon as you have opened the message. We never send advertising as a notification.

Number on the app icon. Where your device supports it, the app icon shows how many messages from your choirs you have not opened yet. We calculate this number on our server from your read marks (2 e5) and send it with the notification about a message. Other notifications do not count.

To deliver a notification, we pass the text, the link into the app, internal IDs (choir, date or message), for dates the start time, place and map link, the number, the expiry time and, where applicable, the reply code to your device's notification service (section 3). In a browser the content is encrypted for the notification service; it sees only the address, the size and the expiry period. When the service reports that the device can no longer be reached, we delete the entry. You turn each kind off under Settings → Notifications, and all of them in the settings of your device or browser. ab|takt works the same without notifications; you then see what is new in the app.

The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR); notifications are a part of the service you turn on yourself. Storing the device ID and the address on your device is permitted under Section 25(2) no. 2 TDDDG.

i) Consents: what applies to all of them

For sections 2 j to 2 n we ask you separately each time. Every consent is optional and off by default. You need none of them for an account or to use ab|takt. You give them when you sign up, under Settings → Consents, for 2 m when you send a rehearsal, for 2 n under Settings → Apple Watch. We store level 1 of 2 n only on your device; its proof (version, time) goes with the note on a transferred rehearsal.

Each consent has a fixed text with a version. Each time you give or withdraw a consent, we store:

This is how we prove that you consented. The legal basis for this is Art. 6(1)(c) in conjunction with Art. 7(1) GDPR. You can see your consents under Settings → Consents; they are included in the export of your data (Settings → Data on our servers → "Export").

Email consents are available only with an account. You tell us which address to write to. If your sign-in has just shown that this mailbox is yours (a code sent to this address, or "Sign in with Google" with a Gmail address), the consent applies at once. Otherwise, for example after "Sign in with Apple" or for a different address, we first send you an email with a confirmation link; without a click we delete the address after two days. Every email contains a link that unsubscribes you from exactly that purpose with one click.

j) News by email (optional)

If you choose "News by email", we write to you at most once a month about what's new in ab|takt, for example new features. These emails contain no surveys, no invitations to conversations or studies and no advertising for others; sections 2 k and 2 l cover those. We process your email address and language. The legal basis is your consent (Art. 6(1)(a) GDPR).

k) Have a say in what ab|takt does next (optional)

If you choose "Have a say", we email you about two to four times a year. We ask how you find ab|takt, invite you to a short conversation, or offer you early access to new features. A conversation takes place only if you accept the invitation and pick a time; the invitation says how it takes place. We do not record conversations unless you separately agree beforehand.

We process your email address, language, your role (if you gave one), your answers and our notes from a conversation. We use answers and notes only to improve ab|takt and summarise them without your name. The legal basis is your consent (Art. 6(1)(a) GDPR).

l) Help shape research on choir rehearsals (optional)

If you choose "Help shape research on choir rehearsals", we invite you by email to studies on rehearsal practice in choirs. We carry them out together with academic partners in music-education research. We process your email address, language and, if you gave one, your role, so that we invite you only to suitable studies. The legal basis is your consent (Art. 6(1)(a) GDPR).

This consent does not yet enrol you in any study. Each study has its own information sheet and its own consent. The sheet gives all the details, including who is responsible for the study. You decide each time whether to take part. We do not pass your email address or other details to any partner in a study unless you separately consent to it.

m) Rehearsals for development (optional)

When you send a rehearsal, we ask whether we may also keep it. With "Rehearsals for development" we keep, listen to and analyse the following to improve ab|takt and develop new features:

This includes training our own recognition models with them. We do not keep score images for this. We do not assess individual singers and do not recognise anyone by their voice. Only our team has access.

Your choir's voices. Recordings contain the singers' voices and the conductor's speech. We keep a rehearsal only if the conductor has confirmed for this choir that all singers are informed and agree, and that all are 18 or over. Their data are covered by their consent, which the conductor obtains (Art. 6(1)(a) GDPR, see section 4). Anyone who no longer agrees tells the conductor or writes to datenschutz@abtakt.com with the choir and rehearsal date. We then delete the kept copies of those rehearsals.

The consent applies to your account, or to this installation if you have no account. The legal basis is your consent and that of the singers and the conductor (Art. 6(1)(a) GDPR).

n) Apple Watch: movements of the conducting hand (optional)

With the ab|takt app on Apple Watch you control the recording on your iPhone, mark places with a tap and see the rehearsal plan on your wrist. Marked places belong to the rehearsal like the recording. The watch or the iPhone only plays the reference pitch; nothing is stored apart from the moment it sounds in the recording.

Recording movements (level 1). Only if you allow "Record the movements of my conducting hand" does the watch record, during your recordings, the acceleration and rotation of the wrist you wear it on, with precise timestamps. We also store what you tell us: which wrist the watch is on, which hand you beat time with and whether you are right- or left-handed, how you conducted (if you say so), the model and system version of the watch and the iPhone, data on the time alignment between the watch and the recording, and which prompts the watch gave you. On the iPhone, the app works out from the movements in which passages you beat time; this describes the recording and is not a grade. For rehearsals you have set to record automatically, ab|takt asks the watch to record acceleration during the planned time even without the app being open (50 times per second); ab|takt keeps only the time in which the rehearsal was recorded and discards the rest. According to Apple, the watch itself keeps these values for up to three more days.

So that the watch can record during the rehearsal, ab|takt starts a workout session on it. We save nothing to the Health app and read no health data; we do not collect heart rate or location.

The data goes from the watch to your iPhone and is deleted on the watch as soon as it has arrived there. On the iPhone it is excluded from iCloud backups. It stays there until you delete it. Under Settings → Apple Watch you can view it, export it one by one or all at once (with your consent history) and delete it. When you transfer a rehearsal (2 b), a short note on the movements goes with it: that they were recorded, with which hand, for how long, how precise the time alignment is, how much of it was beating time and whether you provided it for research. You see this note with the rehearsal in the app and in the web app.

Providing for research (level 2). If you also choose "Provide for research" (account required), we transfer the motion data with the information above to ab|takt for every rehearsal you record with the watch, preferably over Wi-Fi. We keep it in the EU under a random research ID, not under your name or your account ID; only our server knows which account it belongs to, so that we can delete it. We study the data within this research area: conducting movements, their timing and how they relate to the choir's sound and to how rehearsals go, and tools that give conductors feedback. Only our team has access. We keep the sound of a rehearsal for this only if you have also given "Rehearsals for development" (2 m) for that rehearsal and the choir has agreed. Only summarised results that identify no one are published. Working with a research institution happens only after a separate, new consent.

Trying new features first (level 3). If you choose this, we note it on your account and unlock new features from this research for you earlier. You do not need to provide any data for this.

Recording with the watch. If your iPhone cannot be reached, you can, where the app offers it, record the rehearsal with the watch's microphone. This happens only when you choose "Record with the watch" on the watch, and only if you have confirmed beforehand that the choir knows. The recording then goes to your iPhone and is a recording like any other (2 b, section 4). When the iPhone is there, the watch microphone stays off.

We do not recognise anyone by their movements, draw no conclusions about health (such as a tremor) and do not grade your conducting. The watch records only your own movements; this does not concern the singers.

The legal basis is your consent (Art. 6(1)(a) GDPR), separately for each level. Each level is voluntary, off by default and has no effect on features or price. Without level 1 you can still use the watch to control the recording and to mark places. The consents are for people aged 18 and over.

There is no automated decision-making within the meaning of Art. 22 GDPR.

3. Recipients

We process the data in the EU; notification services may also deliver notifications from outside the EU (see below). Some of our providers belong to groups based in the USA, so access from the USA cannot be ruled out completely. The European Commission's adequacy decision on the EU-US Data Privacy Framework and, in addition, the EU Standard Contractual Clauses apply.

Google and Apple also process the sign-in data in the USA as separate controllers. For transfers there they rely, according to their own statements, on the European Commission's adequacy decision on the EU-US Data Privacy Framework, under which Google LLC and Apple Inc. are certified, and in addition on EU Standard Contractual Clauses. Details are in the privacy policies of Google and Apple. For notifications we transfer the data named in 2 h2 to Apple Inc. and Google LLC, also to the USA; the basis is the European Commission's adequacy decision on the EU-US Data Privacy Framework (Art. 45 GDPR), under which both are certified. Which service delivers a notification in a browser is decided by your browser's maker; its terms apply. That service may be located outside the EU, in particular in the USA; it receives the content of the notification only in encrypted form.

4. Important for conductors and administrators: inform your choir first

Recording a rehearsal also records other people's voices. Please tell your choir before recording that you are recording and why (rehearsal notes with ab|takt), obtain the members' consent and do not record if anyone objects. For this there is our text for the choir to read out, send, or print and have signed. Consent must be voluntary: anyone who does not consent must not be disadvantaged as a result, not even in a course or class. Do not record a rehearsal in which anyone under 18 is singing (Terms, section 6). Do not discuss personal matters, for example about health, while recording, or pause the recording for them. If you share excerpts with the choir, members also hear other people's voices: share only if the choir agrees, and check the preview. If rehearsals are also to be kept for development (2 m), ask the choir separately first. Confirm this in ab|takt only if all singers agree and are 18 or over; ab|takt gives you a text for the choir. Let us know if anyone withdraws their agreement. If you write a message to the choir as a conductor or administrator (2 e5) or enter a reply on a member's behalf (2 e4), do not write anything about the health or other very personal matters of individual members. All members read a message.

5. Retention

6. 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 to object to processing based on legitimate interests (Art. 21). You can withdraw consent at any time with effect for the future (Art. 7(3)), for recordings towards the conductor or us. You withdraw each consent in 2 j–2 n separately, under Settings → Consents or by email; email consents also through the link in every email, "Rehearsals for development" and "Provide for research" (2 n) also for single rehearsals. What happened before the withdrawal stays lawful. You withdraw a consent to a study as its information sheet says. Write to datenschutz@abtakt.com. You can also export and delete your data on our servers yourself: in the app under Settings → Data on our servers ("Export", "Delete all my data"). If you write to us without an account, give us the installation ID (Settings → About ab|takt) so that we can find your data. If you can be heard in a recording someone else uploaded, contact the conductor or us.

You can lodge a complaint with a data protection supervisory authority, for example the one for your place of residence (in Austria the Datenschutzbehörde) or the one responsible for us: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA).

7. Obligation to provide data

You do not have to upload anything or create an account. Without an account you can view the example and record on your device, but you cannot transfer anything, join a choir or share anything with one; without an upload we cannot analyse a recording. The consents in 2 j–2 n are optional; you can use ab|takt just the same without them. Without consent under 2 n the watch records no movements. Replies to dates, confirmations of messages and notifications are optional; without them you see dates and messages in the app.

8. Website

This website sets no cookies and uses no tracking. When you visit it, your IP address is processed only to deliver the pages (Art. 6(1)(f) GDPR).