(opens in a new tab)Amazon Web Services
Cloud infrastructure designed for high availability and scale. Confirm hosting locations for your market.
Trust & security
Security, privacy and clinical-record safeguards for cosmetic, aesthetic and laser clinics.

Security & privacy
Encryption, access controls and regular security testing help protect your clinic’s data and patient records.
Hosting and processing locations can depend on your market and the services your clinic uses. Ask us to walk through the relevant arrangements.
(opens in a new tab)Cloud infrastructure designed for high availability and scale. Confirm hosting locations for your market.
(opens in a new tab)Web application firewall (WAF) protection to help filter malicious web traffic.
Your clinic’s data is encrypted at rest and in transit, protecting it while stored and as it moves between systems.
Set user and location permissions around each team member’s work. Multi-factor authentication adds another layer of protection. Trusted-device and clinic-IP controls depend on enabled access features and your clinic’s configuration.
Security audits help us review how information is protected. We assess suspected data breaches and provide notifications where required.
We carry out penetration testing every year to identify security weaknesses. Ask our team about the testing scope and available evidence.
Clinical notes
Create clinical notes with a defined editing window. The author can edit a note on the day it is created. At midnight in the clinic’s local time, the note becomes read-only.
This helps your clinic maintain the integrity of its clinical records. The original remains in place, with later corrections or additions recorded separately as traceable amendments.
Explore clinical notes and markingsResponsible AI
AI can help with documentation. Your practitioner reviews the content and remains responsible for the clinical decisions.

Review the processing, retention and model-training terms for the AI services your clinic uses. Our team can help you confirm the relevant providers and settings.
AI-generated clinical content requires review and validation by a healthcare professional.
Practitioners review AI-generated clinical content and retain responsibility for diagnosis, prescribing and care.
Policies & evidence
A clear starting point for clinic owners, clinical leads and the people reviewing your software.
Detailed security and infrastructure information, available to approved users.
Visit trust centreOpens in a new tabInformation handling, access, retention and breach response.
Read policyReport a suspected vulnerability to our security team.
security@dappleos.comYes. Bring your jurisdiction, clinical services, data-residency requirements and security questionnaire to a demo. DappleOS can explain its published controls and documentation workflows. Your clinic and practitioners remain responsible for the requirements that apply in your market.
Confirm the hosting and processing locations relevant to your market with DappleOS. Requirements can depend on the services and connections your clinic uses. The Privacy Policy describes third-party processing, including overseas providers; do not assume all processing occurs in one country.
The Privacy Policy describes encryption of health information at rest and in transit, authorised access controls, multi-factor authentication, security audits and breach assessment and notification where required. Use the security portal and a demo to review the scope and evidence for your specific requirements.
Where enabled, trusted-device controls let your clinic apply access rules to recognised devices. Configured clinic IP addresses can also support device trust. These controls depend on your access features and settings, so review user permissions, device approval, blocked devices and session behaviour with our team before relying on a particular setup.
This page does not claim independent certification. If your procurement process requires certification, a particular audit report or another formal assurance, confirm that requirement with DappleOS before proceeding.
No software can determine your insurance cover. DappleOS’s documentation workflows can help you retain a clear treatment record and review its history. Confirm your insured activities, record-keeping obligations, notification requirements and any other conditions with your professional indemnity insurer. This page does not imply endorsement by an insurer.
Confirm the model-training, processing and retention terms for each AI service your clinic intends to use, including its providers and settings. Ask the DappleOS team for the relevant documentation before sending patient information. Practitioners review AI-generated clinical content and retain responsibility for clinical decisions.
The author can edit a clinical note on the day it is created. At midnight in the clinic’s local time, it becomes read-only. The original record is preserved, with subsequent corrections or additions recorded separately as traceable amendments. The practitioner remains responsible for making an accurate record and explaining a later change.
Yes. Bring your required retention periods, export requirements, recovery expectations and incident-response questions to the DappleOS team. Review the Privacy Policy and current security portal first, then confirm the relevant arrangements and supporting documentation. Do not assume a particular recovery time, export format or deletion timetable without that review.
Ask DappleOS about your clinic’s documentation and security questions, or book a demo to review specific requirements.
Amazon Web Services, AWS and the AWS logo are trademarks of Amazon.com, Inc. or its affiliates. Cloudflare and its logo are trademarks of Cloudflare, Inc.