We use cookies to give you the best possible experience. Help us improve by accepting all cookies - you'll get a faster, more personalized experience. Or click "Essential Only" for a basic (but limited) experience. Learn more

Security & Compliance Documentation

We Take Your Patients' Data
As Seriously As You Do.

This document provides a comprehensive overview of the security architecture, data handling practices, encryption protocols, compliance certifications, and regulatory adherence that govern every aspect of the DigitalTCO platform.

HIPAA CompliantUK GDPRNHS DSPTCyber EssentialsAES-256 EncryptedBAA Available

Last updated: March 2026  |  Document version: 4.2  |  Next review: September 2026

01

Security Overview

A summary of our commitment to protecting clinical data at every layer of the DigitalTCO platform.

DigitalTCO is a clinical documentation platform purpose-built for dental professionals. The platform converts voice recordings captured during clinical encounters into structured, accurate clinical notes using artificial intelligence. Because this process inherently involves the capture, transmission, processing, and storage of sensitive patient health information, security is not an afterthought or a feature we have bolted on — it is the foundational architecture upon which every aspect of the product has been designed.

We understand that the decision to adopt any technology that handles patient data is not taken lightly. Dental professionals have regulatory obligations under frameworks including the Health Insurance Portability and Accountability Act (HIPAA) in the United States, the UK General Data Protection Regulation (UK GDPR) and the NHS Data Security and Protection Toolkit (DSPT) in the United Kingdom, the Privacy Act 1988 and the Australian Privacy Principles (APPs) in Australia, and various other data protection regimes worldwide. Our responsibility is to ensure that your use of DigitalTCO does not merely satisfy these obligations, but exceeds them.

This document is intended to provide you — and your practice's information governance lead, compliance officer, data protection officer, or legal counsel — with a thorough, transparent account of exactly how we handle data. We encourage you to read it in full. If any aspect of our security posture is unclear, or if you require additional documentation, we are happy to provide further detail upon request.

HIPAA• Active
UK GDPR• Active
NHS DSPT• Active
Cyber Essentials• Active
Privacy Act 1988 (AU)• Active
02

Data Flow Architecture

A step-by-step breakdown of how your voice recording becomes a clinical note — and exactly where encryption, processing, and deletion occur at each stage.

Understanding exactly how data moves through the DigitalTCO platform is critical to evaluating our security posture. Below is a detailed, sequential account of the data lifecycle from the moment you press "Record" to the moment your completed clinical note is available in your account.

1
Audio Capture
When you initiate a recording within DigitalTCO, audio is captured directly from your device's microphone. The audio stream remains on your device during the recording session. No raw audio data is transmitted until you finalise the recording.
Local device buffer — no transmission
2
Encrypted Transmission
Upon completion of the recording, the audio file is encrypted on your device before transmission. The encrypted audio is transmitted to our processing servers via TLS 1.2+ (Transport Layer Security) over HTTPS. This ensures that the audio data is unreadable to any party intercepting the transmission between your device and our infrastructure.
TLS 1.2+ / HTTPS in transit
3
Speech-to-Text Transcription
The encrypted audio arrives at our processing environment, where it is decrypted within a secure, isolated compute instance. The audio is passed to our speech recognition engine for transcription. This transcription process occurs within a sandboxed environment with no persistent storage — the audio exists in volatile memory only for the duration of processing.
AES-256 at rest within processing environment
4
AI Clinical Note Generation
The raw transcription is passed to our clinical AI engine, which structures the transcript into a formatted clinical note according to your selected template and preferences. This process occurs within the same isolated compute environment. The AI engine does not retain any patient data between sessions and does not use your data to train, fine-tune, or improve any machine learning models.
Isolated compute — zero model training
5
Note Delivery & Storage
The completed clinical note is encrypted using AES-256 and stored in your account within our database infrastructure. The note is associated exclusively with your authenticated user account and cannot be accessed by any other user or by DigitalTCO staff without explicit authorisation and a documented, audited access event.
AES-256 at rest — user-scoped access
6
Audio Retention & Deletion
Following successful note generation and delivery, the retention of the original audio file depends entirely on your account settings. If you do not wish to save audio, it is permanently and irreversibly deleted. If you choose to save audio (e.g., as a record of an examination), it is securely stored alongside your other records.
User-controlled retention
Optional Audio Retention
By default, DigitalTCO operates a strict zero audio retention policy where the original voice recording is permanently deleted upon note generation. However, dentists can choose in their settings to save the audio for examination appointments or to keep an audio record of what went on in the appointment. If you do not want to save audio, nothing is retained. If you wish to save audio, we securely store the audio just as we would any other clinical record within the system.
03

