Security & compliance,
built for cardiac data.
CardioBridge handles some of the most sensitive data in healthcare. Security, data protection and clinical governance are engineered into the platform, not bolted on — here is exactly how we keep patient data safe.
- TeqDr is CQC-registered
- ICO-registered
- GMC consultants
- DCB0129 / DCB0160
- EU/UK data residency
- WCAG 2.1 AA (partial)
- Serving clients globally
All patient data lives in an EU-hosted clinical system of record. Identity and pipeline state sit in the UK (London). The frontend is a static app that holds zero patient data — so protected health information never leaves the EU/UK.
We serve patients and clients globally, working with a worldwide network of consultant cardiologists — including clinicians registered locally in the markets we serve. Wherever an ECG is recorded, it is read by an appropriately registered consultant and the data comes back to the same EU/UK footprint described above.
What protects your data today.
EU / UK data residency
We serve patients and clients globally, but the data always lands in the same place. Our clinical system of record is EU-hosted and our identity/pipeline data sits in the UK (London). No clinical content — ECGs, reports or patient records — is stored outside the EU/UK, wherever in the world the ECG was recorded. The one exception is email delivery logs, held in the US by our email provider under Standard Contractual Clauses: a name and an address, never clinical detail. Personal data transferred from the EEA to the United Kingdom relies on the European Commission's adequacy decision for the UK, renewed on 19 December 2025 and valid until 27 December 2031.
Encrypted in transit and at rest
HTTPS everywhere, with data encrypted in transit and at rest across every layer. Calls to the clinical system flow only through EU edge functions — never the browser or a US server.
Tenant isolation by default
Row-Level Security is enforced on every database table. An organisation sees only its own patients and reports; a patient sees only their own results. Isolation lives in the database, not just the UI.
Role-based access control
Two layers of route protection plus per-persona guards mean each role — patient, organisation, cardiologist, ops, admin — reaches only what it should. The database is the real boundary.
Multi-factor authentication
Multi-factor authentication is enforced on the administrative consoles behind CardioBridge — hosting, database, source code, payments, email and identity. The accounts that could reach production are the accounts we protect hardest.
Audit logging & attribution
Access to clinical records is logged with the user, record and timestamp, and every report carries named-consultant attribution — evidence for our clinical-safety case, data-subject requests and internal monitoring.
Data minimisation & retention
We hold the minimum data required. Working ECG data is purged from our pipeline 90 days after a report is issued, uploaded trace files are deleted once delivered to the clinical record, and we honour data-subject erasure requests. The clinical record itself is retained in the system of record under normal medical-records retention.
Secure engineering
Every change ships through CI with automated static analysis (CodeQL), dependency and secret scanning, and a full test suite. Sandbox and production environments are fully separated.
Payments without card data
Billing runs through hosted checkout and invoicing — we never store card numbers. Card data is handled entirely by our PCI-DSS-compliant payments provider. No payment form is embedded anywhere in CardioBridge: every payment, card update and invoice is a redirect to Stripe's own page, so card details are only ever typed into Stripe and never into us.
Hardened in the browser
A strict content-security policy allowlists every script, style and connection the site is permitted to make and blocks everything else, and payment forms may only submit to Stripe. HTTPS is enforced by HSTS, the site refuses to be embedded in a frame, and content-type sniffing is off. None of this requires taking our word for it — it is all publicly inspectable.
Consent you can withdraw
Analytics and advertising tags load on our public website only, never on a signed-in or patient-facing page, and only after you opt in across the UK and EEA. You can change or withdraw that choice at any time from “Cookie settings” in the footer of every page — withdrawing is exactly as easy as giving, and takes effect immediately. We honour Global Privacy Control and Do Not Track as an opt-out everywhere.
Responsible disclosure
We publish a security contact under RFC 9116 at /.well-known/security.txt, and we monitor it. Found a vulnerability? Report it privately to cardiobridge+security@teqdr.com and give us a reasonable chance to fix it before disclosure — we would far rather hear from you than from someone else.
Registered, governed, accountable.
The legal entity behind CardioBridge is Hippocrates Digital Ltd, trading as TeqDr — registered in England and Wales, company number 13280534. Everything below is held today and verifiable; anything we are still working toward is in the roadmap band underneath, never mixed in with it.
TeqDr is CQC-registered
Hippocrates Digital Ltd, trading as TeqDr, is registered with the Care Quality Commission for the regulated activity of diagnostic and screening procedures. Provider ID 1-21722605626.
View on the CQC register ↗ICO-registered
Registered with the Information Commissioner's Office as a data controller (Hippocrates Digital Ltd). ICO registration ZB044070.
View on the ICO register ↗GMC-registered consultants
Every ECG is read and signed by a named consultant cardiologist — AI never issues a report.
Clinical safety cases
Governed under the DCB0129 and DCB0160 clinical-safety standards, with a signed clinical safety officer.
Data Protection Officer appointed
A Data Protection Officer is appointed and contactable at cardiobridge@teqdr.com — meeting Article 13(1)(b) of the UK and EU GDPR, and serving as our designated Data Protection Officer under Singapore's Personal Data Protection Act.
Caldicott Guardian appointed
A named Caldicott Guardian is accountable for how patient-identifiable information is used and shared, and we operate to the eight Caldicott Principles — including the seventh, that the duty to share information for a patient's care matters as much as the duty to protect it. An ECG nobody can read is a safety problem, not a privacy success.
Accessibility — WCAG 2.1 AA
We self-declare PARTIAL conformance with WCAG 2.1 Level AA, and name what is unverified rather than round it up: no independent audit, no automated check in our build yet, and the signed-in workstation and issued PDF reports not yet fully assessed.
Read our accessibility statement →Building toward the standards enterprise & NHS buyers expect
Beyond the registrations and clinical-safety cases above, we are actively working toward the following certifications. These are on our roadmap — we will publish each one here as it is achieved.
UK government cyber-security baseline.
NHS Data Security & Protection Toolkit, for supplying NHS organisations.
Information-security management system certification.
NHS Digital Technology Assessment Criteria for health apps.
Rights that follow you across borders.
We serve clients in markets whose privacy law asks for specific statements, so our privacy policy carries those statements by name rather than a single UK-shaped one. These are published, not available on request.
A Personal Information Collection Statement meeting DPP1(3) of the PDPO — what we collect, why, the classes of person it may be transferred to, and how to request access or correction.
A grievance officer for complaints under the Digital Personal Data Protection Act 2023, contactable at cardiobridge@teqdr.com.
POPIA requests, including access and objection, are routed to our Information Officer at the same address.
Our designated Data Protection Officer under the PDPA is published and contactable, as the Act requires.
The full text of each sits in section 13 of our Privacy policy.
Who we work with.
Every sub-processor involved in running CardioBridge — including the two that only ever see our public website — with what each processes, where it sits, and the security credentials it holds in its own right.
Semble
EUClinical system of record — patient records, ECG documents and signed reports
- ISO/IEC 27001:2022
- Cyber Essentials Plus
- NHS DSPT
- PCI DSS v4.0.1
- GDPR
- ICO-registered
Our patient records sit with a UK clinical-software provider certified to the standards the NHS itself asks for. Semble adds third-party penetration testing, a web application firewall, DDoS protection, endpoint detection and response, data-loss prevention and least-privilege access control, under a named Data Protection Officer.
Semble Trust Center ↗Supabase
UK · LondonAuthentication, pipeline & billing state, edge functions, ECG file staging and in-flight patient data
- SOC 2 Type 2
- ISO 27001
- HIPAA (under BAA)
All data encrypted at rest with AES-256 and in transit with TLS, regular third-party penetration tests, continuous dependency and secret scanning, DDoS protection and point-in-time recovery backups. Our project is pinned to the London region, so identifying data never leaves the UK.
Supabase security ↗Stripe
GlobalHosted checkout & invoicing — no card data stored by CardioBridge
- PCI DSS Level 1 Service Provider
- SOC 1 Type II
- SOC 2 Type II
- SOC 3
- EU–US DPF (UK extension)
The highest certification level in the payments industry, validated annually by an independent assessor. Card numbers are AES-256 encrypted inside a segregated environment, TLS 1.2+ is enforced, and Stripe runs a public bug-bounty programme alongside regular penetration testing and red-team exercises. A card number never reaches CardioBridge.
Stripe security ↗Resend
EU send · US logsTransactional & account email
- SOC 2 Type II
- GDPR
- EU–US DPF (UK extension)
We send from Resend's Ireland region, but Resend stores account data and delivery logs in the United States — so we hold a Data Processing Agreement with Standard Contractual Clauses, and Resend is certified under the EU–US Data Privacy Framework and its UK extension. Only a name and email address are ever involved: no ECG data, no reports, no clinical detail.
Resend security ↗Base44
US · no PHIStatic frontend hosting — zero patient data at rest
- SOC 2 Type II
- ISO 27001
- GDPR
Independent OWASP-based penetration testing, pre-deployment secret and authentication scanning, row-level security and a third-party risk-management programme. Base44 serves the public website and application shell only — every request for clinical data goes to our UK backend, not to the host.
Base44 Trust Center ↗GitHub
US · no PHISource-code hosting
- SOC 1 Type 2
- SOC 2 Type 2
- ISO/IEC 27001:2022
- CSA STAR Level 2
- PCI DSS AoC
GitHub also publishes a CSA CAIQ self-assessment and quarterly bug-bounty reports. It holds our source code and CI pipeline — no patient data of any kind is stored there, and every change ships through automated static analysis, dependency and secret scanning before release.
GitHub Trust Center ↗Public-website analytics only (Analytics & Tag Manager) — never the clinical application
- ISO/IEC 27001
- Consent Mode v2
Google Analytics is inside Google's ISO/IEC 27001 certification, audited by EY CertifyPoint. We list it because it is a sub-processor even though it never touches clinical data: it loads only on public marketing pages, only after you opt in across the UK and EEA, and our code refuses to send a page view for any signed-in route.
Google Analytics ISO 27001 ↗Meta
US · no PHIAdvertising pixel on the public website — never the clinical application
- EU–US Data Privacy Framework
- UK transfer addendum
- Advertising tool, not a security vendor
This one is an advertising pixel for campaign attribution, and we are not going to dress it up as anything else. It exists on public pages only, loads nothing at all until a UK or EEA visitor opts in, honours Global Privacy Control, and is blocked from every signed-in and patient-facing route in code.
Meta Data Privacy Framework ↗GoDaddy
US · no PHIDNS
- ICANN-accredited registrar
- WebTrust-audited certificate authority
- Publishes no SOC or ISO 27001 audit
GoDaddy states plainly that it is not audited for SOC or SSAE 18, and we would rather show you that than leave it off the list. Its scope here is a domain name and its DNS records — it holds no patient data, no credentials and no clinical content, and any change to those records is protected by registrar lock and multi-factor authentication on our account.
GoDaddy Trust Center ↗These are our providers' certifications, not ours — ours are listed above. Every credential here comes from the provider's own public trust page, linked on each card and last verified on 30 July 2026, and we hold a Data Processing Agreement with each provider. A Data Processing Agreement with CardioBridge is available for business customers. See our Privacy policy for how we process personal data.
Documents on request.
Running a security or clinical review? These are written, signed and current — not a promise to produce something later. We share them with business customers under NDA. Tell us what your team needs and we'll get it over.
Request documentation- Data Processing Agreement (DPA)
- Security & data-protection questionnaire
- Records of Processing (ROPA) & DPIA summaries
- Legitimate Interests Assessment (LIA)
- Cross-border transfer assessment
- Clinical retention policy
- Data-subject rights procedure
- Breach notification clocks, by market
- ICO Accountability Framework self-assessment
- Named sub-processor list
Questions about security?
Our team can walk your clinical, IT or procurement stakeholders through our controls in detail.
Talk to our team