Qaro
Home Product Why Us Request Early Access

Privacy Policy

Last updated: November 5, 2026

This Privacy Policy explains how Prometheus Technology Systems Corp ("Qaro," "we," "us") handles information in connection with the Qaro application and website (together, the "Service"). Qaro is a secure staff-communication product for healthcare practices. This policy is written to describe what the Service actually does — not a generic template — and it should be read alongside the App Store and Google Play data-safety disclosures, which it is designed to match.

On this page
  1. Two kinds of people: users and patients
  2. Information we collect
  3. What we do not collect or do
  4. How we use information
  5. Service providers and notifications
  6. Patient information and HIPAA
  7. Security
  8. Retention and deletion
  9. Children's privacy
  10. Changes to this policy
  11. Contact and governing law

1. Two kinds of people: users and patients

Qaro involves two distinct groups, and this policy treats them differently:

  • Users — the clinicians and practice staff who sign in and use Qaro. This policy is about the information of users.
  • Patients — never users and never account holders. Patient information exists only in what staff send each other: the text of a message, or a photo or PDF attached to one (an insurance card, a referral letter). That information is Protected Health Information (PHI) held on behalf of the practice.

Under U.S. health-privacy law, the practice is the covered entity and Qaro acts as its business associate. Our handling of PHI is governed by the Business Associate Agreement (BAA) between Qaro and the practice — not by this consumer-facing policy. Questions about a specific patient's information should be directed to the practice that holds the relationship with that patient.

2. Information we collect

Qaro collects only what it needs to operate:

  • Name and email address — entered by your practice's administrator to identify you to colleagues and display you in the staff directory.
  • Professional details — title, credentials, NPI and a mobile number, where your practice records them, shown to colleagues in the directory.
  • Organization, location(s), and role(s) — used to decide what you can see and do.
  • Who is working each day — the coverage schedule your practice keeps, so colleagues can see who is in today and day rooms know who belongs in them.
  • Message content and attachments — the messages you send, and any photo or PDF you attach to one, with its file name and size. Photos have their location and camera details removed before they are stored.
  • Online status — whether you currently have Qaro open, derived from your live connection. You do not set it, and it is not kept once you disconnect.
  • Device push token — an identifier for your device, used to deliver notifications.
  • Notification-permission state — reported by your device's operating system, used to warn a sender when a recipient cannot be reached.
  • Language preference — a setting stored with your account.

What the mobile app asks your phone for: permission to show notifications; the camera and your photo library, only when you choose to attach a photo, and only the photo you pick; and Face ID, a fingerprint, or your phone's passcode, to unlock Qaro after it has been away (see Section 7). Qaro never sees your biometric data: your phone only tells it whether the check passed. The app does not access your microphone, location, contacts, or calendar.

3. What we do not collect or do

We state these plainly because they are unusual, and they define what the Service is not:

  • No analytics of any kind — no Google Analytics, no Firebase Analytics, no product-usage telemetry.
  • No crash or diagnostic reporting — no Crashlytics, no Sentry, no crash-reporting SDK.
  • No advertising — no ads, no advertising identifiers, no attribution or marketing SDKs.
  • No tracking — there is nothing to track across apps or websites.
  • No location collection — including the location recorded inside a photo, which is removed before the photo is stored.
  • Nothing kept on your phone — messages, photos and documents are fetched from our servers each time you view them and are not saved to your device or its photo library.
  • No sale or sharing of personal information for advertising or any other purpose.

4. How we use information

We use the information above only to provide the Service: to authenticate you, deliver and display messages and their attachments, show who is working and who is online, deliver notifications, and maintain the compliance audit record described below. We do not use it for advertising, profiling, or any purpose unrelated to operating the Service.

5. Service providers and notifications

Qaro relies on a small number of service providers, each of which processes information on our behalf:

  • Microsoft Azure — hosts and stores all application data, including PHI and attached files, in the United States, under a HIPAA Business Associate Agreement.
  • Microsoft Entra External ID — provides authentication and sign-in.
  • Google Firebase Cloud Messaging (FCM) — delivers push notifications; receives the device token and a notification payload that contains no PHI.
  • Apple Push Notification service (APNs) — delivers the same PHI-free payload to Apple devices.

No patient information ever appears in a notification. A push notification carries only a message type, identifiers for the message and its conversation, and whether a file is attached. The visible text is a fixed, generic string such as "New message — Open Qaro to view." or "New photo." Neither the message, the sender's name, nor the file is in it. Actual content is retrieved over our authenticated connection only after you open the app. This is a deliberate commitment, and it is the reason our notification providers can carry Qaro alerts without holding a BAA.

6. Patient information and HIPAA

As described in Section 1, any patient information within Qaro is PHI that we process as a business associate of the practice. Message content and attached files are encrypted, access is restricted to the members of each conversation within one organization, and every message sent and read, and every time a file is opened, is recorded in an append-only audit log. Our obligations with respect to PHI — including permitted uses, breach notification, and the practice's rights — are set out in the BAA between Qaro and each practice, which controls over this policy where PHI is concerned.

7. Security

  • In transit: all communication uses HTTPS/TLS. The mobile app will not run a release build configured against a non-HTTPS endpoint.
  • At rest: message content and attached files are encrypted by Qaro with AES-256-GCM before they are stored, with the key held in Microsoft Azure Key Vault, and Azure encrypts its storage again underneath. Files are never published at a web address: Qaro streams each one to a member of the conversation after checking that they may see it.
  • On your device: your sign-in is stored in the iOS Keychain or Android Keystore and is excluded from backups and from transfers to a new phone, so it never leaves the device it was made on. Messages and files are not stored on the device; a photo you take or pick is removed from Qaro's temporary storage once it is sent.
  • App lock: after 15 minutes away from the app, Qaro hides its content and asks for your phone's Face ID, fingerprint, or passcode before showing anything again. The app switcher shows Qaro's splash screen instead of an open conversation.

Encryption is applied at rest and in transit. Qaro is not "end-to-end encrypted": our servers hold the encryption key so that your message history can be shown to you on any device you sign in to.

8. Retention and deletion

Messages, and the files attached to them, are kept for three years from when they were sent and then deleted automatically. The compliance audit log is append-only: entries cannot be changed or removed one by one, and are deleted when they reach the end of their retention period (six years for most entries). Because the practice owns its data, requests to access or delete information are handled through the practice and its administrators. You may also contact us at support@qarochat.com with a privacy or deletion request, and we will act on it consistent with the practice's instructions and applicable law.

9. Children's privacy

Qaro is a professional tool used by healthcare staff. It is not directed to children, and we do not knowingly collect information from anyone under 18.

10. Changes to this policy

We may update this policy from time to time. When we do, we will revise the "Last updated" date above and, for material changes, provide a more prominent notice. Continued use of the Service after an update means you accept the revised policy.

11. Contact and governing law

Questions about this policy can be sent to support@qarochat.com. This policy is governed by the laws of the State of Georgia, United States, without regard to its conflict-of-laws rules.

Prometheus Technology Systems Corp · qarochat.com

Qaro
by Prometheus Technology Systems Corp

HIPAA-compliant staff communication for multi-location outpatient practices.

Product
  • Features
  • Why Qaro
  • Pricing
Legal
  • Privacy Policy
  • Terms of Use
  • Account Deletion
  • Contact
© 2026 Prometheus Technology Systems Corp. All rights reserved. qarochat.com