Encryption Standards

Technical specifications of the encryption protocols applied to your data at every stage of the DigitalTCO platform.

Encryption is applied at every point in the data lifecycle. We use industry-standard and, where appropriate, above-industry-standard encryption protocols to ensure that patient health information is rendered completely unreadable to any unauthorised party — whether in transit between your device and our servers, at rest within our database infrastructure, or during processing within our compute environment.

Encryption in Transit

Protocol
TLS 1.2 and TLS 1.3
Cipher Suites
ECDHE-RSA-AES256-GCM-SHA384, ECDHE-RSA-AES128-GCM-SHA256
Certificate Authority
Issued by trusted public CA; pinned in application
Perfect Forward Secrecy
Enabled via ECDHE key exchange
HSTS
Strict-Transport-Security enforced with max-age of 31,536,000 seconds and includeSubDomains directive
Deprecated Protocols
SSLv2, SSLv3, TLS 1.0, and TLS 1.1 are disabled and rejected

Encryption at Rest

Algorithm
AES-256 (Advanced Encryption Standard, 256-bit key)
Key Management
Keys managed via cloud provider KMS with automatic rotation
Scope
All stored clinical notes, user account data, and metadata
Database-Level Encryption
Transparent Data Encryption (TDE) enabled at the database layer
Backup Encryption
All database backups are encrypted with the same AES-256 standard
Key Access
Encryption keys are never stored alongside encrypted data; access to keys is restricted to privileged service accounts with MFA

Encryption During Processing

During the brief period in which audio data is being processed (transcription and note generation), data exists only in volatile memory within an isolated compute instance. This instance is provisioned exclusively for the duration of the processing task and is terminated immediately upon completion. No data is written to persistent storage during processing. The compute environment is protected by network-level isolation, role-based access controls, and real-time monitoring.

04

United States: HIPAA Compliance

Detailed overview of our compliance with the Health Insurance Portability and Accountability Act for dental practices operating in the United States.

The Health Insurance Portability and Accountability Act (HIPAA) establishes the national standard for protecting sensitive patient health information in the United States. Any entity or technology that creates, receives, maintains, or transmits electronic Protected Health Information (ePHI) on behalf of a covered entity — such as a dental practice — is classified as a Business Associate and is subject to the full requirements of the HIPAA Privacy Rule, the HIPAA Security Rule, and the HIPAA Breach Notification Rule.

DigitalTCO operates as a Business Associate to dental practices using our platform. We take this classification seriously and have implemented comprehensive administrative, physical, and technical safeguards to meet and exceed the requirements set forth under HIPAA.

Business Associate Agreement (BAA)

We execute a Business Associate Agreement (BAA) with every US dental practice that uses the DigitalTCO platform. The BAA is a legally binding contract that establishes the permitted and required uses and disclosures of Protected Health Information (PHI) by DigitalTCO, our obligations to safeguard that information, and the procedures for breach notification. Our standard BAA is available for review prior to account activation. If your practice requires modifications or addenda to the standard BAA, our compliance team will work with your legal counsel to accommodate reasonable requests.

BAA Availability
A copy of our standard Business Associate Agreement is provided automatically during the US practice onboarding process. If you require a pre-signed copy for review, or if your legal team needs to negotiate specific terms, contact compliance@digitaltco.co.uk and we will arrange this promptly.

HIPAA Security Rule: Technical Safeguards

The HIPAA Security Rule (45 CFR Part 160 and Subparts A and C of Part 164) requires the implementation of technical safeguards to control access to electronic Protected Health Information. DigitalTCO implements the following technical safeguards:

Access Controls (§164.312(a)): Each user is assigned a unique identifier. Authentication is enforced via email and password with optional multi-factor authentication (MFA). Session tokens are time-limited and automatically expire after a period of inactivity. Role-based access controls ensure that users can only access their own clinical data.
Audit Controls (§164.312(b)): The platform maintains comprehensive audit logs of all access events, including user logins, note creation, note viewing, note editing, note deletion, and any administrative actions. Audit logs are immutable, timestamped, and retained for a minimum of six years in accordance with HIPAA requirements.
Integrity Controls (§164.312(c)): Mechanisms are in place to ensure that ePHI is not improperly altered or destroyed. All note modifications are versioned, and the original version is preserved in an immutable audit trail.
Transmission Security (§164.312(e)): All data transmitted between the user's device and DigitalTCO servers is encrypted using TLS 1.2 or higher. We do not transmit ePHI via unencrypted channels under any circumstances.
Person or Entity Authentication (§164.312(d)): The platform verifies the identity of any person or entity seeking access to ePHI before granting access. Authentication mechanisms include email verification, password hashing (bcrypt with salt), and optional TOTP-based MFA.

