Zonov HIS Agent

Privacy Policy

This policy explains how the Zonov HIS Agent Chrome extension and its FastAPI backend access, use, store, and transmit data while supporting OT, IPD, pharmacy, finance, claim, and discovery workflows on approved hospital systems.

Effective date: May 27, 2026 Version: 1.0 Product: Chrome extension + backend service

Contents

Overview Data We Collect How We Use Data Sharing and Transfers Storage and Retention Permissions Security Your Choices Children Changes Contact

1. Overview

Zonov HIS Agent is designed for healthcare workflows in hospital information systems. It operates only on pages and services that the user chooses to open, and it is built to support OT record capture, patient context handling, discovery, and related forms.

The extension reads information from the current web page, stores some settings locally in Chrome, and sends selected data to a backend API when you use a feature that requires server-side processing.

What is local Chrome storage settings, temporary session context, and user-configured endpoints live on the device unless the user clears them.
What may leave the device Page fingerprints, extracted candidates, workflow events, patient context payloads, and optional OCR or voice inputs can be sent to the backend or third-party providers.
Important: This policy describes the project as currently implemented in the repository. If you deploy different hosts, API routes, or providers, update the policy before release.

2. Data We Collect and Process

2.1 Data from the active HIS page

The extension can read content from the page you are actively viewing in order to capture patient and workflow details. Depending on the screen, this may include UHID, patient name, admission or visit identifiers, OT booking details, procedure details, medication details, finance values, claim fields, and other visible DOM content.

  • Visible DOM text and form values from the active tab.
  • Page fingerprints used to recognize supported pages.
  • Extracted field candidates and workflow events.
  • Network payload candidates when network interception is enabled.

2.2 Patient context data

The backend stores central patient context records to support OT, IPD, pharmacy, claim, and finance workflows. This may include canonical patient identifiers, workflow history, event logs, projection job metadata, and data needed to resolve conflicts or refresh data.

2.3 Discovery and mapping data

The extension can collect page discovery results, including candidate labels, values, selectors, and confidence scores. These are used to map HIS screens to canonical fields.

2.4 Local settings and identifiers

The extension stores configuration in Chrome local storage, such as the configured API base URL, approved HIS hosts, license information, API keys entered by the user, and temporary workflow state.

Data type Examples Where it may be stored
Page content Visible patient name, UHID, OT booking data, form fields Browser memory temporarily; backend only when a feature needs it
Discovery payloads Selectors, labels, confidence scores, DOM candidates Backend database and review tools
Workflow events OT progress updates, state changes, mapping status Backend database
Local configuration API base URL, approved hosts, stored keys, session context Chrome local storage

3. How We Use Data

Workflow automation Capture OT, IPD, pharmacy, finance, and claim data from HIS pages and move it into the correct project screens and records.
Page recognition Identify approved pages using fingerprints and discovered DOM patterns so the correct extraction logic can run.
Mapping review Let administrators review candidates in the backend admin UI and approve field mappings.
Optional AI assistance Use Groq for OCR or suggestions when the user enables those features in the product.

Features that can trigger server communication

  • Discovery session capture and page review.
  • OT workflow event persistence.
  • Patient context resolution and projections.
  • OCR and AI suggestions when enabled.
  • Voice capture and speech-to-text when enabled.
  • License and configuration validation.

4. Sharing and Data Transfers

Zonov HIS Agent does not sell patient data. Data is shared only when required to operate the product or when the user explicitly enables a feature that depends on another service.

Recipient Why data is sent Examples of data
FastAPI backend Discovery, patient context, mapping review, OT workflow processing Page fingerprints, extracted candidates, workflow events, context records
Groq OCR and AI suggestions when enabled by the user Images, text prompts, OCR snippets
Deepgram Speech-to-text when voice input is enabled by the user Mic audio chunks during active recording
Configured HIS origin Read-only page access for the workflow screen you opened Browser requests to the hospital site you are using

If data is transferred outside your country or region, it is done only through the service providers above and only for the feature you chose to use.

5. Storage and Retention

5.1 Local device storage

  • Approved hosts, API settings, license details, and user preferences are stored in Chrome local storage.
  • Temporary session state may remain in memory while a workflow screen is open.
  • The user can clear local data by removing the extension or clearing Chrome site/extension data.

5.2 Backend storage

  • The backend stores patient context, discovery sessions, mapping records, workflow events, projection jobs, and review data needed for the product to function.
  • Server-side retention depends on your deployment and operational policy. If you run your own backend, you control how long data is kept.

5.3 Third-party retention

Groq and Deepgram handle only the data you send when you use their related features. Their own privacy policies and retention practices apply to those requests.

6. Chrome Permissions and Why They Are Needed

storage Saves user settings, approved hosts, license details, and temporary local workflow state.
tabs Reads the active tab so the extension can determine which HIS page is open and what workflow to run.
scripting Injects the extension UI and workflow scripts into supported pages when the user opens them.
offscreen Supports background processing tasks that need a hidden browser context.
webRequest Observes selected network requests so the extension can identify useful patient or workflow payloads.
windows and system.display Support extension UI and screen-related workflow features where enabled.
The extension is designed to operate on approved HIS and application pages only. It does not intentionally access unrelated browsing activity for product features.

7. Security

Data sent to the backend and third-party providers is transmitted over HTTPS where supported. The project separates extension-side configuration from backend secrets, and sensitive keys are intended to remain on the backend or in local user storage as appropriate to the feature.

  • Backend URLs and service keys are not meant to be hardcoded into the extension bundle.
  • Users should only configure trusted HIS and backend endpoints.
  • Access should be limited to authorized hospital staff and approved environments.

8. Your Choices and Controls

  • You can disable the extension at any time from Chrome's Extensions page.
  • You can clear extension storage from Chrome settings or by removing the extension.
  • You can stop voice capture or OCR by not starting those features.
  • You can remove approved hosts or API settings from the Options page.
  • You can contact the operator to request guidance about stored backend data in your deployment.

Practical control summary

Stop local collection Close the workflow page, disable the extension, or clear Chrome extension data.
Stop backend processing Stop using the feature that sends data or disable the backend service in your deployment.

9. Children's Privacy

This product is intended for use by healthcare staff and hospital operators. It is not directed to children, and we do not knowingly collect data from children through this product.

10. Changes to This Policy

We may update this Privacy Policy as the product changes. When we do, we will update the effective date at the top of this page. Continued use of the extension after a change means you accept the updated policy.

11. Contact

If you have privacy questions, data access questions, or need to report a problem, contact the project operator at the details below.

Project Zonov AI / Zonov HIS Agent
Email arvind@zonov.ai
Website https://www.zonov.ai/
Support note If your deployment uses different backend or third-party providers, publish an updated policy for that deployment.
This document is a project-specific privacy policy drafted from the repository's current behavior and disclosures. It should be reviewed by your legal or compliance team before public release.