1) Overview
This process describes how external client data is ingested from a client-provided Web API, stored and processed in an EU data centre, and made available to authenticated clients through a secure web application. All stored data (source and results) is encrypted at rest, and access to results is restricted by access controls.
​
2) Actors / Components

• Client Web API: External system providing data.

• Ingestion Service: Retrieves data from the Web API using a secure connection and a client-provided access key.

• EU Data Centre Storage: Stores source data and analysis results. Data is encrypted at rest.

• Processing & Analytics Service: Performs calculations/analysis using the stored data.

• Web Application: Presents analysis results to authenticated clients.

• Users / Roles:

  • Client User: Authenticated user accessing results.

  • Processors: Parties handling data. Preventos Informatics Oy personnel does the data handling.
     

3) Data Flow Summary

1. Data Ingestion

   • Data is read from the client provided Web API using a secure connection (e.g., TLS, HTTPS).

   • Authentication to the API uses a client-provided access key.

2. Secure Storage (Source Data)

   • Data is stored in an EU data centre.

   • Data is encrypted at rest (stored in encrypted form).

3. Processing & Analytics

   • Stored data is used to perform calculations and analysis.

   • Processors (Preventos Informatics Oy personnel) handle the data during processing.

4. Secure Storage (Results)

   • Analysis outputs/results are stored in the same EU data centre.

   • Results are stored encrypted at rest, in the same manner as source data.

5. Client Access & Presentation

   • Results are shown via a web application.

   • The client must be authenticated.

   • The application enforces access control so users only see data they are authorized to access.