HIPAA Security Rule: Administrative Safeguards

Security Management Process (§164.308(a)(1)): DigitalTCO conducts regular risk assessments to identify potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. Risk assessments are performed at least annually and following any significant system change.
Workforce Training (§164.308(a)(5)): All DigitalTCO personnel with potential access to ePHI complete HIPAA awareness training upon hire and at least annually thereafter. Training records are maintained and available for audit.
Information Access Management (§164.308(a)(4)): Access to ePHI is granted on a least-privilege basis. Personnel are granted only the minimum level of access necessary to perform their specific job functions.
Contingency Plan (§164.308(a)(7)): DigitalTCO maintains documented data backup, disaster recovery, and emergency mode operation plans. These plans are tested at least annually.

HIPAA Security Rule: Physical Safeguards

DigitalTCO's infrastructure is hosted on cloud platforms that maintain rigorous physical security controls at their data centre facilities. These include 24/7 security personnel, biometric access controls, video surveillance, environmental controls (temperature, humidity, fire suppression), and redundant power systems. Data centres used for processing and storing US patient data are located exclusively within the United States.

HIPAA Breach Notification Rule

In the unlikely event of a breach of unsecured Protected Health Information, DigitalTCO will notify affected covered entities without unreasonable delay and in no case later than 60 calendar days following the discovery of the breach, as required under 45 CFR §164.410. Our breach notification procedures include identification and containment of the breach, risk assessment to determine whether the breach constitutes a reportable incident, notification to the affected covered entity with all information required under the Breach Notification Rule, and cooperation with the covered entity's own notification obligations to affected individuals and, where applicable, the Department of Health and Human Services (HHS) and media outlets.

US Data Residency

All data belonging to US dental practices — including audio during processing, clinical notes, user account information, and metadata — is processed and stored exclusively within data centres located in the continental United States. No US patient data is transferred to, processed in, or stored in any jurisdiction outside the United States. This includes transient processing; at no point during the data flow described in Section 2 does US patient data leave US-based infrastructure.

State-Specific Compliance Considerations

In addition to federal HIPAA requirements, several US states have enacted their own health data privacy laws that may impose additional obligations. DigitalTCO's architecture has been designed to accommodate the requirements of state-specific health information privacy statutes, including but not limited to the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), the Texas Medical Records Privacy Act, the New York SHIELD Act, and state-level audio recording consent requirements. DigitalTCO's zero audio retention policy and user-consent-driven recording model are designed to align with both one-party and all-party consent jurisdictions, though practices are responsible for obtaining patient consent in accordance with their applicable state law.

05

United Kingdom: GDPR, DSPT & Regulatory Compliance

Comprehensive overview of our compliance with UK data protection law, NHS frameworks, and dental regulatory requirements.

The United Kingdom has one of the most rigorous data protection regimes in the world, governed by the UK General Data Protection Regulation (UK GDPR) as retained in domestic law following the UK's departure from the European Union, the Data Protection Act 2018, and — for organisations handling NHS patient data — the NHS Data Security and Protection Toolkit (DSPT), the Digital Technology Assessment Criteria (DTAC), and Cyber Essentials certification. DigitalTCO has been designed from the outset to satisfy the requirements of each of these frameworks.

UK GDPR: Lawful Basis for Processing

Under Article 6 of the UK GDPR, the processing of personal data requires a lawful basis. DigitalTCO processes personal data on behalf of dental practices, who act as the Data Controller. DigitalTCO acts as a Data Processor. The lawful bases upon which processing is typically conducted include Legitimate Interests (Article 6(1)(f)) — the processing is necessary for the legitimate interests of the dental practice in maintaining accurate clinical records, subject to the Data Controller's own assessment — and, where applicable, Consent (Article 6(1)(a)) and Performance of a Contract (Article 6(1)(b)). For special category health data under Article 9, processing is conducted under Article 9(2)(h) — the processing is necessary for the purposes of preventive or occupational medicine, medical diagnosis, the provision of health care, or the management of health care systems and services.

