Your portal grants it
Sahara connects through your health system's own patient portal using the standard SMART on FHIR authorization flow. You sign in with the health system, not with us, and you approve exactly what is shared.
Synodha › Security
How Sahara handles your record
Sahara connects read-only through your health system's own patient portal using SMART on FHIR authorization, and does not retain a copy of your clinical record. Access is time-limited, revocable at any time, and caregivers use the proxy access their health system already grants.
Written plainly, including the parts we have not done. If you are evaluating us and need something not covered here, ask rather than assume.
Access
How does Sahara get access to my record?
Read-only, and revocable
Access is read-only. Sahara cannot write to your record. Authorization is time-limited and you can disconnect at any time, which discards the session.
Caregivers use proxy access
A family caregiver uses the proxy access their health system already grants them. Sahara does not create a side channel around your provider's own permissions.
Storage
Does Sahara keep a copy of my record?
Sahara fetches your record to display it and does not retain a copy of the clinical data afterwards. What persists is the session needed to keep you connected, and a pseudonymous key used to count usage, which is derived by one-way hash and cannot be reversed to identify you.
The app includes an in-app control that deletes your stored data, and the Consumer Health Data Privacy Policy is the authoritative statement of what is held and for how long.
In transit and in the app
What security measures are in place?
Everything is served over HTTPS with strict transport security. The app sets a content security policy, denies framing, disables content-type sniffing, and restricts browser permissions and cross-origin access. Request logs redact authorization codes and tokens, so credentials do not end up in operational logs.
The patient-education lookup is deliberately PHI-free: only a code system identifier and a code leave the server to retrieve general material. No name, value, date or token is sent with it.
What we do not claim
What certifications does Synodha hold?
Synodha holds no security certification, no HITRUST, SOC 2 or ISO attestation, and no regulatory clearance. Sahara is a consumer application rather than a service offered on behalf of a health system, and it is not a certified health IT product. Claiming otherwise would be easy and wrong.
To report a suspected vulnerability, write to support@synodha.com with "security" in the subject. We will acknowledge it and tell you what we find.