Draft: this text is still being reviewed by a lawyer.
DPIA template for Coretime
A data protection impact assessment (DPIA) maps the risks of a processing operation for the people concerned, and the measures that limit them. Your organisation is the controller and carries out the DPIA; Coretime is the processor and provides the information. This template is filled in with how Coretime works. What your organisation fills in itself is marked like this: to fill in. It is a translation of the Dutch template. Copy the text into your own DPIA form, or print this page.
Is a DPIA needed? Coretime's standard profile assumes it is. The data is about employees, and data protection authorities such as the Dutch Autoriteit Persoonsgegevens list the systematic monitoring of employees as processing that may require a DPIA. Coretime is built so that it does not monitor how individuals perform; this DPIA can establish that for your situation. To be reviewed by a lawyer.
0. About this DPIA
| Organisation | name of the organisation |
| Prepared by | name and role |
| Data protection officer | name, or: none appointed |
| Version and date | version, date |
| Works council | date of its advice or consent, and the outcome |
A. Description
1. Purpose of the processing
Teams improve their ceremonies (planning, daily, review, retrospective) and how they work together. After a ceremony everyone gives a rating anonymously; the team tracks impediments, actions, absence and working agreements; a coach suggests improvements from the team's results as a whole.
Coretime is not meant for, and not suited to, assessing individual employees: there is no rating, ranking or report per person.
Why your organisation uses Coretime: reason and purpose
2. People concerned
- Employees and contractors in the teams that use Coretime: which teams, how many people
- Scrum Masters, coaches, managers and admins: who
- Stakeholders who give feedback on a review without an account: yes or no
3. Personal data
| Data | With a name? | Standard retention |
|---|---|---|
| Account: name, work email address, language, teams, role and rights; sign-in details | Yes | As long as the account exists |
| That someone rated a ceremony (without the rating, without a time) | Yes | 3 years |
| Ratings of ceremonies | No | 5 years |
| Notes with ratings and on the retro board | Not by default | 3 years |
| Impediments and actions, with who raised them and who owns them | Yes | 3 years |
| Absence (only dates, never a reason) | Yes | 1 year |
| Answers to pulse checks | Not by default; with a name only where the profile allows it | 3 years; with a name 90 days |
| Coaching notes about a person (only for the author) | Yes | 1 year |
| Delivery data from Jira or Azure DevOps (sprints, work items, no descriptions) | Sometimes, where someone owns an item | 3 years |
| Optional: personal profile (persona), only for the person themselves | Yes | 12 months after the last time |
| Optional: features from meeting transcripts, names replaced | No | 2 years; the text itself at most 4 hours |
| Audit log and privacy requests | Yes | 7 years |
The Privacy page in Coretime shows the periods that apply to your organisation. Special categories of personal data are not processed on purpose; Coretime asks users to leave them out of notes.
4. Who sees what
- Team members: their team's results as a group, from 5 answers; their team's notes, impediments, actions and absence.
- Scrum Masters and coaches: the same for the teams they support, plus their own coaching notes.
- Managers: their teams' results as a group, from 5 answers, never per person.
- Admins: accounts, settings, privacy requests and the audit log; no ratings per person.
- Coretime: only settings and counts per organisation, never the people or the content.
Differences in your set-up: for example extra admins or managers
5. Parties
- Controller: name of the organisation
- Processor: Coretime, under the data processing agreement
- Coretime's sub-processors: see the list of sub-processors
- Connections your organisation chooses itself, under its own agreement: for example Microsoft 365, Slack, Jira, Azure DevOps, Google
6. Where the data is
Data stays in the EU: the database, the backups, the logs and the error tracking. Coretime uses an AI service only when it is hosted in the EU. Encrypted backups are overwritten after 14 days.
B. Lawfulness
7. Lawful basis
- Ratings of ceremonies are kept without a name and without a time, only for groups from 5 answers; Coretime treats them as not personal data. Review for your situation, also for small teams.
- Other team data: the organisation's legitimate interest (GDPR, article 6(1)(f)). Balancing test: the organisation's interest, the employees' interests, and why the measures below strike the balance
- Personal profile: taking part is the employee's own choice, and only they see the result. Review: consent is rarely free in an employment relationship.
- Analysis of meeting transcripts: lawful basis; only with the works council's consent.
8. Necessity and proportionality
How Coretime keeps the processing as small as it can:
- Ratings without a name and without a time; results only from 5 answers, and below 3 answers nothing is kept.
- Notes and pulse checks anonymous by default.
- No comparison between teams; each team against its own baseline.
- Absence without a reason.
- Optional features (personal profile, meeting transcripts, AI help) off by default.
- Retention periods Coretime applies by itself every night.
Are there less intrusive ways to reach the purpose? assessment
9. Rights of the people concerned
Everyone sees in Coretime what is recorded about them (Settings, What Coretime keeps about you), and asks there for a copy or for erasure. Admins handle requests on the Privacy page: search, export and erase, with recorded evidence, within 30 days. Ratings were never linked to anyone and so cannot be looked up either.
How your employees are informed: for example intranet, team meeting, email; date
10. Employee participation
Advice or consent of the works council: date and outcome. Coretime provides information for the works council for it.
C. Risks
| Risk for employees | How Coretime limits it | Remaining risk |
|---|---|---|
| Someone is assessed on their own ratings | Ratings without a name and a time; only group results from 5 answers | low, medium or high |
| Teams are ranked against each other | No rankings; each team against itself | |
| In a small team it is possible to guess who gave what | A minimum of 5 to show, nothing kept below 3; nobody sees who has not answered yet | |
| Sensitive information in notes or coaching notes | Notes anonymous by default; coaching notes only for the author, removed after 1 year | |
| Questions about the reason for absence | Coretime records only dates, never a reason | |
| Meeting transcripts are read | Off by default; names replaced; text erased after at most 4 hours; only with the works council's consent | |
| Access by unauthorised people | Organisations separated in the database, encrypted connections and backups, two-step sign-in, audit log | |
| Data outside the EU | Coretime and its sub-processors in the EU; connections only when your organisation chooses them | |
| Data used for another purpose, such as a performance review | Coretime shows nothing per person; beyond that, an agreement within your organisation | |
| AI training with employees' data | AI help off by default, only anonymous signals, no training |
D. Measures and decision
Your organisation's measures:
- Personal profile: on or off
- Analysis of meeting transcripts: on or off
- Agreement that results from Coretime are not used to assess employees: where it is recorded
- Admins and their tasks: who
- Employees informed on: date
- This DPIA reviewed again on: date, for example after a year or with a new feature
Decision: the processing goes ahead or not, on which conditions
Approved: name, role, date
Template, draft · date · not yet reviewed by a lawyer