Data Processing Agreement (DPA)

In accordance with Article 28 of the UK GDPR, DigitalTCO enters into a Data Processing Agreement with every UK dental practice. The DPA sets out the subject matter and duration of processing, the nature and purpose of processing, the type of personal data and categories of data subjects, and the obligations and rights of the controller. Our standard DPA is compliant with ICO guidance and is available upon request.

Data Subject Rights

DigitalTCO has implemented technical and organisational measures to support dental practices in fulfilling data subject rights requests under Articles 15–22 of the UK GDPR. These include the right of access (Article 15), right to rectification (Article 16), right to erasure (Article 17), right to restriction of processing (Article 18), right to data portability (Article 20), and right to object (Article 21). Requests are processed in accordance with the applicable time limits (one calendar month, extendable by two further months where requests are complex or numerous).

NHS Data Security and Protection Toolkit (DSPT)

The DSPT is a mandatory online self-assessment tool developed by NHS England for all organisations that access, process, or store NHS patient data. The DSPT requires organisations to demonstrate compliance with the National Data Guardian's 10 Data Security Standards, which cover areas including staff training, data handling, asset management, access controls, network security, continuity planning, incident response, and unsupported systems.

DigitalTCO submits an annual DSPT assessment and maintains a published "Standards Met" status. Our DSPT submission addresses all 10 standards and their associated evidence requirements, including the completion of annual data security awareness training by all staff, the maintenance of a comprehensive Record of Processing Activities (RoPA), documented data protection policies and procedures, technical measures including encryption, access controls, and patch management, and an incident response plan that is tested at least annually.

Digital Technology Assessment Criteria (DTAC)

The DTAC is a framework published by NHS England for assessing digital health technologies. While originally designed for apps, platforms, and medical devices used within the NHS, the DTAC criteria represent best practice for any digital health technology operating in the UK. DigitalTCO's architecture and data handling practices align with the DTAC's requirements across its five assessment domains: Clinical Safety, Data Protection, Technical Security, Interoperability, and Usability and Accessibility.

Cyber Essentials

Cyber Essentials is a UK government-backed certification scheme that sets out baseline security controls for organisations. DigitalTCO has achieved Cyber Essentials certification, which verifies that we have implemented controls covering firewalls and internet gateways, secure configuration, access control, malware protection, and patch management. We undergo the Cyber Essentials assessment annually and maintain current certification at all times.

Information Commissioner's Office (ICO) Registration

DigitalTCO is registered with the Information Commissioner's Office (ICO) as a Data Processor in accordance with the requirements of the Data Protection Act 2018. Our ICO registration details are available upon request.

International Data Transfers

DigitalTCO utilises distributed databases across the UK, the US, and the EU. The UK GDPR includes specific clauses that allow for safe and secure data transfers between these countries, making this practice completely legal and compliant. We ensure that all cross-border data transfers are protected by appropriate legal safeguards and specific agreements to guarantee the security of your patient data.

GDC Record-Keeping Standards

The General Dental Council (GDC) requires that dental professionals maintain adequate clinical records. DigitalTCO is designed to support compliance with the GDC's Standards for the Dental Team, specifically Standard 4.1 ("Make and keep contemporaneous, complete and accurate patient records"). Our AI-generated clinical notes are structured to capture the key information required for compliant dental records, including clinical findings, treatment provided, materials used, informed consent, and post-operative instructions. However, it is the clinician's responsibility to review and approve all AI-generated notes before they are finalised as part of the patient record.

06

Australia: Privacy Act & Health Records Compliance

How DigitalTCO meets Australian federal and state-level requirements for the handling of health information.

Australia's data protection framework for health information is primarily governed by the Privacy Act 1988 (Cth) and the 13 Australian Privacy Principles (APPs) set out in Schedule 1 of the Act. In addition, several Australian states and territories have enacted their own health records legislation that imposes additional or supplementary requirements, including the Health Records Act 2001 (VIC), the Health Records and Information Privacy Act 2002 (NSW), and the Health Records (Privacy and Access) Act 1997 (ACT).

Dental practices in Australia are classified as health service providers under the Privacy Act and are required to comply with the APPs when collecting, using, disclosing, and storing health information. DigitalTCO has been designed to support Australian dental practices in meeting these obligations.

Australian Privacy Principles (APPs) — Compliance Mapping

