# Your DPIA becomes a check, not a project.

For the DPO and the privacy officer. Your organisation is the controller, Axiomatic the processor. Every kind of data is here with its place and period; you complete the DPIA from the privacy pack.

> Can I finish my DPIA from this?

- [GDPR, art. 9(1), data concerning health](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679)
- [GDPR, art. 28(1), the processor agreement](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679)
- [GDPR, art. 35(3)(b), the DPIA](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679)

## Every heading filled in. Your part left open.

Our answer under every heading the GDPR asks for.

DPIA · Inora · Art. 35 and 36 GDPR

### Filled in for you, heading by heading

Privacy pack §6 · public · version 1.16

1. 01 Systematic description Art. 35(7)(a) GDPR The processing, the roles and the data flows: filled in.

   Filled in by Axiomatic

   The record above, about your staff and the clients they ask about. Recipients: the two sub-processors in the chain, both in the EU.

   Your part

   The scale: how many staff, which teams and locations, how many sources.

   Backed in [Privacy pack §2](https://axiomatic.digital/policies/privacy-pack.en.pdf) [Sub-processors](https://axiomatic.digital/en/trust/sub-processors)

2. 02 Purposes Art. 35(7)(a) GDPR Each purpose, with its processing.

   Filled in by Axiomatic

   The purpose in the record, and no other: no training, never combined with another organisation.

   Your part

   Confirm this is your purpose, for each team Inora reaches.

   Backed in [Privacy pack §3](https://axiomatic.digital/policies/privacy-pack.en.pdf)

3. 03 Necessity and proportionality Art. 35(7)(b) GDPR Minimal data and the alternatives: filled in. You set the legal basis.

   Filled in by Axiomatic

   No BSN, no second client file; with single sign-on no passwords. Conversations 90 days by default; a longer term you weigh in this DPIA.

   Your part

   Set the legal basis, with the articles in the record, and weigh it against what happens now: searching, calling a colleague, not knowing.

   Backed in [Privacy pack §4](https://axiomatic.digital/policies/privacy-pack.en.pdf)

4. 04 Risks to data subjects Art. 35(7)(c) GDPR Every risk with likelihood, impact and measure.

   Filled in by Axiomatic

   Nine risks, each with likelihood, impact and measure: health data in typed or spoken text, watching staff, a wrong answer, a request from a foreign authority, a data breach, service measurements used as a performance measure, an error in the competence record, a question in the test set (only on your instruction) traced or kept too long, and the answer record traced to whoever asked.

   Your part

   The weighing for your organisation: which teams, which clients, which residual risks you accept.

   Backed in [Privacy pack §5, the risk table](https://axiomatic.digital/policies/privacy-pack.en.pdf)

5. 05 Measures Art. 35(7)(d) GDPR Every measure, with where it stands.

   Filled in by Axiomatic

   Built to NEN 7510 and ISO 27001: an environment per organisation, TLS 1.2 or higher and AES-256, only the engineers who build Inora reach production, every access logged.

   Your part

   Your own measures: which groups get access, and what you ask staff about what they type.

   Backed in [Security overview](https://axiomatic.digital/policies/security-overview.en.pdf) [Control matrix, the basis for your statement of applicability](https://axiomatic.digital/policies/control-matrix.en.pdf)

6. 06 Views of data subjects Art. 35(9) GDPR Our part is there; the views are your staff’s.

   Filled in by Axiomatic

   Your staff speak through the works council: its consent (art. 27 WOR) is their view. The request is ready, with the rules on conversations above.

   Your part

   Ask for the consent and record it, and hear the client council where it fits.

   Backed in [Works council](https://axiomatic.digital/en/trust/works-council) [Consent request](https://axiomatic.digital/policies/works-council-consent-request.en.pdf)

7. 07 Prior consultation Art. 36 GDPR Our answer is there; the decision is yours.

   Filled in by Axiomatic

   Not needed when the measures above remove the high risk. Our estimate of the residual risk is given per risk in the risk table.

   Your part

   Your DPO weighs the residual risk and records the weighing. If a high risk remains, you consult the Dutch Data Protection Authority before the start.

   Backed in [Privacy pack §5](https://axiomatic.digital/policies/privacy-pack.en.pdf)

> “The DPIA came three-quarters filled in. I only had to do our part.”

Privacy officer, home-care organisation

## You decide. We answer for the chain.

All processing stays in the EU. We answer to you for both sub-processors.

European Union All processing and storage, the model included · data processing agreement

All processing and storage, the model included · data processing agreement

1. Controller

   Art. 4(7) GDPR

   ### Your organisation

   The care organisation

   - Decides

     What Inora is for, which sources it holds, who works with it and how long conversations stay.

   - Carries

     The legal basis, the DPIA and the report to the Dutch Data Protection Authority.

2. Data processing agreement Art. 28(3) GDPR

3. Processor

   Art. 28 GDPR

   ### Axiomatic B.V.

   Delft · KvK 97816825

   - Does

     Builds, implements and runs Inora, only on your written instructions.

   - Answers for

     Every sub-processor, to you.

4. Sub-processing agreement Art. 28(4) GDPR

5. Sub-processors

   Art. 28(4) GDPR

   - ### Amazon Web Services EMEA SARL

     Luxembourg · Europe (Ireland) Region

     - Does

       Hosts Inora and runs the model through Amazon Bedrock, on the EU inference profile.

     - Keeps

       Amazon Bedrock does not store the question or the passages and does not pass them to the model’s maker.

   - ### Microsoft Ireland Operations Limited

     Dublin · Azure, EU region

     - Does

       Runs parts of Inora in the EU region.

     - Keeps

       With the modified abuse monitoring Microsoft approves for sensitive data: Microsoft stores no questions or answers, and no Microsoft employee reads them.

   * Are bound by

     Duties no lighter than ours. Neither trains a model on your data.

A new sub-processor

1. 30 days ahead You hear by email, before it processes anything of yours.
2. Your objection Until it is resolved, it processes nothing of yours.
3. No solution Then you may end the agreement for the part that cannot be delivered without the new sub-processor, at no cost.

Data processing agreement · Art. 28(2) GDPR

Parents

Parent companies · United States

- ### Amazon.com, Inc.

  Seattle · EU-U.S. Data Privacy Framework

- ### Microsoft Corporation

  Redmond · EU-U.S. Data Privacy Framework

We transfer nothing: your data stays in the EU. Storage in the EU does not rule out a request from a foreign authority. If one comes, you hear of it first, unless the law forbids it, and we object to any without a valid basis.

Data processing agreement · Art. 48 GDPR

## Your record of processing, already filled in.

Every processing activity with its place and period. The whole record is in the pack.

Record of processing

Inora, processed by Axiomatic B.V. on behalf of your organisation

- Purpose

  To give care workers answers from the organisation’s own sources, and to draft reports in its format. Each processing below states its own purpose, and no other.

- Basis

  Art. 30(1) GDPR, filled in from the record Axiomatic keeps as processor (Art. 30(2) GDPR) · the data processing agreement

- Processor

  Axiomatic B.V., Delft (KvK 97816825); data protection officer: an external DPO, reachable at fg\@axiomatic.digital (Art. 30(2)(a) GDPR)

- Recipients

  Axiomatic B.V. (processor); Amazon Web Services EMEA SARL and Microsoft Ireland Operations Limited (sub-processors); per team the team lead and the works council

- Security

  The control matrix, on the IT and security page

1. P1 Documents Its own storage and search index, Europe (Ireland); embedding through Amazon Bedrock in the EU As long as you keep it; out of backups within 30 days

   Protocols, guidelines and work agreements, with the names of authors and owners.

   - Whose

     Staff, as author or owner

   - What for

     Searching, and showing as a source

   - Where

     Its own storage and search index, Europe (Ireland); embedding through Amazon Bedrock in the EU

   - How long

     As long as you keep it; out of backups within 30 days

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

2. P2 Questions, answers and reports Europe (Ireland); the model and speech transcription in the EU, through Amazon Bedrock or Azure OpenAI 90 days, or the period you set; a conversation the function you named asked for, until the investigation is complete.

   Questions, answers with their source, reports in SBAR or SOAP. Everything typed or spoken counts as health data.

   - Whose

     Staff; the clients they ask about

   - What for

     Answers from your sources, reports in your format; per conversation the topic sorted for the team reports, built in

   - Where

     Europe (Ireland); the model and speech transcription in the EU, through Amazon Bedrock or Azure OpenAI

   - How long

     90 days, or the period you set; a conversation the function you named asked for, until the investigation is complete.

   Legal basis · yours

   Art. 6 GDPR

   Art. 9(2)(h) GDPR

   Art. 30(3)(a) UAVG

   for you to fill in

3. P3 Accounts Europe (Ireland) While access lasts, plus 30 days

   Name, work email, a unique identifier and groups from your identity provider, through single sign-on and SCIM.

   - Whose

     Staff with access

   - What for

     Signing in, access by role

   - Where

     Europe (Ireland)

   - How long

     While access lasts, plus 30 days

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

4. P4 Logs Europe (Ireland) 12 months

   Sign-ins, admin actions, IP addresses, times, every access by Axiomatic. Record access is under P11.

   - Whose

     Your staff and Axiomatic’s

   - What for

     Security, incident investigation, accountability; on request you receive the logging only totalled per team of at least five people and per day, one member of staff’s sign-in times and IP addresses never

   - Where

     Europe (Ireland)

   - How long

     12 months

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

5. P5 Support and implementation Europe (Ireland), in your own environment The period of the processing concerned

   Only the documents you ask Axiomatic to look at; a staff conversation only on a written request from the function you name. No copies outside your environment.

   - Whose

     Staff; the clients they ask about

   - What for

     Solving issues, guiding the implementation

   - Where

     Europe (Ireland), in your own environment

   - How long

     The period of the processing concerned

   Legal basis · yours

   Art. 6 GDPR

   Art. 9(2)(h) GDPR

   Art. 30(3)(a) UAVG, where needed

   for you to fill in

6. P6 Service measurements Europe (Ireland) Per user 30 days, after that only totalled per team of at least five people

   Numbers of questions and response times per user, without content or names.

   - Whose

     Staff with access

   - What for

     Only to run your own environment and fix problems in it; never to you per worker.

   - Where

     Europe (Ireland)

   - How long

     Per user 30 days, after that only totalled per team of at least five people

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

7. P7 Competence record Europe (Ireland) In Inora for as long as the worker works for you, plus 30 days; in those 30 days you export it to your own personnel file, where your own term applies.

   Per worker, the reserved and high-risk procedures under your training policy, with the procedure, the protocol with its version, the date, on whose instruction and who signed off the practical assessment, kept current from what the worker reports doing; questions to Inora never count. Never the content of a conversation, a score or a usage figure.

   - Whose

     Staff, by name

   - What for

     Your competence register in Inora Matrix: only the competence record the inspectorate expects (Wkkgz, Wet BIG); in the pilot a preview for the participating team, until the works council consents

   - Where

     Europe (Ireland)

   - How long

     In Inora for as long as the worker works for you, plus 30 days; in those 30 days you export it to your own personnel file, where your own term applies.

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

8. P8 Test set Europe (Ireland) Until you withdraw the instruction, at the latest until the end of the agreement; then deleted within 30 days

   Questions from your organisation, and answers a member of staff or a check flagged with their question, stripped of the names of clients and staff by a language model in the EU; no person reads a question or answer in it.

   - Whose

     Staff; the clients they asked about

   - What for

     To test every new version of Inora before it goes live in your environment; only on your written instruction, after the works council’s consent where you have one

   - Where

     Europe (Ireland)

   - How long

     Until you withdraw the instruction, at the latest until the end of the agreement; then deleted within 30 days

   Legal basis · yours

   Art. 6 GDPR

   Art. 9(2)(h) GDPR

   Art. 30(3)(a) UAVG

   for you to fill in

9. P9 Answer record Europe (Ireland), at Axiomatic; you receive it on written request 2 years; then out of backups within 30 days

   Per answer the sources with their versions, the check it passed and the date, and a reference the member of staff sees with the answer; never who asked, the time, the ward, the question or the answer.

   - Whose

     Staff and clients, only so far as identifiable

   - What for

     Accounting for what an answer rested on, for an incident or a complaint

   - Where

     Europe (Ireland), at Axiomatic; you receive it on written request

   - How long

     2 years; then out of backups within 30 days

   Legal basis · yours

   Art. 6 GDPR

   for you to fill in

10. P10 Record data Europe (Ireland); the model in the EU, through Amazon Bedrock or Azure OpenAI The period in your data processing agreement; what remains falls under P2

    Once Inora reads the record, through a connection or the user’s own login: what Inora reads from the client record for the task under way, a question, preparing a visit, a review, a rule or signal, at night too. No second record.

    - Whose

      The clients; the staff in whose name the work runs

    - What for

      Doing the task, with the rights of whoever does the work

    - Where

      Europe (Ireland); the model in the EU, through Amazon Bedrock or Azure OpenAI

    - How long

      The period in your data processing agreement; what remains falls under P2

    Legal basis · yours

    Art. 6 GDPR

    Art. 9(2)(h) GDPR

    Art. 30(3)(a) UAVG

    for you to fill in

11. P11 Record log Europe (Ireland) The period in your data processing agreement

    Once Inora reads the record, through a connection or the user’s own login: per step what Inora did, on whose behalf, for which client and with what result; never what anyone asks. The EHR keeps its own log.

    - Whose

      Staff; the clients concerned

    - What for

      Checking record access, set up to NEN 7513; open to the function you appoint, per client or in an investigation, never as a figure about one member of staff

    - Where

      Europe (Ireland)

    - How long

      The period in your data processing agreement

    Legal basis · yours

    Art. 6 GDPR

    Art. 9(2)(h) GDPR

    Art. 30(3)(a) UAVG

    for you to fill in

- Backups

  Daily, encrypted, kept 30 days, in the Europe (Ireland) Region, across several availability zones.

- After the end

  Until day 30 everything back: documents in their own format, the rest machine-readable; day 30 gone from active systems, day 60 from backups. Confirmed in writing.

* May I type a client’s name?

  From the client record Inora reads with the rights of whoever does the work, for the task under way: a question, preparing a visit, a review, a rule. It never asks for a name, date of birth or citizen service number, and it keeps no second record. Whatever someone types or dictates, we treat as health data. Whether it is allowed follows from the legal basis you set.

  P2 · privacy pack

## No one reads what staff ask.

No one in your organisation. Axiomatic only on written request, and staff hear of it.

- ### Axiomatic

  Named in the DPA

  Access log · your organisation’s environment

  - Without a written request no access
  - 14 Oct · DPO · for a complaint 1 conversation
  - Care worker told 15 Oct

  Axiomatic reads a conversation only on a written request from the function the organisation names, for an incident or a complaint; every access is logged and the member of staff is told. In an outage or security incident Axiomatic examines the system logs and the answer record, never a conversation. Whoever made the request gets a finding about Inora, never what the member of staff asked or read.

  - [Privacy statement · Staff conversations](https://axiomatic.digital/en/trust/privacy#staff-conversations)

What care workers ask Inora never reaches the organisation. Only what the care worker sends does, and the competence record the inspectorate expects.

[How the works council reads it](https://axiomatic.digital/en/trust/works-council)

## We report first. Your deadline stays yours.

You hear as soon as we know, with everything for your own report.

Deadlines

Who does what after a data breach

1. Hour 0

   *Axiomatic*

   We see a data breach, or suspect one.

2. Within 24 hours

   *Axiomatic*

   We report it to you, with what you need for your own report.

3. Within 72 hours of our notice

   *Your organisation*

   Your report to the Dutch Data Protection Authority, where the breach must be reported.

4. Within 10 working days

   *Axiomatic*

   Our written report: what happened and what we changed.

Our deadline is a maximum, not a waiting time: you hear as soon as we know enough to report it. Your own deadline does not wait for our report.

## Everything for your DPIA, in one place.

What the DPO receives from Inora, and when.

- [Sub-processors](https://axiomatic.digital/policies/sub-processors.en.pdf): Who else processes data, and where.
- [Privacy pack with the DPIA pre-filled](https://axiomatic.digital/policies/privacy-pack.en.pdf): The DPIA pre-filled: the roles, and each processing with its purpose, place and period.
- [Privacy statement](https://axiomatic.digital/policies/privacy.en.pdf): What we process, why, where and for how long.
- [Continuity](https://axiomatic.digital/en/implementation#what-stays): Your knowledge if you stop, if we stop, or if Axiomatic changes hands.
- Notice and report of a data breach: Our notice within 24 hours, then our report.