Skip to content
Kordinert

Privacy

Privacy policy

Version 2026-10 · Last updated 29 October 2026

Kordinert is a tool for the choirs and singers who use it. This policy explains what personal data is processed, why and on what legal basis, how long it is kept, who it is shared with, and the rights you have. It is written to be read, not to cover us.

Who we are

Kordinert is provided by Birget AS, org. no. 933 189 775, Voksenhagen 17, 0770 Oslo, Norway. You can reach us at support@kordinert.no.

We have no data protection officer. Privacy enquiries go to the same address and are answered by us.

Who is responsible for what

Responsibility is split in two, and the split decides who you should contact.

Your choir is the data controller for what it registers about its members: the member list and membership history, attendance and responses to activities, leaves of absence, notes, dues, posts and messages. Birget AS is the processor for those and handles them only on the choir’s instruction, under the data processing agreement the choir accepted when it was created.

Birget AS is itself the controller for your platform account (sign-in and profile), for billing the choir’s subscription, for technical error logging and for usage statistics.

If your request concerns data the choir is responsible for, we may forward it to the choir’s owner and tell you that we have. We never delete a choir’s data on our own initiative.

What data is processed

Depending on how your choir uses Kordinert, we process:

  • Account data: name, email address, sign-in information and your chosen language.
  • Profile data you or the choir add: phone number, birth date, address, pronoun, avatar and optionally an emergency contact.
  • Membership history: voice group, status, admission, probation, leaves of absence, committees and roles in the choir.
  • Activity: responses to rehearsals and concerts, and recorded attendance.
  • Content: posts, comments, messages and files you share within the choir.
  • Cases you report to Support: what you write, the pictures you attach, which device and version of the app you used, and the answers we give you.
  • Dues: charges, invoices and payments recorded by the choir’s board.
  • Technical: push-notification tokens for the mobile app, which version of the mobile app runs on each installation you are signed in on and which model and system version it runs on, your calendar feed address, strictly necessary cookies and operational logs.
  • Use: the date you last used Kordinert, one for the web and one for the app. How much each feature is used is counted without being linked to you — see “Usage statistics”.

What we use the data for, and on what basis

A choir’s member data is processed on the choir’s legitimate interest in running itself — keeping the member list, planning rehearsals and productions, recording attendance, sending messages and managing dues (GDPR Article 6(1)(f)).

Your name, the voice part you sing and your profile photo are visible to the other members of the choir. That is part of being in a choir, and rests on the same basis.

When you open a post on the wall, the fact that you have read it is stored. The post’s author and those who moderate the wall can see it, and the read receipt is kept as long as the post exists and is deleted with your account. In a conversation, the other participants can see how far you have read. Nobody sees when you read.

Your contact details are visible to other members only if you have consented to it (Article 6(1)(a)). You can withdraw that consent at any time, and withdrawal does not affect the lawfulness of the processing before it.

Your platform account is processed to perform our agreement with you (Article 6(1)(b)). Billing and accounting are processed to meet a legal obligation (Article 6(1)(c), the Norwegian Bookkeeping Act). Error logging, security logs and the record of which versions of the app are in use are processed on the basis of our legitimate interest in a stable and secure service. Usage statistics are processed on the basis of our legitimate interest in knowing how Kordinert is used (Article 6(1)(f)).

What you report to Support is processed in order to answer you (Article 6(1)(b)) and to keep a record of what was reported and done (Article 6(1)(f)). Your choir sees neither that you have written to us nor what you wrote.

We do not use the data for marketing, we never sell it, and no decision about you is made automatically or by profiling.

Special categories of data

Membership of a church choir can reveal religious belief. Where it does, the processing rests on Article 9(2)(d), which allows a not-for-profit body with a religious aim to process data about its own members, and the data is not disclosed outside the choir without consent.

If you write health information into a leave request — illness, pregnancy, a family situation — it is processed on your explicit consent (Article 9(2)(a)). The reason text is deleted automatically six months after the leave ends, and it never travels in a notification.

Age