APP 1 — Open and Transparent Management: DigitalTCO maintains a publicly available privacy policy that describes how we collect, hold, use, and disclose personal information. This document constitutes part of that transparency commitment.
APP 2 — Anonymity and Pseudonymity: DigitalTCO does not require patients to interact with our platform directly. All data is collected and managed by the dental practice (the APP entity).
APP 3 — Collection of Solicited Information: DigitalTCO collects only the minimum personal information necessary to provide the clinical documentation service: voice recordings and the resulting clinical notes. We do not collect information that is not reasonably necessary for this purpose.
APP 5 — Notification of Collection: Dental practices using DigitalTCO are responsible for notifying patients about the collection of their information, including the use of AI-assisted documentation. DigitalTCO provides template notification language that practices can adapt for their own use.
APP 6 — Use or Disclosure: DigitalTCO uses personal information solely for the primary purpose for which it was collected — the generation of clinical notes. We do not use personal information for any secondary purpose, including direct marketing, analytics, or AI model training.
APP 8 — Cross-Border Disclosure: Where Australian patient data is processed or stored using infrastructure located outside Australia, DigitalTCO ensures that the overseas recipient is subject to equivalent privacy protections, in accordance with APP 8. We take reasonable steps to ensure that the overseas recipient does not breach the APPs in relation to the information.
APP 11 — Security of Personal Information: DigitalTCO implements technical and organisational measures to protect personal information from misuse, interference, loss, and unauthorised access, modification, or disclosure. These measures are described in detail throughout this document.
APP 11.2 — Destruction and De-identification: Personal information that is no longer needed for any purpose for which it may be used or disclosed under the APPs is destroyed or de-identified. Audio recordings are permanently deleted immediately after note generation.

Notifiable Data Breaches Scheme

Under Part IIIC of the Privacy Act 1988, DigitalTCO is required to notify the Office of the Australian Information Commissioner (OAIC) and affected individuals in the event of an eligible data breach — that is, a breach that is likely to result in serious harm to any individual whose personal information is involved. DigitalTCO maintains a documented breach response procedure that includes identification and containment, assessment of likely harm, notification to the OAIC and affected individuals within the prescribed timeframes, and remedial action to prevent recurrence.

Australian Health Practitioner Regulation Agency (AHPRA)

The Dental Board of Australia, administered by AHPRA, sets the Code of Conduct for dental practitioners, which includes requirements relating to clinical record-keeping. DigitalTCO supports compliance with these requirements by generating structured, contemporaneous clinical notes that capture the essential elements of each patient encounter. As with all AI-generated documentation, the registered dental practitioner retains full clinical responsibility for reviewing, amending, and approving all notes.

My Health Record

DigitalTCO does not currently integrate directly with the My Health Record system. Clinical notes generated by DigitalTCO can be exported and uploaded to My Health Record-connected practice management systems by the dental practice, in accordance with the My Health Records Act 2012 (Cth) and associated rules.

07

Rest of World: International Compliance

How DigitalTCO approaches data protection for dental practices operating outside the United States, United Kingdom, and Australia.

DigitalTCO is used by dental professionals in a growing number of jurisdictions. While our primary compliance focus is on the United States (HIPAA), the United Kingdom (UK GDPR, DSPT), and Australia (Privacy Act 1988), our security architecture has been designed to accommodate the data protection requirements of practices operating in other jurisdictions.

European Economic Area (EEA)

For dental practices operating within the European Economic Area, the EU General Data Protection Regulation (Regulation (EU) 2016/679) applies. DigitalTCO's data handling practices are aligned with GDPR requirements, including lawful basis for processing, data minimisation, purpose limitation, storage limitation, data subject rights, and cross-border transfer safeguards. Where data is transferred outside the EEA, Standard Contractual Clauses (SCCs) as approved by the European Commission are utilised.

Canada

The Personal Information Protection and Electronic Documents Act (PIPEDA) governs the handling of personal information in the Canadian private sector. Provincial legislation, such as Alberta's Health Information Act (HIA) and Ontario's Personal Health Information Protection Act (PHIPA), may also apply. DigitalTCO's data minimisation, consent, and security practices are consistent with the principles set out in PIPEDA and applicable provincial health information legislation.

New Zealand

The Privacy Act 2020 and the Health Information Privacy Code 2020 govern the handling of health information in New Zealand. DigitalTCO's practices are consistent with the 13 Information Privacy Principles set out in the Privacy Act 2020 and the specific rules for health information in the Health Information Privacy Code.

