FROID Psique · Security

Understand the path of the data.

Privacy starts by distinguishing purpose, processing and storage. This page describes the architecture of the new version; the current policy and contractual documents detail suppliers, regions, retention and responsibilities.

Facial analysis and video calls are different paths

For facial analysis, the browser extracts numerical coefficients and sends them to the engine on the server. This does not mean that all the video of a teleconsultation stays on the device: communication between participants may use the call's own transmission and relay.

Pattern calculation uses coefficients, not a library of facial recordings. The absence of a measure is declared, without fabricating values.

Audio and transcription

The processing architecture described by FROID provides for infrastructure contracted by FROID, hosted in Finland, and transient audio, with no session file for later playback. Transcription may involve a specialized supplier. Each supplier's retention conditions must be stated in the current policy.

Transcripts, summaries, measures and notes are data distinct from the raw media and may remain stored for the authorized purposes.

Protection and permissions

Protected transmission, encryption at rest, organizational separation and access control are part of the protection architecture. Access to clinical content must respect authorized roles and relationships, not merely the fact that someone administers a clinic.

We do not equate protection in transit with a guarantee that the server never accesses content: authorized processing steps need to handle the data. No architecture allows promising absolute security.

Governance of aggregated analysis

Data-Froid is separated from the private clinical record by purpose and eligibility criteria. Removing direct identifiers is only part of the process. Textual syntheses, combinations of attributes and small groups also need risk assessment.

Anonymization parameters, query floors and re-identification tests require technical documentation. In this presentation we do not publish numerical guarantees of anonymity, nor do we convert an internal score into a probability of identification.

Rights, contracts and transparency

The professional's contract and the patient's authorizations delimit the applicable uses. Requests about data must be handled in accordance with the policy, the legal bases and retention obligations, without promising automatic deletion of every record in every situation.

Need to assess the architecture before engaging?