Skip to content
Ureport
FeaturesForm modeHow it worksFAQ
Contact Open Ureport
FeaturesForm modeHow it worksFAQ Browser extension Templates For your specialty About Contact
Open Ureport
Home/Security

Contents

  1. 1. Encryption in transit
  2. 2. Audio data handling
  3. 3. Patient data
  4. 4. Account protection
  5. 5. Access controls
  6. 6. AI model training
  7. 7. Organisation controls
  8. 8. Files you send us
  9. 9. Records system connections
  10. 10. Incident response
  11. 11. Reporting vulnerabilities
  12. 12. Contact

Last updated: September 2026

Security and Data Handling

Security is central to how we design Ureport. Clinical information is sensitive by nature, and our architecture reflects that from first principles. This page describes the technical and organisational measures we use to protect your data and your patients’ privacy. Our handling follows the Nigeria Data Protection Regulation (NDPR) and is aligned with HIPAA principles.

1. Encryption in transit

All communication between the Ureport application, the browser extension and our servers uses TLS 1.2 or higher. This applies to audio uploads, note retrieval, and all account management operations. We do not accept unencrypted connections.

2. Audio data handling

When you submit audio for transcription, it is transmitted over an encrypted connection to our processing service. Once the transcription is complete and the draft note is returned to your device, the audio is deleted from our systems. We do not cache, archive or store raw audio recordings. Live captions shown while you record are display only and are never stored.

3. Patient data

Ureport’s architecture is built so that patient-identifiable information does not persist on our servers. Notes are generated, returned to the user’s device, and not stored by us. If you include patient names or identifiers in your dictation, those are present only in the transient processing pipeline and are not retained after the session completes.

4. Account protection

Passwords are hashed with a modern one-way algorithm and are never stored in a form we can read. Two-factor authentication is available on any account and can be made mandatory by an organisation, after which members cannot turn it off. New sign-ins can require device approval.

Sign-in attempts are rate limited per account and per address. Changing your password signs out every other device immediately. “Sign out everywhere” ends every session on the server, not just on the device you are holding. You can see and revoke your active sessions from the app.

5. Access controls

Access to production systems is restricted to authorised personnel on a need-to-know basis. We use multi-factor authentication for all internal system access. Audit logs are maintained for administrative operations.

6. AI model training

We do not use patient dictation content or clinical notes to train AI models. The AI pipeline processes your audio to generate a note and then discards the input. Model improvements are based on aggregated, anonymised usage signals unconnected to any patient data.

7. Organisation controls

An organisation administrator can see members, usage, registered devices and, where filing is enabled, that a note was filed and when. Administrators can lock the organisation to approved devices. They cannot see notes, recordings or dictation, because we do not hold that content.

8. Files you send us

Any file attached to a support message is written to a quarantine area that nothing serves, and is not readable by anyone until it has been checked. Images are re-encoded from their pixels, which removes anything hidden inside the file. Documents are scanned before release. A file that cannot be checked is refused rather than accepted unchecked.

9. Records system connections

Where an organisation files notes into its own records system, the connection is authenticated with credentials that organisation controls and can rotate or revoke at any time. Revoking takes effect immediately. We log that a note was sent and when; we do not log or retain its clinical content.

10. Incident response

We maintain an incident response plan for security events. In the event of a confirmed data breach affecting user account data, we will notify affected users within the timeframe required by applicable law, including the NDPR (72 hours for notifiable breaches where applicable).

11. Reporting vulnerabilities

If you discover a security vulnerability in Ureport, please report it responsibly through the UnityPulse contact page. We will acknowledge your report within two business days and work with you to address the issue before any public disclosure.

12. Contact

Security questions? Reach us through the UnityPulse contact page. Support replies within two business days.

Ureport

AI clinical dictation for every specialty except imaging.

A UnityPulse product. Radiologists and sonographers: TScribe.

Product

  • Features
  • How it works
  • Form mode
  • Browser extension
  • Templates

For your specialty

  • General practice
  • Nursing
  • Obstetrics and gynaecology
  • Emergency medicine
  • Pharmacy
  • Public and community health

Company

  • About
  • Contact
  • FAQ
  • UnityPulse for organisations
  • TScribe for imaging

Legal

  • Privacy
  • Terms
  • EULA
  • Cookies
  • Security
  • Data deletion
  • Acceptable use
  • Extension privacy
© 2026 UnityPulse. Made in Nigeria.Not a medical device. Every note is reviewed by a qualified clinician.