Privacy Policy

Last updated: 13 August 2026

What we never store

• Audio recordings. When you dictate, the audio is sent securely for transcription and is processed in-flight. It is never written to our disks or databases and is discarded the moment the request completes. No audio file has ever been stored.

What we store — account data (all modes)

• Your email address, name, and a securely hashed password.
• Subscription status and billing identifiers from our payment processors.
• A session cookie and minimal anti-abuse counters.

What we store — clinical data (clinic/hospital mode)

When clinic or hospital features are enabled for your tenant, the following clinical data is stored in your isolated per-tenant database, at your instruction:

• Encounters: patient name, transcript text, and encounter metadata.
• Reports: structured document output (report JSON, PDF filename).
• Diagnoses: ICD-10 clinical codes associated with encounters.
• Suggestions: medication and investigation order suggestions.
• Integration data: when EMR integration is configured, patient identifiers (including national ID, date of birth, address, phone numbers) and a patient crosswalk linking MediVoice encounters to your EMR records.
• Audit trail: before/after values for clinical record changes.

This data is stored in a per-tenant isolated database. Other tenants cannot access your data. The data is exposed to your EMR system via a local FHIR R4 read server over MediVoice's own database.

Standalone or solo-doctor use retains no clinical content — transcripts and documents exist only in your browser during the session.

Data retention

Clinical record retention is enforced per tenant and configurable, with a default of 90 days. You may configure a longer retention period if your jurisdiction legally requires it. Expired records are automatically purged by a daily retention job.

Account deletion

You may delete your account at any time. Deletion removes your data from live systems immediately. Encrypted backup copies are not edited in place; they expire automatically on our retention schedule (24 hourly, 30 daily, 12 weekly backups) and are permanently removed within twelve weeks.

Third-party processors

• Anthropic (United States) — AI text structuring. Every transcript is sent to Anthropic to produce the structured clinical document.
• Groq (United States) — audio transcription. Your dictation audio is processed by Groq to produce text. On the AI Prescriptions product, Groq also processes clinical notes and Egyptian national ID images for extraction.
• Stripe, Paymob, PayPal — payment processing. Card details are handled entirely by the processor; we never see or store card numbers.
• Hostinger (European Union — Germany and France) — infrastructure hosting. All data at rest is stored in the EU.

Anthropic and Groq operate under standard terms. Clinical data and transcripts are sent to the United States for AI processing. This cross-border transfer is performed with your consent.

Your responsibility as a clinician

MediVoice is a clinical documentation tool. You remain the custodian of your patients' records. Exported PDFs are saved wherever you choose; please store and share them in line with your local medical-records and data-protection obligations.

Your rights

Depending on your jurisdiction (including Egypt's PDPL, Law 151 of 2020), you may have the right to access, correct, export, or delete your personal data. To exercise these rights or ask any privacy question, contact privacy@naghamyhealth.com.

Contact

support@naghamyhealth.com
privacy@naghamyhealth.com
Naghamy Health LLC · 30 N Gould St #65183 · Sheridan, WY 82801 · USA