Your data. Your control.
How Functional LAB protects clinical information, how users retain control over their data, and how the platform is designed to remain portable if hosting providers change.
Data controller
Functional LAB acts as data controller for information collected through the platform in the course of providing rehabilitation, clinical monitoring and coaching services.
Hosting, database and software providers
Functional LAB relies on established cloud infrastructure, database, transactional-email and payment providers. Provider selection prioritises encryption in transit and at rest, geographic residency compatible with UK data-protection expectations, and contractual data-processing terms.
Data ownership and permitted use
Clients and clinics remain the owners of their clinical and operational data. Functional LAB uses this data only to deliver the service, keep it running, meet safety obligations and honour the agreed contract.
Data is not sold
Functional LAB does not sell client or patient data. Data is not shared with advertising networks or data brokers.
AI training
Client or patient data is not used to train foundation AI models. AI features operate on the current user's data at the point of use and do not contribute to third-party model training under our current provider agreements.
Data-hosting and backup locations
Primary hosting and database regions are documented internally and disclosed to clinic partners under NDA. Once the production region is confirmed for public disclosure it will be listed here.
Encryption
All traffic to Functional LAB is served over HTTPS with modern TLS. Databases and object storage are encrypted at rest by the underlying provider.
Role-based access controls
Every clinical read and write is guarded by role and, for clinicians, by caseload. Administrators may only see what their role allows; patients only see their own data.
Multi-factor authentication
TOTP-based multi-factor authentication is available to every account and is strongly recommended for administrators and clinicians.
Audit logging
Every clinical or security-relevant action is written to an append-only audit trail with actor, target, outcome, before/after diff, IP hash and timestamp. Audit records are not editable by application code.
Clinical-record locking and amendment history
Signed clinical notes are locked. Later changes are captured as formal amendments — the original version is preserved and the amendment history is visible on the record.
Backup and restoration
Backups are performed by the underlying database and object-storage providers on a schedule appropriate for the tier in use. Restoration is exercised periodically as part of production-readiness reviews.
Data-retention principles
Records are retained for as long as required to deliver the service and meet legal, contractual and clinical obligations. Retention rules are configurable per data category and reviewed periodically.
Data-export options
Administrators can export every collection they control as JSON or CSV, either individually or as a single ZIP bundle, with all secrets stripped. Individual patients can request a machine-readable copy of their record via the Data Subject Request workflow.
Account closure and data return
On account closure a portable export of the account's data is offered and the account is deactivated. Deletion follows the applicable retention rules for clinical records.
Wearable-data controls
Wearable-device connections are opt-in and revocable at any time. Metrics ingested from wearables are treated as clinical telemetry, subject to the same access controls and audit as other clinical data.
Key subprocessors
A live list of subprocessors (cloud hosting, database, email, payments, AI providers, wearables partners) is maintained internally and shared with clinic partners under NDA.
International data transfers
Where personal data is transferred outside the UK, transfers are governed by the safeguards offered by the underlying provider (Standard Contractual Clauses, UK Addendum, adequacy or equivalent).
Security incident contact
Suspected security incidents can be reported to security@functionallab.com. Reports are triaged against our internal incident-response process which includes a breach register with a 72-hour countdown.
Data-rights requests
Patients and clinic partners can raise access, portability, rectification or erasure requests via privacy@functionallab.com. Requests are tracked on the Data Subject Request queue with an SLA countdown.
Independent security testing
Independent penetration testing status is tracked internally. When a fresh report is available it will be summarised here.
Clinical-use approval status
Clinical production approval is pending. Until it is granted the platform must not be used with real patient-identifiable clinical information.
Email functional.lab25@gmail.com. Data-rights requests: functional.lab25@gmail.com.