Heimdall service information
Privacy notice
What information Heimdall uses, where optional features send it and how to raise a privacy request.
Notice version 2026-11-04-demo-2
Draft for demonstration review. These notices describe the current demonstration and require organisational and legal review before use with real patient information.
The supplier or privacy-contact details are not yet complete. Use synthetic patient information only and obtain the responsible organisation’s details before providing real information.
The demonstration label identifies intended use; it does not itself isolate a database or establish regulatory approval.
Responsible organisation and contact
- Legal entity
- Not yet confirmed
- Business address
- Not yet confirmed
- Privacy contact
- Not yet confirmed. Ask the organisation that gave you access to identify its privacy contact before sharing real personal information.
The EMS or hospital supplying your access must identify its responsibilities for care records. The software supplier’s role depends on its agreement and actual processing. Those responsibilities must be confirmed before real patient use.
Information and purposes
- Accounts: staff identity, role, organisation and session information support sign-in, permissions and account administration.
- Cases: the application can process patient identity, clinical descriptions, next-of-kin information, destinations, decisions and observations for case coordination. Use synthetic values in this demonstration.
- Activity: case events, access and security events, unit/session membership and support activity support traceability and service operation.
- Devices: browser information and notification subscriptions support delivery to devices you enable.
- Optional voice and location: microphone audio, transcripts, speech text and location support the functions you choose to start.
Information can come from the user, their organisation, an authorised receiving organisation or an assigned device. A fake patient name does not anonymise a real national ID, voice, address or sensor reading.
Who receives information
Access depends on the current role, organisation, crew context and case participation. Destination changes can end a hospital’s current case access. Hosting and authorised support providers may process information under the responsible organisation’s arrangements; the approved vendor list and hosting locations still require confirmation.
Google receives location/search inputs for mapping, discovery and routing. Browser push services process notification-delivery information. These services can involve infrastructure outside South Africa. Keep patient identity and clinical narrative out of map searches.
See the Google Privacy Policy for Google’s processing. The responsible organisation must assess the applicable vendor and international-transfer arrangements before real data is used.
Astrid and your microphone
Wake and speech-activity detection run locally in the browser. Captured audio is sent through Heimdall to Groq for transcription. Eligible transcript text can be sent for command classification. Text for speech synthesis is also sent to Groq and can contain requested case information.
Heimdall’s durable speech cache is restricted to predefined static prompts. Dynamic patient read-back bypasses that cache. This does not establish the provider’s retention settings: review Groq’s data handling and the organisation’s actual settings.
Enable voice only when appropriate for the people nearby. Use Turn off Astrid to stop listening and playback. Manual operation remains available. Turning off cannot recall information already sent to a provider.
Location and notifications
Your device-alert choice is remembered for your account, organisation and role in this browser. After browser permission is granted, Heimdall can complete activation automatically and restore alerts on later sign-ins. Logout pauses delivery. Enabling for another account requires confirmation before an existing subscription moves. Foreground sound may need another click after reopening the app.
Live ambulance location requires an explicit start for the current active transport. The browser requests location permission; sharing pauses in a hidden tab and stops on a transport change/end or when you stop it. An in-flight update and previously recorded positions cannot be recalled by the stop control.
Device notifications require explicit activation and browser permission. Background messages use generic wording, but people with device access may see them. Turn off device alerts removes this browser’s subscription where supported; in-app records remain available.
Review explanations and off controls in Privacy settings. A browser permission or feature choice does not establish permission on behalf of a patient.
Retention and your requests
Record-specific retention periods, legal holds, provider retention and backup schedules must be approved by the responsible organisation. Alert expiry and case archiving are application behavior, not a universal legal retention policy. Do not submit real clinical information until these arrangements are established.
You may raise an access, correction, objection or deletion request with the responsible organisation. It must verify your identity or representative authority, assess the applicable rights and retention obligations, and explain its decision. A request does not automatically permit destruction of a medical record.
Use the privacy contact above when confirmed. Avoid attaching a medical record or national ID to an initial general enquiry. Ask for a secure submission channel. Complaints may also be raised with the South African Information Regulator.
Children and information security
Children’s information, emergency/incapacity arrangements and the applicable care-processing basis require the healthcare organisation’s approved process. A staff member’s acknowledgement of this notice does not replace that process.
Authentication, tenant/case access checks and audit mechanisms support information protection. Outstanding security and operational work still requires review before real patient use. This notice does not certify POPIA compliance, medical-device approval or clinical safety. Report suspected exposure immediately to the supplying organisation.