MedPass
Privacy Policy
Effective July 2, 2026
MedPass (“the app”) is a medication documentation tool for licensed residential care facilities, published by Saiphyr (“we,” “us”). This policy describes what information the app handles and how.
What we collect
Facility account email address. MedPass uses an invite-only facility account (email and password) to sign a device into your facility. We store the account email and facility name with our authentication provider (Supabase) so we can provision and support your account. That is the only information about you that leaves your device.
Nothing else. MedPass contains no analytics, no advertising, no tracking identifiers, and no third-party data sharing.
Resident and care data stays on the device
All resident, medication, administration, and audit records you enter in MedPass are stored locally on the device where they were entered. They are not transmitted to us or to any third party.
Validation program notice: the current release of MedPass is part of an invite-only validation program. Facilities are instructed to use fictional (mock) resident data only. MedPass is not intended for real patient information during this phase, and no protected health information is collected or transmitted.
Staff sign-in PINs
Staff member names and PINs used on the shared-device sign-in screen are created by your facility administrator and exist only on your device. PINs are stored as salted cryptographic hashes, never as plain text.
Data retention and deletion
- Signing a facility out of a device (“Sign out facility”) permanently erases all app data on that device.
- To delete your facility account (the email we store), contact us at the address below and we will remove it.
Security
Communication with our authentication service uses standard TLS (HTTPS) encryption. Local data is protected by iOS device security and app sandboxing.
Children
MedPass is a professional tool for licensed care facility staff and is not directed at children.
Changes
If our data practices change — for example, when optional cloud synchronization is introduced for production facilities — we will update this policy and its effective date before those changes take effect.
Contact
Saiphyr — phil.johnson.potter@gmail.com