Privacy policy · Tietosuojaseloste
How Treat handles your data.
Last updated 5 November 2026. Sama suomeksi · Samma på svenska.
This policy covers the Treat healthcare app: patient intake, a conversational symptom survey, and case review by a licensed healthcare professional.
The Treat healthcare app
The app itself runs on Google Cloud in Finland
(region europe-north1, Assured Workloads EU Data Boundary).
The other processors it uses are listed in §8. The sections below follow the
structure of a Finnish tietosuojaseloste.
1 — Controllers
The Treat service has two controllers, depending on the data concerned.
Treat Health Oy (business ID 3618620-6), Helsinki, Finland, is the controller for data related to your user account and use of the platform ("account data"): identification and contact details, authentication, acceptance of terms and marketing consents, billing, service logs, and feedback.
The healthcare provider whose professional reviews your case — a clinic, or a practice run by a physician, nurse, therapist or other practitioner, registered in the register of social and healthcare service providers (Soteri) kept by the Finnish Supervisory Agency (Lupa- ja valvontavirasto) — is the controller (rekisterinpitäjä) for the patient records created in the care relationship, that is, the patient register under the Finnish Act on the Status and Rights of Patients (potilaslaki 785/1992) ("patient-record data"). Treat Health Oy processes patient-record data on the provider's behalf as a data processor (GDPR Article 28). The reviewing professional is bound by the professional secrecy duty in section 17 of the Finnish Act on Health Care Professionals (laki terveydenhuollon ammattihenkilöistä 559/1994).
2 — Contact
Data-protection contact: [email protected]. The same address also serves patient-record matters: we relay your request to the healthcare provider acting as controller. For complaints you may always contact the Office of the Finnish Data Protection Ombudsman (Tietosuojavaltuutetun toimisto), Ratapihantie 9, 00520 Helsinki.
3 — Purposes and legal bases
| Purpose | Controller | Legal basis |
|---|---|---|
| Providing the healthcare service (intake, healthcare-professional review, decision) | The healthcare provider (Treat as processor) | Contract (Art. 6(1)(b)) and the healthcare exception for special-category data (Art. 9(2)(h)); statutory obligation under potilaslaki |
| Maintaining the patient register | The healthcare provider (Treat as processor) | Statutory obligation (Art. 6(1)(c), potilaslaki) |
| Identifying and authenticating you (strong authentication) | Treat Health Oy | Contract (Art. 6(1)(b)) |
| Recording your consent for the professional to view your Kanta records | The healthcare provider (Treat as processor) | Explicit consent (Art. 9(2)(a)) |
| Invoicing, bookkeeping, and Kela-reimbursement handling | Treat Health Oy | Contract (Art. 6(1)(b)) and statutory obligation (kirjanpitolaki 1336/1997) |
| Monitoring service quality (post-case feedback) | Treat Health Oy | Legitimate interest (Art. 6(1)(f)) |
| Security, abuse prevention, and incident response | Treat Health Oy | Legitimate interest (Art. 6(1)(f)) |
| Product development on anonymised data | Treat Health Oy | Legitimate interest (Art. 6(1)(f)); data is anonymised before use |
4 — Data we process
Account data (Treat Health Oy as controller):
- Identification & contact: name, Finnish personal identity code (henkilötunnus, "hetu"), email, phone number, preferred language, and a stable authentication identifier.
- Consents: acceptance of Treat's terms of service and any marketing consent.
- Billing: invoice line items, payment status, and Kela-reimbursement identifiers where applicable.
- Service logs: IP address, request timestamps, and browser details; hetu and free-text clinical fields are redacted at the application boundary.
- Feedback: service rating, healthcare-professional rating, and free-text comment.
Patient-record data (the healthcare provider as controller; Treat as processor):
- Guardian data when the patient is a minor: the guardian's name, hetu, and contact details, plus proof of custodial rights.
- Kanta consent: your consent for the professional to view your Kanta records (scope, text version, and timestamp).
- Clinical intake: the symptoms and answers you type or dictate, allergies, current medication, and relevant medical history.
- AI intake transcript: the structured follow-up questions and your answers, used to compile a preparatory summary for the reviewing healthcare professional. You can correct the summary, and it is sent only after you approve it.
- Case & decision: the reviewing healthcare professional's summary, clarifying messages, and the case status. Prescriptions and referrals are issued in the healthcare provider's own patient record system.
5 — Data sources
- Directly from you when you sign up, chat, or submit a form.
- From your employer, if it provides the service: your name and date of birth, used to match your account to the employer's staff list.
- From the reviewing healthcare professional when they add notes, decisions, or clarifying messages to your case.
- From the Nordic identity broker Idura at sign-in: name, hetu (or the equivalent national identifier for other Nordic eIDs), and a stable OIDC subject identifier — see §10 for the full flow.
- Generated by our servers during use of the app (case IDs, timestamps, logs).
6 — Retention
The healthcare provider, as controller, is responsible for the retention of patient-record data; Treat stores the data on the provider's behalf. Patient records follow the Finnish retention rules for patient records (potilaslaki and Ministry of Social Affairs and Health decree 298/2009): typically 12 years from the patient's death, or 120 years from birth. Consent records are kept for the same period so that consent can be demonstrated. Billing and bookkeeping records: six years (Finnish Accounting Act). Service, audit and access logs: 90 days in the active log store, and archived for 12 years as required by Finnish patient data legislation.
7 — Disclosure
Personal data is disclosed only where there is a legal basis to do so. Disclosures of patient-record data are decided by the healthcare provider acting as controller.
- Kanta (the national health archive operated by Kela): the healthcare provider, through its reviewing professional, is responsible for the patient-record entries. The professional views your Kanta records and records prescriptions and patient-record entries in Kanta from the provider's patient record system, as required by law and your consent. Treat itself does not connect to Kanta.
- The provider's patient record system, D-Alusta (Kuura Health Oy): Treat relays the summary you approved, the case messages, and your identification and contact details to it so that the professional can handle your case.
- Your employer, if it provides the service: its administrators see your name, email address and whether you have accepted the invitation, and only company-level usage counts — never the content of your cases or which employee used the service. Counts are shown for completed months only; counts under five are not shown, and other counts are rounded down to a multiple of five. In a very small company, such counts can reveal more than in a large one.
- Treat's customer service sees the messages you send to customer service and, when the professional asks for an in-person appointment to be booked, your name, personal identity code, phone number and the appointment address you confirmed, the professional's name and booking instruction, your employer's name, coverage terms and coverage summary (PDF), and the clinic, address and time you chose. The personal identity code is needed to book the appointment with the clinic in your name, and the address to choose a clinic near you. Customer service does not see your conversation with the professional or your intake answers, except the professional's booking instruction: it is shown word for word and may contain health information needed for the booking.
- Other healthcare providers when you consent, or when a statutory obligation requires it (for example continuity of care under section 13 of potilaslaki).
- Public authorities (courts, police, the Tax Administration, social insurance institutions, and supervisory authorities) when they have a legal basis for the request.
- A buyer of the Treat business in the event of a merger, acquisition, or restructuring — subject to the same safeguards, and we will notify you of the transfer.
- Debt-collection agencies and legal counsel only to the extent necessary to enforce an unpaid invoice.
We do not disclose your data to advertisers or data brokers, and we do not sell your data.
8 — Processors (sub-processors)
The following parties process personal data on Treat's behalf under a signed Data Processing Agreement (GDPR Article 28). For patient-record data they act as sub-processors in the chain healthcare provider → Treat → the processor listed below:
| Processor | Scope | Region | DPA |
|---|---|---|---|
| Google Ireland Limited (Google Cloud Platform) | Treat app: Cloud Run, Cloud SQL PostgreSQL, Cloud Storage, Secret Manager, KMS, and Vertex AI (Gemini) for speech-to-text and document analysis — all patient chats, case records, healthcare-professional accounts, and company data live here. | europe-north1 (Helsinki), Assured Workloads EU Data Boundary; Vertex AI in the EU | Google Cloud DPA |
| Microsoft Ireland Operations Limited (Azure OpenAI) | The AI intake assistant: the follow-up questions, your answers, and the preparatory summary. | EU Data Zone | Microsoft Products and Services DPA |
| Amazon Web Services EMEA SARL (Amazon SES) | Transactional email such as invitations and account notices; no health data. | eu-north-1 (Stockholm) | AWS GDPR DPA |
| 46elks AB (Sweden) | Text messages and phone calls to and from Treat's phone number. | Sweden | Signed DPA on request |
| Cloudflare, Inc. |
Marketing site and DNS: Cloudflare Pages, plus
DNS, TLS, and DDoS protection for treat.health, and a
backup route for transactional email when Amazon SES is
unavailable. Never handles patient chats or case data.
|
Global network; see §11 | Cloudflare Customer DPA |
| Idura ApS (Denmark, CVR 35142207), Gammel Kongevej 3E, 1610 København V — a Nordic eID broker | Strong electronic identification (vahva sähköinen tunnistaminen) via Finnish bank credentials and Mobiilivarmenne, Swedish BankID and Freja ID, Norwegian BankID and Vipps, and Danish MitID. Idura brokers the authentication event and returns a signed OIDC token from which we store the claims we need (see §10). | EU only — Idura commits in its privacy policy not to transfer or store personal data outside the EU | Idura Privacy Policy · signed DPA on request |
When we add or replace a processor, we update this list before the new processor starts handling data. You can request the current signed DPAs at any time from [email protected].
Kanta (Kela) is not a processor in this chain. Kanta is a separate national register operated by Kela under its own statutory basis; the healthcare provider acting as patient-register controller and Kela act as independent controllers for the records exchanged under your explicit consent. Treat is not a party to that exchange.
9 — The AI intake assistant
The intake chat uses Microsoft's Azure OpenAI service in the EU Data
Zone. Speech-to-text uses Google's Vertex AI (Gemini) hosted in the EU
(eu.rep.googleapis.com). Both are called server-to-server
under enterprise terms — we do not use
consumer AI services, and the providers do not use your data to train
models. The assistant only asks structured follow-up questions and
compiles a summary that you can correct and must approve before it is
sent; it does not diagnose, treat, prioritise urgency, or make
automated decisions within the meaning of GDPR Article 22 — the
clinical decision always rests with the reviewing healthcare
professional. The providers may retain data for a limited time for
abuse monitoring. We have applied for a Google abuse-monitoring log
exemption for the Treat project; until it is approved, we do not
assume strict zero retention for AI calls.
10 — Strong authentication (Idura)
To meet the identity-assurance requirements for a healthcare provider, sign-in uses Idura ApS (a Danish company, CVR 35142207, Gammel Kongevej 3E, 1610 København V; privacy notice), a Nordic identity broker. Idura fronts the national eID schemes for us, so we do not have to integrate each one individually:
- Finland: Finnish Trust Network bank credentials and Mobiilivarmenne.
- Sweden: BankID and Freja ID.
- Norway: BankID and Vipps.
- Denmark: MitID.
How the flow works. Your browser is redirected to Idura, which sends you on to the eID method you pick. That provider verifies your identity (for example with a fingerprint, PIN, or one-time code), and Idura returns a signed OpenID Connect token to Treat. Treat stores only the fields it needs from the token: your name, national identifier (hetu or its Nordic equivalent), and a stable subject identifier used to recognise you on later logins.
Roles. Idura is our processor for brokering the authentication event and is bound by a DPA (see §8). The underlying eID issuers — the banks, mobile operators, MitID, Freja, and others — are independent controllers for the authentication event on their side and publish their own privacy notices. Treat never receives your bank credentials, MitID code, or biometric data — only the verified identity claims listed above.
Where data flows. Idura commits in its own privacy policy that authentication traffic and any related personal data stay inside the European Union — Idura will not transfer or store such data outside the EU. The assertion is transient at Idura, and we do not retain it beyond the immediate sign-in exchange; the durable record lives in your Treat account (see §4 and §6).
Idura's own sub-processors. Idura publishes its sub-processor list at trustcenter.idura.eu/subprocessors. As of the date of this policy the list comprises Microsoft Azure (Ireland / Netherlands) and AWS (Germany) as hosting providers for the authentication traffic, and HubSpot as Idura's internal CRM — HubSpot does not receive Treat authentication data. Idura holds FTN, MitID, NSIS, DORA, GDPR, and NIS 2 attestations.
Assurance level. We require the FTN "substantial" assurance level (or its equivalent in the other Nordic countries), which is the level Finnish regulators expect for access to healthcare services.
11 — International transfers
Health data stays inside the EEA. The processors that handle it are
contractually restricted to EU regions for Treat's data (Google Cloud
europe-north1 with Assured Workloads EU Data Boundary;
Azure OpenAI EU Data Zone; Amazon SES eu-north-1; 46elks
in Sweden; Idura EU-only, see §10). Cloudflare operates a global
network: DNS lookups, the marketing site, and transactional email
sent through the backup route when Amazon SES is unavailable may be
processed outside the EEA. Those emails contain no health data, and
such transfers rely on the European Commission Standard Contractual
Clauses in Cloudflare's DPA.
12 — Security
Concrete measures we operate under GDPR Article 32:
-
Encryption at rest for all stored data. The database
and secrets use customer-managed KMS keys in
europe-north1, rotated every 90 days; other storage uses Google-managed encryption. - Encryption in transit via TLS 1.2 or later on all endpoints; the database accepts only encrypted connections.
- Least-privilege access: production access is restricted through Google IAM with per-service accounts; there are no shared credentials, and all access is audit-logged.
- Strong authentication for all users through Idura eID; there is no password sign-in. Only you can read your conversation with the healthcare professional in the Treat application; no Treat staff or administrator role can read it.
- Pseudonymisation and redaction of hetu and free-text clinical fields in application-level service logs.
- Backups with point-in-time recovery, encrypted with the same KMS keys; database backups expire within about two weeks.
- Confidentiality obligations in every employment and subcontractor agreement; healthcare professionals are additionally bound by section 17 of the Finnish Act on Health Care Professionals (559/1994).
- Incident response: we notify the Finnish Data Protection Ombudsman within 72 hours and affected users without undue delay of any breach that meets the GDPR threshold.
13 — Your rights
You may request access to your data, its correction or deletion, restriction of processing, or a portable export; withdraw a consent; or object to processing based on legitimate interest. Some rights are limited when the data forms part of a statutory patient record under potilaslaki. Contact [email protected] — we reply within one month, and we relay requests concerning patient-record data to the healthcare provider acting as controller. You always retain the right to complain to the Office of the Finnish Data Protection Ombudsman.
14 — Cookies
The app uses only strictly necessary cookies (session, CSRF protection, and language). No third-party advertising or analytics cookies are set. The marketing site may set an anonymous first-party analytics cookie, described in its own cookie notice.
15 — Changes
If we materially change this policy, we will update the date at the top and notify signed-in users in the app before the change takes effect.