You must be at least 13 to have your own Kordinert account. If you are under 18, the choir records a guardian as your emergency contact. Children under 13 get no account: the choir registers them with a guardian as the contact person.

How long we keep data

The general rule is that data is kept for as long as you have an account and your choir uses the service. On top of that we delete automatically:

  • An unused account: we send a warning email after 24 months without a sign-in and delete the account three months later. Signing in during those three months stops the deletion on its own.
  • If you ask for a sign-in code with an email address that has no account, we send an email saying there is no account at that address. We use the address only for that, and delete it from the queue as soon as the email is sent. To send at most one an hour, we remember a non-readable code of the address for one hour. The basis is our legitimate interest in telling the person who asked for the code (Article 6(1)(f)).
  • Your emergency contact: removed when your last active membership in any choir ends.
  • Notes the choir’s leadership wrote about you: deleted 12 months after the membership ends.
  • The reason text in a leave of absence: deleted six months after the leave ends.
  • Notifications: archived 90 days after being read, and deleted 90 days after archiving. The send queue and digests are deleted 30 days after sending.
  • Import files containing member lists: deleted 30 days after the import completes or was last touched.
  • Push tokens from devices unseen for 90 days: deleted.
  • Which version of the mobile app you use, and on which model and system version — one entry for each installation of the app you have been signed in on: deleted 13 months after the installation was last in use.
  • The date you last used Kordinert, on the web and in the app: kept for as long as you have an account, and deleted with it. The counts of how much the features are used, and the figures we work out from them, say nothing about who used them, and are kept as statistics.
  • Rejected and withdrawn applications to join a choir: deleted six months after the decision.
  • Accounting material — invoices, payments and dues charges: kept for five years after the end of the financial year, as section 13 of the Norwegian Bookkeeping Act requires.
  • Requests for a quote you send us from the pricing page: deleted from the support mailbox 12 months after they arrive.
  • Content you report to us from the wall: the email carrying your reason and your address is deleted from the support mailbox 12 months after it arrives. The post or comment itself is not copied into the email. Support reads the post, or the comment together with the post it is under — nothing else of the wall — and can remove what does not belong there. Every read and every removal is recorded in the audit trail with a reason support gives, and the choir’s owner sees them.
  • Cases with Support: what you wrote, the answers you got and the pictures are deleted 12 months after the case is closed. A case you do not answer after it has been solved closes by itself after 30 days. If you delete your account, your cases are deleted with it.
  • Operational logs: 30 days. The sign-in log — who signed in when, and from which IP address: 90 days, because it is the log a question about a compromised account is answered from. Audit trails of who did what: five years, with the actor pseudonymised if the account is deleted.

The choir’s own records

Messages have no automatic deletion deadline in this version, and a choir’s history — who sang, when, in which voice group, with what attendance — is the choir’s own archive and is kept for as long as the choir exists. If you delete your account, that history remains under the label “Former member”, without your name or contact details. That is why we pseudonymise rather than delete: the records are the choir’s as much as they are yours.

Deleting your account

You delete your Kordinert account yourself, whether or not you are in a choir. Sign in at kordinert.no/konto and choose «Delete my account» under Privacy and account. In the Kordinert mobile app it is under More → Privacy and account or, if you are not in a choir, behind «Delete account» on the screen the app shows you. If you are in a choir, you also find it under Privacy in My profile on the web. We send an email confirmation, and the clock starts only once you open the link in it: the account is deleted 14 days later. If you change your mind, cancel the deletion in the same place at any point within those 14 days. If you are the only owner of a choir you have to hand ownership over first — otherwise the choir is left with no-one who can administer it.

When the deletion runs, your sign-in is removed, your name and contact details are overwritten, your avatar is deleted, notes about you are deleted and leave reasons are emptied. You leave every choir you are a member of, your roles end, and your name is also removed from notifications sitting with other people. Posts and attachments you made stay without your name, because they are part of the choir’s and the other participants’ own conversation. If you want a specific post gone, you can delete it yourself at any time. A message you had already removed is no longer part of the conversation — its text is deleted outright.

