How team data flows
A TriageFit seat pack involves two separate data relationships, and keeping them separate is the design. Your organisation hands us a small amount of contact data so we can run your roster. Your people, once they accept a seat, become TriageFit members in their own right, with their own account, their own consent and their own privacy policy. This page walks each flow end to end; the data processing agreement gives the same boundary its legal form.
What your organisation gives us
- Your organisation's name and billing details, at purchase
- For each person you invite to a seat, as you invite them: their work email address, the role you give them, and whether the seat is funded by you
- Optionally, four workforce labels against that same address, worded by you rather than chosen from a list: department, site or region, employment type and tenure band. They are what lets an aggregate report speak about one department rather than the whole organisation, and every one of them can be left blank
That is the full list, and the invitation form holds no other field. We never ask you for an invitee's name, home address, date of birth or payroll number, and there is nowhere to enter one. We use what you do give us to bill the pack, send each invitation, keep your roster current, and group the aggregate figures by whichever labels you chose. Under the data processing agreement we process all of it on your instruction, as your processor.
What flows back to your organisation
- The roster: each invitation's state and whether it was redeemed, and for every person who has accepted, the name on their own TriageFit account, their email address, their seat type and the date they joined. That name is theirs to set and to change, and it reaches you from their account rather than from anything you told us
- Aggregate reports: participation and progress for the group as a whole, released only when at least five distinct members contributed to a figure, and suppressed with no number shown below that floor
- Invoices and billing history for the pack itself
Nothing else flows back. No organisation role can see an individual's training, food, messages, check-ins or any other health data, through any screen or any API route. People are told at redemption exactly what their employer can see, so nobody has to take our word for it, or yours.
What your people give us directly
A member's own use of TriageFit, from the intake through training, nutrition, check-ins and coaching conversations, is a relationship between that member and us. We hold it as an independent controller under the privacy policy, health data is processed only with the member's explicit consent, and the member keeps the ordinary rights over it: access, export, correction, consent withdrawal and erasure, exercised from inside their own account rather than through you.
Where it runs
The application and database run in Frankfurt, member uploads are stored under EU jurisdiction, and AI processing runs in EU regions only, enforced at runtime. Payments run through Stripe and email through Resend, both global providers. The sub-processor list names every service involved, what it does and where it runs, and the security overview covers encryption, access control and auditing.
When someone leaves, and when the pack ends
When you revoke a seat, or the pack lapses, the person's funded membership ends but their account and data remain their own: they can carry on with a personal plan or leave and take the ordinary member rights with them. Ending the pack changes what your organisation funds, never who owns the data. Roster data we processed on your behalf is deleted or returned after the agreement ends, as the data processing agreement sets out.
Questions
If your review needs more than these pages give, write to info@triagemethod.com and we will answer directly.