Skip to content

Security

Security that supports daily care.

What Wareed does today to protect clinic accounts and patient information. Each point below describes how the product works now, not a plan.

Organizations stay separate

Every record belongs to one organization, and staff only ever see their own organization’s data. Inside an organization, roles decide what each person can open or change, and administrators can further limit people to particular branches or departments.

Sign-in and sessions

Passwords are stored only as bcrypt hashes and must meet a strength check. After five wrong passwords an account locks for 15 minutes and the owner is emailed. Sessions live in secure, HTTP-only cookies that last for the browser session, or 30 days when someone chooses to stay signed in, and are revoked when a password is reset.

Encryption

All traffic uses HTTPS, and browsers are told to refuse plain HTTP (HSTS). Visit audio that a clinic chooses to keep is encrypted with AES-256-GCM before it is stored and deleted on the clinic’s schedule; by default no audio is kept after transcription.

AI and patient data

Fatma and the visit scribe act within each staff member’s permissions. Language-model requests are routed only to providers that neither store nor train on them, and we do not use patient records, conversations or recordings to train AI models.

Accountability

Changes to records, sign-ins, permission changes and actions taken by AI features appear in the activity and audit logs, so administrators can see who did what and when.

Hosting, backups and assessments

Clinics evaluating Wareed can ask security@wareed.io for our current hosting region, backup schedule, recovery objectives and any independent security assessments. We do not publish figures here that we cannot keep up to date.

Report a concern

To report a potential vulnerability, email security@wareed.io with enough detail for our team to investigate safely. Please do not include patient data in an email report.