Middle East and Gulf Cooperation Council (GCC)

Several GCC states have enacted or are developing data protection legislation, including the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, the Saudi Arabia Personal Data Protection Law (PDPL), and the Qatar Law No. 13 of 2016 Concerning Personal Data Privacy. DigitalTCO will work with practices in these jurisdictions to ensure that our data handling arrangements meet local requirements, including data localisation requirements where applicable.

General Approach to International Compliance

For jurisdictions not specifically addressed in this document, DigitalTCO applies a "highest standard" approach: we apply the most protective set of controls from among our existing compliance frameworks (HIPAA, UK GDPR, Privacy Act 1988) to all users by default. This means that regardless of your jurisdiction, your data benefits from AES-256 encryption at rest, TLS 1.2+ encryption in transit, zero audio retention, strict access controls, and comprehensive audit logging. If your jurisdiction has specific requirements that are not addressed by our default controls, we will work with you to identify and implement any additional measures that may be required.

08

Infrastructure & Hosting

Details of the physical and cloud infrastructure that underpins the DigitalTCO platform.

DigitalTCO's production infrastructure is hosted on enterprise-grade cloud platforms that maintain extensive compliance certifications, including SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, PCI DSS Level 1, and FedRAMP. The specific hosting arrangements vary by region to ensure compliance with data residency requirements:

United States
US-based data centres (us-central, us-east). All US patient data remains within the continental United States at all times.
United Kingdom
Distributed across databases in the UK, US, and EU. Data transfers are conducted legally and securely in accordance with UK GDPR provisions.
Australia
Australia-based data centres (australia-southeast1 / Sydney). Australian patient data is processed and stored within Australia.
Other Regions
Routed to the nearest compliant data centre region, with data residency requirements assessed on a per-jurisdiction basis.

Network Architecture

Our network architecture implements defence-in-depth principles. Production services operate within a Virtual Private Cloud (VPC) with network segmentation that isolates processing, storage, and application layers. Ingress traffic is filtered through a Web Application Firewall (WAF) and distributed denial-of-service (DDoS) protection. Egress traffic is controlled via network access control lists and security groups. Internal service-to-service communication is encrypted and authenticated.

Redundancy and Availability

The platform is architected for high availability with redundancy across multiple availability zones within each region. Database infrastructure uses automated replication with synchronous writes to ensure data durability. Our target uptime SLA is 99.9%, and we maintain a public status page for real-time service health monitoring.

09

Access Controls & Authentication

How we control who can access what, and how identity is verified at every level of the platform.

User Authentication

Authentication Method
Email + password, with optional TOTP-based multi-factor authentication (MFA)
Password Requirements
Minimum 8 characters, complexity requirements enforced, checked against known breached password databases
Password Storage
Passwords are hashed using bcrypt with per-user salt; plaintext passwords are never stored or logged
Session Management
Authenticated sessions are managed via secure, HTTP-only, SameSite cookies with configurable expiry
Session Timeout
Automatic session expiry after 30 minutes of inactivity
Account Lockout
Progressive lockout after repeated failed authentication attempts, with CAPTCHA challenge

Internal Access Controls

Access to production systems and customer data by DigitalTCO personnel is governed by the principle of least privilege. Access is granted only to personnel whose job function requires it, is approved by a designated security lead, is logged in an immutable audit trail, requires multi-factor authentication, and is reviewed quarterly and revoked upon role change or termination. DigitalTCO personnel do not have the ability to view, read, or access the contents of clinical notes stored in user accounts under normal operating conditions. Access to raw data requires an explicit, documented, and approved access request with a stated justification.

10

Data Retention & Deletion

How long we keep data, what we keep, and how deletion works.

Voice Audio
By default, deleted immediately after successful note generation. Dentists can opt-in via settings to save audio recordings alongside their clinical records.
Clinical Notes
Retained in your account for as long as your account is active. Available for export or deletion at your request at any time.
Account Data
Retained for the duration of your subscription. In the UK, upon account closure, patient data is retained for 11 years (unless deletion is explicitly requested) to meet record-keeping requirements.
Audit Logs
Retained for a minimum of 6 years (HIPAA) or as required by applicable regulation in your jurisdiction.
Payment Data
Processed by our PCI-DSS compliant payment processor. DigitalTCO does not store credit card numbers or payment credentials.
Support Correspondence
Retained for the duration of your subscription plus 12 months, then permanently deleted.

