Skip to main content

DPIA starter for a TriageFit rollout

This is an outline your data protection officer can start from if your organisation decides to carry out a data protection impact assessment before rolling out TriageFit seats. We have filled in the parts that are facts about the software, each drawn from the data flows and data processing agreement pages, and left the judgements to you.

We are not your lawyers and this is not legal advice. Whether a DPIA is required, how you score each risk and whether what remains is acceptable are decisions for your organisation and its DPO. The one place where we offer a reading of the law rather than a fact about the software is marked as our reading.

1. The processing, in one paragraph

Your organisation buys a pack of seats and invites people to them by work email. If you verify your organisation's work-email domain, a person with an address there can also ask for a seat themselves, and we send the invitation to that address as if you had. Each person who accepts opens a TriageFit account of their own. Your administrators see a roster and aggregate reports. TriageFit is your processor for the roster and an independent controller of everything a member does inside the service.

2. Roles

  • Your organisation is the controller of the roster data, and TriageFit processes it on your documented instructions under the data processing agreement.
  • TriageFit is the controller of member data: intake, training, nutrition, check-ins, messages and any health data a member shares. It holds that data under its own privacy policy, and health data is processed only with the member's explicit consent.
  • Each member exercises their data-protection rights over their own data directly with TriageFit, from inside their account.

3. What your organisation processes

Your organisation processes the roster and nothing else about a person.

  • For each person you invite: their work email address, the role you give them and whether you fund the seat
  • The work-email domains you verify, which name your organisation and nobody in it. A person who asks for a seat through one is recorded as an invitation to their own address, as a member on a seat you fund
  • Optionally, four workforce labels in your own words: department, site or region, employment type and tenure band
  • Generated by TriageFit: each invitation's state including whether it was redeemed, each seat's state and the associated dates
  • For a person who has accepted: the name on their own TriageFit account, which they set and may change
  • Your organisation's name and billing details

The invitation form holds no other field. Special categories of personal data are not part of the roster.

4. Why your organisation holds no health data

No organisation role can see an individual's training, food, messages, check-ins or any other health data, through any screen. A billing administrator cannot open a health report at all. What reaches you is the roster and aggregate reports, and each person is told at redemption exactly what their employer can see. Clause 3 of the DPA states the same boundary as a contract term: your organisation is not a controller of member data and does not receive it. Your DPIA can record it as a design fact and a contract term.

5. Necessity and proportionality

  • Minimisation. Work email, role and funding status are what seat administration needs. The four workforce labels are optional and each can be left blank.
  • Purpose. Sending invitations, tracking redemption and seat state, showing the roster to your administrators, producing aggregate participation and progress reports, and billing the pack.
  • Reporting floor. A figure is released only when at least five distinct members contributed to it, for every grouping. Below that floor the report shows no number at all.
  • Subtraction. The report also withholds a second group where needed, so that subtracting published figures from a published total never describes a group of fewer than five people.
  • Members' choice. A seat is taken only when the person accepts it from the link sent to their own address. That holds for a seat asked for through your work-email domain too: an invitation left unaccepted for 48 hours returns its seat to the pack, and removing the domain withdraws every one still waiting. A member whose funded seat ends keeps their account and their rights over their own data.

6. Risks and the controls already in place

Score likelihood and severity yourselves. These are the risks we expect a reviewer to raise and what the software does about each.

An administrator infers a person's health from a small group

The five-person floor and the subtraction rule above apply to every report. Changes to the workforce labels are recorded, so a change to the groups can be traced to who made it.

An administrator reaches an individual's records

Each account can reach only its own data. Staff access to special-category health records is limited and recorded.

Roster data stays after the contract ends

Retention is set out in section 8.

A sub-processor is outside the EU

Section 7 lists where each service runs. Where a listed service processes personal data outside the European Economic Area, the DPA commits TriageFit to a valid transfer mechanism under Chapter V GDPR before the processing occurs.

A breach affecting the roster

TriageFit notifies you without undue delay after becoming aware of a personal data breach affecting roster data, under clause 10 of the DPA.

7. Sub-processors and where they run

The service and database run in Frankfurt, member uploads are stored under EU jurisdiction, and AI processing runs in EU regions only. Invitations go out by email. Every sub-processor engaged today is below, with where it runs.

  • Google Cloud (Vertex AI). EU only.
  • Neon. EU (Frankfurt).
  • Vercel. EU (Frankfurt).
  • Stripe. Global provider.
  • Resend. Global provider.
  • Upstash. EU (Frankfurt).
  • Sentry. EU (Germany).
  • Cloudflare R2. EU jurisdiction.
  • Google (Google Analytics 4 and Search Console). Global provider.
  • Browser push services (Google, Mozilla, Apple and Microsoft). Set by the member's browser.
  • Phone push services (Apple and Google). Set by the member's phone.

The sub-processor page gives what each one does. TriageFit emails your billing contact before a new sub-processor processes roster data.

8. Retention

When the agreement ends, TriageFit deletes or returns the roster data at your written choice. If you express no choice within 30 days of the end, TriageFit deletes it. Member data is unaffected: it belongs to the member relationship, and a member whose funded seat ends keeps their account.

9. For your DPO to complete

Our reading, not legal advice: a pack that gives the employer a roster and aggregate reports with a five-person floor, and no access to individual health data, is a lighter processing operation for the employer than one in which the employer holds employee health records. Whether it still meets your threshold for a DPIA is a call for your DPO.

  • Your lawful basis for inviting staff to a funded seat
  • How you will tell staff about the invitation and the roster
  • Who in your organisation holds the administrator role, and why
  • What your own workforce labels reveal, and who may edit them
  • Your likelihood and severity scores for each risk in section 6
  • Whether you consulted staff or their representatives
  • Your review date

Questions

If your DPO needs something these pages do not give, write to info@triagemethod.com and we will answer directly.