Built with security at the centre
The platform includes layered controls designed to protect clinic accounts, patient information and programme access throughout the prescription and delivery workflow.
Security designed around the prescription and delivery workflow
Each control exists to protect a specific part of the journey — from a practitioner logging in, to a patient opening a programme.
Data encryption
Sensitive patient and programme data is encrypted, reducing exposure if a system is ever compromised.
Staff multi-factor authentication
An additional verification step protects clinic accounts beyond a password alone.
Secure patient verification
Patients confirm their identity with a six-digit code before any programme content is shown.
Cryptographically secure links
Programme links are generated to be unguessable and are scoped to a single programme.
Token hashing & rotation
Access tokens are hashed and automatically replaced whenever a programme is resent.
Account lockout
Repeated failed sign-in attempts trigger a temporary lockout to slow credential-guessing attempts.
Rate limiting
Requests to sensitive endpoints are rate-limited to reduce automated abuse.
Audit logging
Clinical changes and account activity are logged to support internal review and accountability.
Role-based access
Practitioners, receptionists and administrators are limited to the access their role requires.
Multi-clinic data isolation
Each clinic's data is kept logically separate from every other clinic on the platform.
Secure media delivery
Images, videos and PDFs are served through controlled, access-checked delivery.
XSS protection & sanitisation
User-entered content is sanitised to reduce cross-site scripting risk.
Security headers
Standard browser security headers are applied across the platform.
Strong password requirements
Password policies are enforced for every staff account.
Configurable session timeouts
Clinics can set how long an inactive session remains signed in.
Email log redaction
Sensitive content is redacted from delivery logs where it is not required.
Login-attempt logging
Sign-in attempts are logged to help identify unusual account activity.
Patient-page indexing controls
Patient programme pages are marked noindex and nofollow so they are not surfaced by search engines.
Consent & acknowledgement logging
Relevant consent and acknowledgement actions are recorded against the patient event timeline.
Compliance-ready controls, clinic-owned responsibility
PhyseoApp is designed with healthcare data protection in mind and includes features that support responsible data protection practices. It is built to support clinic security and compliance requirements, including features designed to support GDPR-related obligations.