Right to Deletion

You may request the deletion of your clinical notes, account data, or any other personal information held by DigitalTCO at any time by contacting our support team or using the in-app data management tools. Deletion requests are processed within 30 calendar days. Upon deletion, data is removed from all primary storage systems. Data may persist in encrypted backup systems for up to an additional 30 days, after which it is permanently purged.

11

Sub-Processors & Third Parties

A transparent list of the third-party services that handle data as part of DigitalTCO's operations.

DigitalTCO uses a limited number of third-party sub-processors in the delivery of our service. Each sub-processor has been evaluated for security and compliance, is bound by a Data Processing Agreement (or equivalent contractual safeguards), and is subject to ongoing monitoring. We maintain a register of all sub-processors, which is available to customers upon request.

Sub-Processor Change Notification
In accordance with our DPA and BAA obligations, DigitalTCO will notify customers of any proposed changes to our sub-processor list at least 30 days in advance. Customers may object to the engagement of a new sub-processor if they have reasonable grounds to believe that the proposed sub-processor does not provide adequate data protection safeguards.

Our sub-processors fall into the following categories: cloud infrastructure providers (hosting and compute), speech-to-text processing engines, large language model providers (for clinical note generation), payment processing, email delivery, and customer support tooling. Each sub-processor processes only the minimum data necessary for its specific function. No sub-processor has access to the full dataset. Audio data is processed in isolation by the speech-to-text engine and is never passed to or accessible by any other sub-processor. No sub-processor uses DigitalTCO customer data to train, fine-tune, or improve their own models or services.

DigitalTCO records audio of clinical encounters for the purpose of generating clinical documentation. Because this process involves the recording of conversations between dental practitioners and patients, appropriate consent must be obtained. The specific consent requirements vary by jurisdiction and are the responsibility of the dental practice (as the Data Controller or Covered Entity) to implement. DigitalTCO provides the following guidance and resources to support practices in meeting their consent obligations.

United States

In the United States, audio recording consent requirements vary by state. Some states operate under one-party consent rules (where only one party to the conversation needs to consent), while others require all-party consent. Dental practices must ensure compliance with their state's applicable wiretapping or eavesdropping statute. In all cases, we recommend informing patients that AI-assisted documentation technology is being used and obtaining explicit verbal or written consent, documented in the patient record. DigitalTCO provides a sample consent form and notification script that practices can adapt for their use.

United Kingdom

Under the UK GDPR and the Data Protection Act 2018, dental practices must have a lawful basis for processing patient data, which includes audio recordings. Practices should update their privacy notice to include reference to the use of AI-assisted clinical documentation, ensure that patients are informed of the recording and its purpose, and provide patients with the opportunity to opt out. The GDC's Standards for the Dental Team require that patients are informed about how their information is used.

Australia

Under the Privacy Act 1988 and APP 5, dental practices must notify patients about the collection of their personal information. This includes informing patients that audio recordings are being made for clinical documentation purposes, the purpose of the recording, who will have access to the recording and the resulting notes, and how the recording will be handled after processing (i.e., immediate deletion). State and territory surveillance legislation may also apply. Practices should seek legal advice regarding the specific consent requirements in their jurisdiction.

Consent Resources Available
DigitalTCO provides template consent forms, patient notification scripts, and waiting room signage templates in our Customer Resources portal. These templates are available in English and are designed to be adapted by practices to suit their specific regulatory and clinical context. They do not constitute legal advice, and we recommend that practices have their consent materials reviewed by their own legal counsel.
13

Incident Response

Our procedures for identifying, containing, investigating, and reporting security incidents.

DigitalTCO maintains a documented Security Incident Response Plan (SIRP) that defines the procedures for detecting, responding to, containing, investigating, and recovering from security incidents. The plan is reviewed and updated at least annually and is tested through tabletop exercises and simulated incident scenarios.

Incident Classification

Security incidents are classified into severity levels: Critical (confirmed or suspected breach of ePHI/personal data with potential for serious harm), High (security event with potential to compromise data integrity or availability), Medium (security event with limited impact and no data exposure), and Low (anomalous activity requiring investigation but posing no immediate threat). Each severity level has defined escalation procedures, response timeframes, and communication protocols.

Notification Procedures

