At Lumina, security is foundational to how we build, deploy, and operate our platform. We understand that dental practices entrust us with sensitive patient information and critical business data and protecting that data is our highest priority.
Built on world-class infrastructure with security at every layer
Full compliance with UK data protection regulations and Data Protection Act 2018
All data stored exclusively in AWS London region and never leaves UK jurisdiction
Military-grade encryption for all data at rest and TLS 1.2+ in transit
Mandatory multi-factor authentication for every user account
Compliance Standards & Trusted Partners




Comprehensive documentation of our security practices and controls
As a UK-based company processing data for dental practices across the United Kingdom, we fully comply with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. Our commitment to data protection is embedded in every aspect of our platform design and operations.
Our infrastructure implements controls consistent with international healthcare security standards, including administrative safeguards (access controls, workforce training, incident procedures), physical safeguards (data centre security, equipment controls), and technical safeguards (encryption, audit controls, integrity controls, transmission security).
Our security controls are designed to align with NHS Data Security and Protection Toolkit (DSPT) requirements, making Lumina suitable for practices that work with or alongside NHS services.
All Lumina data is processed and stored exclusively within the AWS London region (eu-west-2). This ensures patient data never leaves UK jurisdiction, maintains compliance with UK data protection requirements, provides low-latency access for UK-based practices, and aligns with NHS data residency guidance.
We use Amazon Web Services (AWS) as our infrastructure provider. AWS maintains comprehensive compliance certifications relevant to healthcare:
We operate a multi-account strategy with strict separation between environments. This architecture ensures complete isolation between production, staging, and development systems.
| Environment | Purpose | Data Type |
|---|---|---|
| Production | Live patient-facing systems | Real patient data |
| Staging | Pre-production validation | Synthetic/anonymised data only |
| Development | Internal development and testing | Synthetic/anonymised data only |
Service Control Policies (SCPs) enforce organisation-wide security guardrails, preventing any accidental cross-environment access. Developers have no access to production resources or data. This means all internal development, testing, and experimentation occurs using synthetic data—real patient information is never used for development purposes.
All data stored within Lumina is encrypted at rest using AES-256 encryption, the same standard used by governments and financial institutions worldwide.
| Storage Type | Encryption Method |
|---|---|
| Patient Records | AES-256 via AWS-managed encryption |
| Documents & Files | AES-256 server-side encryption |
| Backups | Encrypted with same standards as source |
| Authentication Secrets | AWS Key Management Service with managed keys |
All data transmitted to and from Lumina is encrypted using modern cryptographic protocols. We enforce strict transport security across all connections.
Lumina uses AWS managed identity services for enterprise-grade authentication, providing bank-level security for all user accounts.
We implement fine-grained role-based access control (RBAC) with 58+ granular permission types. Every API request is authorised in real-time, with permissions evaluated based on user role, organisation, and specific resource being accessed. This ensures staff members only have access to the data and functions appropriate to their role within the practice.
Your data is never shared across organisations. Each organisation's data is completely isolated, ensuring that information from one organisation cannot be accessed by another. Within your organisation, access is controlled by the permissions granted to each user by your administrators.
All Lumina APIs are protected through multiple security layers, ensuring that only authorised requests reach our systems.
AWS Web Application Firewall (WAF) shields all APIs against OWASP Top 10 threats including SQL injection, cross-site scripting (XSS), and malicious request patterns. Attack attempts are logged, blocked, and analysed for security intelligence.
For system integrations, we implement secure API key lifecycle management:
We implement comprehensive backup strategies to protect against data loss, ensuring your practice can recover from any scenario.
| Mechanism | Description | Recovery Point |
|---|---|---|
| Point-in-Time Recovery | Continuous backups of all database tables | Any point in last 35 days |
| Real-Time Replication | Change capture for near real-time backup | Near real-time |
| Document Versioning | Complete document version history | All versions retained |
| Cross-Region Capability | Architecture supports multi-region if required | Regional failover ready |
Production database tables are protected against accidental deletion through multiple safeguards including infrastructure-as-code deletion policies and database-level deletion protection. Administrative changes require multi-person approval.
We implement automated retention policies that comply with healthcare regulations while respecting privacy principles.
| Data Type | Retention Period | Policy |
|---|---|---|
| Active Patient Records | Duration of subscription + legal requirement | Practice-controlled |
| Clinical Records | Minimum 11 years (adults), 25 years (children) | GDC guidance compliant |
| Audit Logs | 7 years | Compliance and investigation |
| Session Data | 24 hours after expiry | Automatic deletion |
| Temporary/Cache Data | 7 days maximum | Automatic TTL deletion |
After subscription cancellation, your data remains accessible for export for a minimum of 2 years. Full data export is available in standard formats at any time during this period.
Every action within Lumina is logged for security, compliance, and operational visibility. Our audit system captures the complete picture of system activity.
Audit logs themselves are protected with the same rigor as patient data:
Our security team operates continuous monitoring for unusual access patterns, failed authentication attempts, system performance and availability, and security-relevant events. Alerts are generated automatically and investigated promptly by our security team.
Our AWS Organisations structure ensures developers work exclusively with synthetic/anonymised data. No production credentials exist in development environments, and code cannot be deployed to production without passing through staging validation.
In the event of a security incident, we follow a structured response process designed to minimise impact, maintain transparency, and prevent recurrence.
We maintain detailed incident response runbooks and conduct regular tabletop exercises to ensure our team is prepared to respond effectively to any scenario.
We use a limited number of carefully vetted sub-processors. Each is bound by data processing agreements with equivalent security and privacy requirements.
| Provider | Purpose | Data Processed | Location |
|---|---|---|---|
| Amazon Web Services | Infrastructure | All service data | UK (eu-west-2) |
| Stripe | Payment processing | Payment information only | EU |
When practices choose to enable third-party integrations, data sharing is carefully controlled:
While we implement comprehensive security measures at the platform level, practices also play an important role in maintaining data security.
| Lumina Responsibility | Practice Responsibility |
|---|---|
| Platform security & infrastructure | User account management |
| Encryption & key management | Password security & MFA compliance |
| Backups & disaster recovery | Staff security training |
| Security monitoring & response | Regular access reviews |
| Compliance tools & capabilities | Compliance processes & policies |
| Incident response & notification | Timely incident reporting |
Ensure all staff complete mandatory MFA setup during account creation
Use unique, strong passwords for Lumina accounts
Regularly audit user permissions and remove leavers promptly
Educate staff on recognising phishing and social engineering
Keep devices updated with current software and security patches
Contact us immediately if you suspect unauthorised access
If you have questions about our security practices or would like additional information for your due diligence process, we're here to help.
Report a security concern or request information
security@luminadental.comWe can provide additional documentation, complete security questionnaires, or arrange calls with our technical team for enterprise practices.
This policy is reviewed and updated at least annually, or whenever significant changes are made to our security practices. Last updated: February 2026.