Privacy & Security Policy

Effective date: 2026-03-20
Last updated: 2026-11-16 (optional export to Google Sheets)
Provider: Didenco
Contact: jan@didenco.be

This policy consolidates Didenco's privacy and data-protection documentation for the handling of personal and special-category (medical) data. See also the Terms & Conditions and the Data Processing Agreement.

Roles under the GDPR. For account and user data (the healthcare professional's own data), Didenco acts as controller. For patient data submitted to or generated through the Service, Didenco acts as processor on behalf of the healthcare professional or, for a group practice, the practice, which is the controller — see the Data Processing Agreement.

1. Privacy Notice

What We Collect

Why We Process Data

Legal Bases

Sharing and Processors

Sharing Within a Practice

Data Location and Transfers

Retention

Your Rights

Security

2. Record of Processing Activities (RoPA)

Processing Register

Processing activityData subjectsData typesPurpose Legal basis (Art. 6 / 9)Recipients/processorsStorage location RetentionSecurity measures
Patient diagnosis/session records Patients Health data, identifiers, transcript, conversation summary, medical reports, example medical reports. Audio is transmitted to the transcription provider but not stored in the database. Care support and session management Art. 6(1)(b), Art. 9(2)(h) (or Art. 9(2)(a) with explicit consent) Approved therapists of the controller's practice; AWS (hosting and Bedrock LLM processing); Speechmatics (audio transcription) AWS EU (storage eu-north-1; Bedrock processing eu-central-1) 10 years (or local law) Encryption at rest/in transit, RBAC, logs
User account management Clinicians/staff Name, email, role, auth metadata, practice membership and practice role Authentication, access control, and practice membership Art. 6(1)(b) Didenco (internal processing) AWS EU (eu-north-1) Account lifetime + 1 year Password policy, least privilege
Practice-management sync (Crossuite integration, optional) Patients, clinicians Appointment/agenda events, patient identifiers, and session notes pushed to Crossuite Two-way sync with the user's own Crossuite practice-management system Art. 6(1)(b), Art. 9(2)(a)/(h) Crossuite (service.crossuite.app), at the user's instruction and using the user's own credentials Crossuite; connection tokens encrypted at rest in the Didenco database Per the user's Crossuite account; tokens until the user disconnects Encrypted credential storage, TLS
System monitoring and audit logs Users/admins IP, device, event logs, access logs (in infrastructure logs, not in application database) Security monitoring and incident response Art. 6(1)(b) Amazon Web Services (AWS) AWS EU (eu-north-1) 90 days Restricted, access-controlled logs
Support communications Users Contact details (email address) and message content Customer support and issue resolution Art. 6(1)(b) Google (Gmail/SMTP email delivery) Google Workspace / Gmail (subject to Google's terms; may involve non-EEA processing) Retained in the email inbox until no longer needed Access controls, TLS in transit

Note: Session audio recordings themselves are not stored in the database; patient names, transcripts, conversation summaries, medical reports, and example medical reports are stored. Audio is transmitted to the transcription provider (Speechmatics) for processing.

Note: The optional "Open in Google Sheets" action is not a Didenco processing activity towards Google. When a therapist clicks it for a session, their browser downloads the filled Excel intake form from Didenco (as for the normal download) and uploads it directly from the browser to the therapist's own Google Drive (Google Drive API, drive.file scope only), converted to a Google Sheet. The Google access token stays in browser memory and is never sent to or stored on Didenco's servers; Didenco's servers send no data to Google for this feature. The resulting copy lives in the controller's Google account, outside the Service; Google is a destination chosen by the controller, not a Didenco sub-processor.

International Transfers

3. Processor DPA Register

Maintain signed DPAs for all processors handling personal data.

ProcessorServiceData processedData locationTransfer mechanismDPA signed
Amazon Web Services (AWS) Hosting / database / storage / audit logging / Bedrock LLM processing Account, medical, logs, audit logs EU regions eu-north-1 / eu-central-1 N/A if EEA-only; SCCs if needed AWS GDPR DPA (auto-incorporated)
Speechmatics (Cantab Research Ltd, UK) Audio transcription (speech-to-text) Patient audio (special-category), transcript United Kingdom (EU adequacy); sub-processors may be outside the EEA EU SCCs + UK Addendum Yes — signed DPA (July 2026)
Google (Google Workspace / Gmail) Support-email delivery (SMTP) Contact email, support message content Google (may be non-EEA) EU SCCs (via Google Workspace Cloud Data Processing Addendum) Yes — Google Workspace Cloud DPA (incorporated)

Note: Google Drive / Google Sheets export ("Open in Google Sheets") is not listed as a sub-processor. The upload runs from the therapist's browser to the therapist's own Google account, on the controller's instruction; Didenco's servers send no data to Google and hold no Google access token. The controller is responsible for its own agreement with Google (e.g. Google Workspace with Google's Cloud Data Processing Addendum). This is separate from Didenco's use of Google for support email.

Minimum Vendor Requirements

4. Data Protection Impact Assessment (DPIA)

Processing Overview

Purpose and Necessity

Risks to Individuals

Measures and Safeguards

5. Data Retention Policy

Retention Schedule

Data categoryDefault retentionJustificationDeletion method
Medical records and session notes 10 years (or local legal requirement) Clinical/legal obligations Secure deletion from primary + backups per schedule
Account/profile data Contract term + 1 year Service administration and dispute handling Hard delete/anonymization
Security and access logs 90 days Security monitoring and incident response Automated log lifecycle expiry
Support tickets/emails 1 year after closure Support continuity and quality assurance Periodic purge

Rules

6. Security Policy (Personal and Medical Data)

Technical Controls

Operational Controls

Governance

Encryption for Data in Processing: Options Considered

To strengthen protection of data while actively being processed, two additional approaches were formally evaluated.

Option A: AWS Nitro Enclaves

Assessment outcome: not feasible for current application workflow.

Conclusion: Nitro Enclaves were considered, but rejected for this architecture because the required real-time external service dependency conflicts with enclave network isolation constraints.

Option B: End-to-End Encryption of Patient Names

Assessment outcome: not feasible for current application workflow.

Conclusion: End-to-end encryption of patient names was considered, but rejected because required LLM processing depends on plaintext access and the application workflow prohibits strict E2E encryption for this field.

7. Data Breach Procedure

Privacy contact: jan@didenco.be

1) Detect and Triage

2) Contain and Investigate

3) Notify

4) Remediate and Learn

8. Access Control Policy

Principles

Requirements

Practice-Based Access to Patient Records

Emergency Access

9. Key Management Policy

Scope

Controls

Recovery and Continuity

10. Vendor Risk Assessment

Use this checklist before onboarding vendors that process personal or medical data.

Note: Google Drive / Google Sheets, used by the optional "Open in Google Sheets" export, is not onboarded as a Didenco vendor: the upload runs from the therapist's browser to the controller's own Google account, and Didenco's servers send no data to Google. Assessing Google for that use (agreement, legal basis, data location) is the controller's responsibility.

AreaQuestionsStatusNotes
LegalDPA signed? Subprocessor terms acceptable?[Pass/Fail][notes]
SecurityEncryption, access control, logging, incident response documented?[Pass/Fail][notes]
Data locationEEA hosting available? Transfer mechanism in place if not?[Pass/Fail][notes]
PrivacySupports DSARs, deletion, retention controls?[Pass/Fail][notes]
ReliabilityBackups, availability targets, support commitments?[Pass/Fail][notes]

Decision

11. Logging and Audit Policy

Logged Events

Requirements

Review