In the event of a reportable data breach, DigitalTCO will notify affected customers in accordance with the applicable regulatory timeframes: within 60 days under HIPAA, without undue delay (and within 72 hours to the relevant supervisory authority) under UK GDPR, and as soon as practicable under the Australian Notifiable Data Breaches scheme. Breach notifications will include a description of the nature of the breach, the categories and approximate number of individuals affected, the likely consequences of the breach, and the measures taken or proposed to address the breach.

14

Audit Logging & Continuous Monitoring

How we maintain visibility into every action taken on the platform and detect anomalous activity.

DigitalTCO maintains comprehensive audit logs that record all significant events within the platform. Audit logs are immutable (append-only), timestamped with UTC synchronisation, stored in a separate, access-restricted logging infrastructure, encrypted at rest, and retained for a minimum of six years. Logged events include user authentication events (login, logout, failed attempts), note creation, viewing, editing, and deletion events, administrative actions (user management, configuration changes), API access events, and system health and error events.

Continuous Monitoring

The platform employs real-time monitoring and alerting for anomalous activity, including unusual login patterns (geographic anomalies, time-of-day anomalies, multiple failed attempts), unexpected data access patterns, elevated API request volumes, infrastructure health metrics (CPU, memory, disk, network), and security event correlation. Alerts are routed to our on-call engineering and security team for triage and investigation.

15

Personnel Security

The measures we take to ensure that the people behind DigitalTCO are trustworthy and trained.

All DigitalTCO personnel with access to production systems or customer data are subject to background verification checks prior to the commencement of employment or engagement, confidentiality agreements and non-disclosure obligations, mandatory security awareness training upon onboarding and at least annually thereafter, HIPAA-specific training (for personnel handling US customer data), UK GDPR and data protection training (for personnel handling UK customer data), and role-specific access provisioning based on the principle of least privilege.

Access credentials are revoked immediately upon termination of employment or engagement. All company-issued devices are subject to endpoint protection policies including full-disk encryption, screen lock enforcement, and remote wipe capability.

16

Penetration Testing & Vulnerability Management

How we proactively identify and remediate security vulnerabilities.

DigitalTCO conducts regular security testing to identify and remediate vulnerabilities before they can be exploited. Our vulnerability management programme includes automated dependency scanning (continuous), static application security testing (SAST) integrated into our CI/CD pipeline, dynamic application security testing (DAST) performed at least quarterly, external penetration testing conducted by an independent, qualified third-party security firm at least annually, and remediation SLAs (Critical: 24 hours, High: 7 days, Medium: 30 days, Low: 90 days).

The results of penetration tests and vulnerability assessments are reviewed by our security lead and used to inform our security roadmap. Executive summaries of the most recent penetration test report are available to enterprise customers upon request under NDA.

17

Business Continuity & Disaster Recovery

How we ensure the platform remains available and your data remains safe, even in the event of a major disruption.

DigitalTCO maintains a Business Continuity Plan (BCP) and Disaster Recovery Plan (DRP) that are designed to ensure continuity of service and the protection of customer data in the event of a major disruption, including infrastructure failures, natural disasters, cyberattacks, and provider outages.

Recovery Time Objective (RTO)
4 hours — target time to restore platform availability following a major disruption.
Recovery Point Objective (RPO)
1 hour — maximum acceptable data loss, measured as the time between the most recent backup and the point of failure.
Backup Frequency
Continuous replication with point-in-time recovery capability. Full backups taken daily.
Backup Storage
Encrypted backups stored in a geographically separate region from the primary data centre, within the same compliance jurisdiction.
DR Testing
Full disaster recovery drill conducted at least annually. Tabletop exercises conducted quarterly.
18

Request Security Documentation

How to obtain our full security whitepaper, BAA, DPA, penetration test summary, or other compliance documentation.

We believe that transparency is a prerequisite for trust. If you require any of the following documents, please contact our compliance team and we will provide them promptly:

Standard Business Associate Agreement (BAA) — US practices
Data Processing Agreement (DPA) — UK, EU, and international practices
Full security whitepaper with technical architecture details
Most recent penetration test executive summary (available under NDA)
DSPT publication reference and submission status
Cyber Essentials certificate
Sub-processor register
Data Protection Impact Assessment (DPIA) template
Sample patient consent forms and notification scripts
Vendor security questionnaire completion (we are happy to complete your practice's or group's security questionnaire)
Security Package

Ready to Review Our Documentation?

Our compliance team will send you our full security package — including BAA, DPA, whitepaper, and any additional documents your practice requires — typically within one business day.

Request Security Package →

compliance@digitaltco.co.uk  |  Response within 1 business day