CoretimeNederlands

Draft: this text is still being reviewed by a lawyer.

Data processing agreement

This data processing agreement belongs to the agreement between the customer and legal name, trading as Coretime, KvK KvK number, address (Coretime or the processor), for the use of the Coretime service. The customer is the controller. The customer accepts this agreement when it creates its organisation or takes out a subscription; an administrator can do so on the customer’s behalf. Terms have the meaning given in the General Data Protection Regulation (GDPR). This is a translation of the Dutch version; if the two differ, the Dutch version prevails.

1. Subject

  1. Coretime processes personal data on the customer’s behalf, only to provide the Coretime service as described in the agreement and the terms of service. Annex 1 describes the processing: its purpose, the types of data and the data subjects.
  2. This agreement applies for as long as Coretime processes personal data for the customer.

2. The customer’s instructions

  1. Coretime processes the personal data only on the customer’s documented instructions. The customer’s use of Coretime, and the settings administrators choose, count as such instructions.
  2. If Coretime believes an instruction infringes the GDPR, it tells the customer immediately.
  3. If Coretime is legally required to process data, for example by court order, it tells the customer in advance, unless the law forbids that.

3. The customer’s responsibility

The customer decides what Coretime is used for and ensures a valid legal basis. The customer informs its staff, obtains the works council’s consent where needed, and carries out a data protection impact assessment (DPIA) where needed. Coretime provides the information for this, among other places on the Your data page, on the Privacy page for admins, with a DPIA template and information for the works council, and in a technical annex on request.

4. Confidentiality

Coretime ensures that everyone who has access to the personal data on its behalf is bound to confidentiality.

5. Security

  1. Coretime takes appropriate technical and organisational measures to secure the personal data. Annex 2 describes them.
  2. Coretime may change the measures, as long as the level of security does not decrease.

6. Sub-processors

  1. The customer gives Coretime general authorisation to engage sub-processors. The current list is in Annex 3 and on the Sub-processors page.
  2. If Coretime wants to add or replace a sub-processor, it tells the customer’s administrators at least 30 days in advance. The customer can object on reasonable grounds within that period. If the parties cannot agree, the customer can end the agreement before the change takes effect.
  3. Coretime imposes the same obligations on every sub-processor as in this agreement, and remains responsible to the customer for its sub-processors.
  4. Connections the customer switches on itself, such as Jira, Azure DevOps, Slack, Microsoft 365, Google Calendar or an AI provider, are not sub-processors of Coretime. The customer chooses those services and has its own agreement with them; Coretime only exchanges data with them on the customer’s instructions.

7. Transfers outside the EU

Coretime processes the personal data in the European Economic Area. Transfers outside it happen only where the GDPR allows them, for example on the basis of an adequacy decision or standard contractual clauses. Annex 3 states where that is the case.

8. Data subjects’ rights

  1. Coretime contains tools with which the customer can handle data subjects’ requests itself: seeing what is recorded about someone, exporting, correcting and erasing, with recorded evidence of how a request was handled.
  2. If a request reaches Coretime, it forwards it to the customer. Where needed, Coretime helps the customer answer within the legal deadline.

9. Personal data breaches

  1. Coretime notifies the customer of a personal data breach without undue delay, and where possible within 48 hours of discovering it. That way the customer can notify the supervisory authority within 72 hours, where needed.
  2. The notification contains what is known at that moment: the nature of the breach, the data and people concerned, the likely consequences and the measures taken. Coretime supplements the notification as more becomes known.
  3. Notifying the supervisory authority and data subjects is the customer’s responsibility. Coretime helps with it.

10. Assistance

Coretime reasonably assists the customer with a DPIA and with a prior consultation of the supervisory authority, with the information it has.

11. Audits

  1. Coretime makes available to the customer the information needed to demonstrate that it complies with this agreement.
  2. If that information is insufficient, the customer may have an audit carried out once a year by an independent expert bound to confidentiality, after at least 30 days’ notice. The audit disrupts operations as little as possible. The costs are the customer’s, unless the audit shows a material shortcoming.

12. End of the processing

  1. During the agreement, administrators can download all data of their organisation at any time.
  2. After the agreement ends, or earlier at the customer’s request, Coretime deletes the personal data. Deletion takes place 30 days after the request, so that the customer can still change its mind. Encrypted backups are overwritten automatically after at most 14 days.
  3. After deletion, Coretime keeps only a record of it: the organisation’s name, the dates and the number of deleted records, and no personal data of staff.
  4. A legal retention obligation may postpone the deletion of certain data; Coretime then uses that data for nothing else.

13. Liability

The parties’ liability is governed by the terms of service.

14. Final provisions

Where this agreement conflicts with other arrangements, this agreement prevails as regards the processing of personal data. This agreement is governed by Dutch law.

Annex 1: the processing

Purpose. Providing Coretime: teams rate their ceremonies, run pulse checks, follow up retrospectives, impediments and actions, and look at trends, all with privacy as the starting point.

Data subjects. The customer’s employees and contractors who use Coretime or appear in it, and external participants the customer invites, such as stakeholders giving review feedback.

Types of data.

Special categories of personal data are not knowingly processed; Coretime asks users to leave them out.

Retention periods. As described in the privacy statement, section 4. Coretime applies them automatically.

Location. Data centres in the European Union: Germany, with backups also at a second Hetzner location in the EU.

Annex 2: security measures

Annex 3: sub-processors

Sub-processorWhatWhere
Hetzner Online GmbHHosting of servers, database and backupsGermany (EU); backups also at a second location in the EU
Scaleway SASSending email: invitations, sign-in links, noticesFrance (EU)
Scaleway SASAnswers for “Ask the coach” and the sprint report’s improvements with Coretime’s AI, only when an admin switches it on; the team’s question and anonymous signals and figuresFrance (EU)
Mistral AI SASAnswers for “Ask the coach” and the sprint report’s improvements with Coretime’s AI, only when an admin switches it on; the team’s question and anonymous signals and figuresEU
Mollie B.V.Payments; only data of the billing contactNetherlands (EU)

Version 1.0 · effective date