Effective date: 1 November 2026 (subject to legal review)
Last updated: 25 October 2026
Sienna Health (“Sienna”, “we”, “us” or “our”) provides browser-based, locally deployed electronic health record and practice-management software for healthcare practices.
The service is operated by Obed Klein, a sole proprietor trading as Sienna Health, with a business address at Steingruberstr. 5, 90579 Langenzenn, Germany.
Contact: support@sienna.health
This Policy explains how Sienna processes personal information in connection with its public website, customer relationships, subscriptions, operational heartbeat and technical support. It does not replace the privacy notice of a clinic using Sienna for patient care.
Sienna is designed to run on hardware within the healthcare practice’s own premises. Clinicians and authorised staff access the locally hosted application using a web browser.
In ordinary operation:
Sienna’s central server receives clinic contact information and operational heartbeat information, as described below. The service is also advertised with standard remote support. Under the current intended configuration, support does not provide Sienna with access to the contents of patient records. We will update this Policy if the deployed technical permissions change that boundary.
The local-first design may allow the application to remain accessible without an external internet connection where the deployment supports this. Availability still depends on local hardware, power, local networking, configuration and connected services.
We may process the clinic’s name, business address, business email, telephone number, names and contact details of professional representatives, account/licence identifiers, subscription selection, quotation and invoice details, support correspondence and related customer-service records.
We also collect the details you submit through the guided-demo form on this website, such as your name, email address, telephone number, practice name, preferred time and message. We use those details only to respond to your enquiry and arrange the demo you requested.
A customer installation sends an authenticated operational heartbeat to Sienna’s central server in Germany. Depending on the deployed version, the heartbeat may include:
The central server may also see the source IP address and ordinary connection logs. Heartbeat identifiers and network information may be linked to a particular clinic or installation and therefore may constitute personal information or confidential business/security information in some circumstances.
The heartbeat is intended for service-health monitoring, diagnostics and support. It is not designed to contain patient names, clinical notes, diagnoses, prescriptions, laboratory results or patient records.
We do not intentionally use website advertising trackers or analytics trackers. Website and infrastructure providers may nevertheless process ordinary technical logs needed for operation, error diagnosis, abuse prevention and security, which can include IP address, timestamp, requested URL, browser or device information and error details. The actual logging depends on the deployed hosting configuration.
A clinic may use Sienna to maintain names, contact details, medical histories, clinical notes, diagnoses, prescriptions, laboratory results, medical images, uploaded documents, insurance or medical-aid details, billing records and information about minors.
These records are stored in the clinic’s environment and are controlled by the clinic. Sienna does not routinely receive them on its central server. If a clinic separately discloses record content to Sienna in a support ticket or otherwise, the clinic must avoid sending more information than is necessary and the parties must handle the disclosure under the applicable contract and law.
Where the EU General Data Protection Regulation (GDPR) applies, Sienna processes customer and technical information for the following purposes and legal bases, as appropriate to each activity:
The clinic is responsible for selecting and documenting its own lawful basis for collecting and using patient health information. Sienna’s Privacy Policy does not itself provide that lawful basis for a clinic.
We use customer and operational information to:
We do not sell patient information or use patient health information for advertising. We do not currently use AI systems to process patient information as part of the service.
We may make information available to:
We do not disclose patient records to third parties as part of the normal central heartbeat process because the heartbeat is not intended to contain patient records.
Sienna is operated from Germany and its central heartbeat server is in Germany. Clinic contact information and heartbeat data sent to that server are processed in Germany. The customer’s patient records are designed to remain within the customer’s local practice environment. The parties must reassess this description if remote support, a new feature, a backup arrangement or another service causes patient data to be accessed or transferred across borders.
We keep customer and technical information only for as long as reasonably necessary for the purposes described in this Policy, subject to legal recordkeeping obligations and the need to establish or defend legal claims.
We are finalising specific retention periods for the following categories, taking into account operational need, legal recordkeeping obligations and data minimisation:
We will update this Policy with the confirmed periods. Patient-record retention is managed by the clinic. The software currently soft-deletes or archives a record; it remains recoverable in the database. A user-interface deletion is not permanent erasure. The clinic must account for this when determining retention and responding to patient requests.
Sienna reports using individual accounts, role-based access, audit logs, encrypted network connections and encryption at rest. The actual protection depends on the deployed version, configuration and the division of responsibilities between Sienna and the clinic.
Because the application is installed locally, the clinic is responsible for physical security, power, local network security, user accounts, device security and the practice’s backups. No system can be guaranteed completely secure. A backup timestamp or checksum is not proof that a backup can be restored; restoration should be tested.
Depending on the applicable law, individuals may have rights to access, correct, delete, restrict or object to processing, request portability, withdraw consent, or lodge a complaint with a supervisory authority.
For patient records, requests should ordinarily be directed to the clinic responsible for those records. Sienna will reasonably assist the clinic where a request concerns information Sienna actually processes on its behalf. For customer contact, account or heartbeat information processed by Sienna, contact support@sienna.health.
We may need to verify identity and authority before responding. A deletion request does not mean Sienna can permanently erase a patient record stored in the clinic’s database; the clinic must assess the applicable legal requirement and the software’s available deletion mechanism.
Sienna does not operate patient accounts or collect patient information through its own intake forms under the current service. A clinic may maintain records concerning minors in its local installation. The clinic is responsible for complying with laws concerning children, parental or guardian authority, confidentiality and healthcare records.
Sienna does not intentionally use advertising or behavioural analytics trackers on the public website. The website may use strictly necessary technical storage or receive server logs needed for security and operation. If non-essential cookies, analytics or third-party embeds are introduced, we will update this Policy and any required consent mechanism before deployment.
If Sienna becomes aware of a security incident affecting personal information it processes, it will investigate, take reasonable steps to contain and remedy the incident, and make notifications required by applicable law and contract. The healthcare provider remains responsible for its own legal notifications concerning patient records it controls, with assistance from Sienna where applicable.
For privacy questions or complaints, contact support@sienna.health. Individuals may also contact the competent data protection authority where they have a right to do so.
We may update this Policy to reflect changes in the service, data flows, applicable law or business practices. We will post the updated version and change the “Last updated” date. We will provide additional notice or obtain consent where required by law.
Sienna Health
Operated by Obed Klein, sole proprietor
Steingruberstr. 5, 90579 Langenzenn, Germany
Email: support@sienna.health
Choose the entry point that fits your stage: a quick sandbox, a guided demo, or a practice-fit discussion for your clinic.
Walk through consultation, records, scheduling, and billing with the team.
Explore the product with sample patient data and no sales call.