Some things remain: accounting material for five years because the Bookkeeping Act requires it, audit trails with you pseudonymised, and the choir’s pseudonymised history. This is stated in the answer you get.

Your rights

You have the right to access the data we hold about you, to have it corrected, to have it deleted, to have the processing restricted while a dispute is resolved, to object to processing based on legitimate interest, and to receive the data in a machine-readable format.

You can download a complete copy of your data yourself at kordinert.no/konto or under My profile — it spans every choir you belong to and includes your platform data. You edit your own profile, and the choir’s leadership can correct member data and history.

If you ask for restriction, the choir’s leadership sets a marker that hides you from the member overviews and stops notifications to and about you until the matter is settled.

Requests go to support@kordinert.no and are answered within one month. For a complex request we may extend by up to two further months, and we tell you within the first month if we do. You may complain to Datatilsynet (the Norwegian Data Protection Authority) at any time (https://www.datatilsynet.no/).

Where the data is stored and how it is secured

The database, the files and the sign-in are run by Supabase in Stockholm, Sweden. Personal data is stored in the EEA; Supabase is a US company, so our agreement with it rests on the EU Standard Contractual Clauses. One exception: the copy of a case with Support is held by GitHub in the USA — see “Who we share with”. Each choir is isolated with row-level security in the database: a query from one choir cannot reach another choir’s data, whatever the client asks for.

All traffic is encrypted. Internal access is limited to those who need it, and administrative actions are logged. Backups are taken daily and kept encrypted for at most 30 days — the backups are in Stockholm as well.

Backups are not rewritten. When we delete something it leaves the live database immediately and falls out of the backups as they rotate within 30 days. If we ever have to restore from a backup, the deletions are re-applied afterwards.

Your avatar is one exception we want to be plain about: it sits at a public address. The address cannot be guessed and the images cannot be listed, but anyone holding the link can open the picture without signing in. If you would rather not have that, do not upload an avatar, or remove the one you uploaded.

Who we share with

We use a small number of vendors for well-defined tasks. All of them have a data processing agreement with us, and transfers outside the EEA rest on the EU Standard Contractual Clauses.

  • Supabase (Stockholm, Sweden; the vendor is US-based) — the database, the files and the sign-in, and the storage of the backups. Supabase runs on the Amazon Web Services (AWS) data centre in Stockholm. Everything is stored in the EEA, and the agreement rests on the EU Standard Contractual Clauses.
  • Gigahost (Norway) — the servers that deliver Kordinert in the browser and the Kordinert API the browser and the mobile app use. Gigahost stores no personal data beyond operational logs, which are deleted each time the service that wrote them is redeployed; requests and responses pass through the servers in transit.
  • Fiken — invoicing and accounting for the choir’s subscription. Vipps MobilePay — recurring subscription payments when selected. Billing contact and necessary order information are shared; member dues are not included.
  • Sentry (EU region, Frankfurt) — error logging. Personal data is scrubbed before an event is sent, IP addresses are not stored, session replay is off, and events are deleted after 90 days. The vendor is US-based, so the agreement rests on the EU Standard Contractual Clauses.
  • Resend (USA) — outbound email: invitations, digests, dues invoices and word that something has happened in a case with Support. The mail from Support does not contain what was written in the case.
  • Expo (USA) — delivery of push notifications to the mobile app.
  • GitHub (USA) — the workspace of Support. What you and we write in a case is copied to a closed area at GitHub that only Support can open, so that we can read and answer from there. Pictures you attach are not copied. The copy is deleted with the case, but GitHub may keep a log of what it sent us for a few days afterwards, and email notifications GitHub has already sent to Support stay where they were sent. The agreement rests on the EU Standard Contractual Clauses.
  • Anthropic (USA) — AI-assisted import of production plans. The feature starts off for every choir: text a leader pastes is sent only once the choir itself has switched it on under Settings → AI assistance. Every call is recorded in the choir’s own log. Anthropic does not use the content to train models and deletes it within 30 days; content flagged for a breach of Anthropic’s usage policy may be kept for up to two years.

Maps from OpenStreetMap

When a leader picks the place for activities, a small map of it is shown. The map is loaded directly from the OpenStreetMap Foundation in the United Kingdom, so your browser sends its IP address and ordinary browser details there while the map is shown. The OpenStreetMap Foundation is not our processor but responsible in its own right for what it receives, and the United Kingdom is covered by an EU adequacy decision. The map appears only where a leader picks a place for activities (the activity form and the new-season wizard), and only when the place has a map position.

The address search in those same places goes through our server to the Photon search service run by komoot GmbH in Germany, which searches the same OpenStreetMap data. What is sent is the search text as typed (it may be an address), the choir’s country and the language the page is shown in — nothing that identifies you.

Postal places from Kartverket

When a Norwegian postal code is typed into Kordinert or comes with a member import, the postal place fills in by itself. Our server then looks the code up in the open address register of Kartverket, the Norwegian Mapping Authority. Only the four digits are sent — nothing that identifies you — and your browser asks no one but Kordinert. Kartverket is not our processor. Place data © Kartverket (CC BY 4.0).

Services you connect yourself

If you subscribe to your calendar in Google Calendar, Apple Calendar or another app, that app fetches the activities and stores them in your own account there. That is outside our control, and you govern it by removing the subscription or rotating your calendar address under My profile.

If you connect an AI tool such as Claude to Kordinert (the MCP connector), the tool can read what you yourself may see in the choir, and no more. The answers to your questions are sent to the tool and sit in your own account with its provider. That provider is not our processor: how long the answers are kept there, and whether they are used to train models, follow from your own agreement and your own settings with the provider. The choir does not switch the connector on or off; you do, and you remove it under My profile → Connected apps.

If you download the app, Apple or Google holds the customer relationship for the download. We receive no personal data from them beyond what you enter in the app yourself.

Usage statistics

We count how Kordinert is used, so that we know what to build, fix and follow up. We do the counting ourselves, in our own database: with no cookies, no analytics tools from anyone else, and nothing shared with anyone.

Features are counted without names. When someone answers an activity, sends a message, opens the scores or plays the rehearsal mixer, one is added to today’s figure for that feature, on the web, on iOS or on Android. Most of it is counted on the server when the action is saved. What happens only on the device, such as the app being opened or a score being played, the app or the browser sends as a count. A count holds only the feature, where it was used and on which day — not who, and not which choir.

Each account has a date for when it was last used, one for the web and one for the app. It is there so that we can count how many people use Kordinert, and Kordinert’s own staff read it only as figures. Your choir never sees the date.

Your choir’s leadership — whoever holds the owner role, and whoever may see members’ private details — sees a usage status worked out from that date and from when you last signed in: «Not started», «Used in the last 30 days» or «Not used for over 30 days». The status does not say when, nor what you did. It covers your use of Kordinert as a whole, not only for one choir. You see the same status yourself on My profile. The basis is the choir’s legitimate interest in following up its members (Article 6(1)(f)), and you cannot opt out of it.

For each installation of the app we also keep the model and system version of the phone or tablet, and whether it is a phone or a tablet. On the web, the browser and the operating system are counted per day, without being stored on your account. We also use the sign-in log to count sign-ins per day.

The basis is our legitimate interest in knowing how the service is used (Article 6(1)(f)). None of the figures is shown for one person or one choir. The counts, and the figures we work out from them, are statistics that say nothing about who you are, and they are kept. The date you last used Kordinert is kept for as long as you have an account, and is in the copy of your data you can download. The details of an installation are deleted 13 months after it was last in use, and the sign-in log after 90 days.

Cookies

Kordinert sets only cookies that are strictly necessary to deliver the service you asked for: sign-in, security and language choice. Cookies of that kind need no consent under the Norwegian Electronic Communications Act, which is why the site has no consent banner.

We use no marketing or tracking cookies, no third-party analytics and no tracking pixels. Our usage statistics use no cookies. The full list is in the cookie statement.

Changes to this policy

For material changes we give notice in the service and update the version number and date at the top. If we change something that affects what you agreed to, we ask you to accept again.