H
Hospital AI Assistant
Hospital workspace
Privacy & Data Protection

Privacy Policy

This policy describes how information is processed when authorized hospital personnel use Hospital AI Assistant and its related services for frontline work, patient/OPD documentation, staff coordination, facility maintenance, and voice-assisted workflows.

App: Hospital AI AssistantEffective: 1 November 2026Last updated: 1 November 2026

1. Overview and hospital responsibility

Hospital AI Assistant is a voice-first workplace tool for hospitals and clinics. It supports patient registration and OPD-related documentation for authorized personnel, facility complaints, work orders, employee availability, duty sessions, assignment, supervisor verification, and operational reporting. It is intended to assist frontline processes, not replace a hospital's clinical judgment or existing hospital management system.

The hospital or healthcare organization that deploys the service generally determines what patient, employee, and operational information is entered, who may use it, and the lawful basis for processing. The service operator processes that information to provide the requested functions and according to applicable agreements and legal requirements. Hospitals are responsible for providing appropriate notices and obtaining permissions or consents where required.

2. Information we collect and process

Depending on enabled modules and an individual's access, the service may process:

Hospital and account detailsFacility name, account identifiers, contact details, user roles, authentication/session records and permissions.
Employee recordsNames, designations, assigned departments, work contact details, availability sessions, recorded duty hours, task assignments and progress.
Patient and clinical informationPatient identifiers and contact details, registration details, OPD encounters, doctor assignments, consultation notes, prescriptions and related authorized records where features are enabled.
Facility and operational recordsComplaints, work orders, reported locations, priorities, assigned personnel, work histories, approvals, rework, incidents and supervisor notes.
Voice and AI contentAudio voluntarily recorded for a voice action, resulting transcripts, extracted fields, questions, responses and confirmed records.
Images, documents and attachmentsPhotos and files deliberately captured or selected, including patient or employee documents and operational evidence, as allowed by the account's modules.
Device and notification informationDevice push tokens, platform details and application diagnostic or error information necessary for notifications and service operation.
Security and audit informationAuthentication activity, access logs, role changes, record changes and security-related events.

Health information is sensitive. Authorized users should enter only the information needed for their work and avoid including unrelated personal or clinical details in voice recordings or notes.

3. App permissions and device access

Microphone

The microphone is used when a user actively starts voice reporting, searching, documentation or task updates. Recorded audio may be transmitted for speech-to-text and AI interpretation. The application is not intended to continuously record ambient conversations.

Camera, photos and documents

Where the relevant feature is available, users may select or capture photos, identification/supporting documents or work evidence. The app uses the selected files to provide the requested workflow.

Notifications

With device permission, the app may register a push-notification token and use it to deliver work-related alerts, such as assignments or operational updates, when notification delivery is enabled.

Device permissions can be controlled through Android settings. Denying a permission may limit the relevant feature without preventing other available features from working.

4. How information is used

  • Authenticate users and enforce facility, department, clinical and role-based permissions.
  • Record authorized patient registration, OPD visits, consultations and related documents.
  • Receive, classify, assign, update and verify facility complaints and operational tasks.
  • Display employee work availability, department coverage and duty time derived from availability sessions.
  • Provide voice transcription, structured previews, authorized search answers and spoken responses.
  • Send operational push alerts if configured, maintain audit trails, troubleshoot errors and secure the service.
  • Support permitted exports and integrations requested by the hospital.

Availability-derived duty hours represent self-declared on-duty sessions and should not be treated as independently verified attendance or payroll records without additional controls.

5. Voice processing and AI assistance

When an authorized user submits an audio recording or other prompt, the app may transmit the relevant content to speech recognition and AI service providers to transcribe, normalize language, extract structured fields or answer permitted work questions. Such content may contain health or employee information if included by the user.

Creation or modification of operational and clinical records is designed around an editable preview and explicit user confirmation, subject to the specific feature. Read-only authorized questions may return immediately. AI-generated outputs can be inaccurate and must be checked by the responsible professional before use in care or operational decisions.

The assistant is not a medical professional and does not independently diagnose patients, prescribe treatment or replace a licensed clinician's decisions.

6. Sharing and service providers

Personal information is not sold as part of this service. Information may be made available to authorized hospital users according to their responsibilities and permissions, and may be processed by contracted providers supporting hosting, database/storage, speech recognition, AI processing, security, diagnostics and notifications.

Information may also be disclosed where lawfully required, or where necessary to protect users, patients and the service. The hospital may separately control disclosures, exports and integrations for its own records.

7. Role-based and departmental access

Access to patient/OPD data, employee directories, work orders and supervisory actions depends on assigned permissions. Clinical data should be available only to authorized clinical or administrative roles. Facility staff assistants are intended to answer questions about their permitted operational scope rather than exposing unrelated patient or doctor records.

Hospital administrators are responsible for maintaining accurate accounts, removing unnecessary privileges and revoking access when staff leave or change responsibilities.

8. Data security

We aim to use appropriate organizational and technical safeguards, including authenticated access, permission checks, access restrictions, audit logs and secure network communication. Specific hosting, encryption, backup and retention configurations depend on the deployed environment and should be confirmed with the service operator and hospital.

No networked service can guarantee absolute security. Users must protect credentials and devices and promptly report suspected unauthorized access.

9. Data retention

Records are retained as needed to provide hospital services and to meet applicable contractual, clinical, recordkeeping, legal, security and dispute-resolution requirements. Patient documentation, prescriptions and audit information may have mandatory retention periods and must not be automatically erased when a task or staff account is removed.

Audio recordings may be temporarily processed by speech and AI providers. Transcripts or approved structured entries may be retained as part of a hospital record. Retention periods, provider settings and backup deletion cycles should be confirmed for the deployed service.

10. Access, correction and privacy rights

Individuals may have rights to access, correct or request deletion of personal data under applicable law. Patient clinical records are generally managed by the hospital, which may need to verify the request and apply medical record retention rules. Employees should normally contact their hospital administrator for records held within the hospital account.

11. Account and data deletion

Users may request account closure or deletion of applicable personal information through the hospital or the privacy contact below. The recipient may verify identity and authority before acting. Where deletion is legally permitted, records may be erased or anonymized; where retention is required, access may instead be restricted or records retained for the prescribed period.

Deletion of operational complaints or department configuration does not imply deletion of patient records, prescriptions or mandatory audit history.

12. Children and patient records

This is a professional hospital staff application, not an app for children to register or operate independently. The hospital may process information about pediatric patients through authorized care workflows, subject to the applicable legal, consent, confidentiality and safeguarding requirements.

13. International processing

Where the configured hosting, transcription, AI or notification providers operate outside the hospital's country, data may be processed internationally. The hospital and service operator should confirm applicable transfer requirements, agreements and safeguards for their deployment.

14. Changes to this policy

This policy may be updated when hospital workflows, integrations, service providers, data handling or legal requirements change. Updated versions will display a revised date on this page.

Privacy and deletion contact

Hospital AI Assistant · Hospital workspace
[Add verified privacy contact email before publishing]

Hospital website