MedID Privacy Policy
Last Updated: December 21, 2025
IMPORTANT NOTICE: MedID handles sensitive medical and personal health information. This Privacy Policy explains how we collect, use, protect, and share your data. Please read this carefully before using the MedID application.
1. Introduction
Welcome to MedID ("we," "our," or "us"). MedID is a medical identification application that allows personal users (patients) to store their medical information and medical professionals to access this information in emergency situations.
This Privacy Policy describes:
- What personal and medical information we collect
- How we use and protect your information
- Who can access your information
- Your rights regarding your data
- How to contact us with privacy concerns
2. Information We Collect
2.1 Account Information
When you create a MedID account, we collect:
- Email address - Used for account creation and authentication
- Password - Securely hashed and stored by Firebase Authentication
- Account type - Personal user (patient) or Medical professional
- Account creation timestamp - When your account was created
- Email verification status - Whether your email has been verified
- Google Account information (if using Google Sign-In) - Email and sign-in method indicator
2.2 Personal Profile Information (Personal Users)
Personal users may provide the following information in their medical profile:
| Category |
Data Fields |
| Basic Identity |
First name, middle name, last name, birthdate, gender, preferred language |
| Contact Information |
Phone number with country code |
| Physical Characteristics |
Height, weight, hair color, eye color, profile photo |
| Address |
Street address (2 lines), city, state/province, zip/postal code (currently US addresses only) |
| Medical Information |
Blood type, organ donor status, medical conditions (selected from 342 conditions), medications (stored per condition), medical notes |
| Timestamps |
Profile last updated date (automatically recorded when you save changes) |
| Emergency Contacts |
Primary and secondary emergency contact names and phone numbers |
2.3 Medical Conditions
We provide a database of 342 medical conditions that users can select from, including but not limited to:
- Chronic conditions (diabetes, hypertension, heart disease)
- Allergies (food allergies, drug allergies, environmental allergies)
- Mental health conditions (depression, anxiety, PTSD)
- Rare diseases and specialized conditions
- Implanted medical devices (pacemakers, defibrillators)
2.4 Scanning and Access Information (Medical Professionals)
When medical professionals scan a patient's QR code or NFC tag, the following information is collected:
Server-Side Audit Logging (HIPAA Compliance):
- Medical professional's user ID (actor)
- Patient ID being accessed
- Timestamp of access (server-generated)
- Action type (QR scan, NFC scan, profile view)
- IP address and device information
- Success or failure status
These audit logs are stored server-side in an immutable format with cryptographic hash chain integrity to prevent tampering. Audit logs are retained for a minimum of six (6) years as required by HIPAA regulations.
Local Device Storage:
- Cached patient information for quick access (encrypted)
- Scan history for the medical professional's reference
Local scan records are isolated per medical professional account using encrypted secure storage.
2.5 Device and Usage Information
- Device identifier - Android ID or iOS Identifier for Vendor, collected for fraud prevention and rate limiting
- Device type - Mobile device platform (Android/iOS) for security logging
- Device security status - Whether your device is rooted (Android) or jailbroken (iOS), checked locally to warn users about potential security risks to their medical data
- Biometric capabilities - Whether your device supports Face ID, fingerprint, or other biometric authentication (capability only, not biometric data itself)
- Session activity - Timestamp of last user interaction for automatic session timeout
- App lifecycle state - Foreground/background status for security timeout enforcement
- App preferences - Display settings, category visibility toggles
- NFC/Camera permissions - Required for scanning functionality
2.6 Security and Fraud Prevention Logs
To protect against abuse and ensure HIPAA compliance, we log certain security events to our cloud database:
- Failed account creation attempts (rate limiting)
- Failed medical code validation attempts
- Two-factor authentication (2FA) verification attempts and lockouts
- Failed login attempts
- Unauthorized access attempts to protected health information (PHI)
- Session timeout and automatic lock events
- Device identifier and platform for each security event
This data is used solely for security, fraud prevention, and HIPAA compliance. It is not used for analytics, advertising, or tracking.
3. How We Use Your Information
3.1 Primary Purposes
- Emergency Medical Access - To provide critical medical information to healthcare professionals in emergency situations
- Account Management - To create and maintain your MedID account
- Profile Management - To store and display your medical information
- QR/NFC Generation - To create scannable codes linking to your medical profile
3.2 Medical Professional Access
Medical professional account holders can:
- Scan patient QR codes or NFC tags to access medical information
- View complete medical profiles of personal users
- Store scanned patient records locally on their device for reference
IMPORTANT: By using MedID as a personal user, you consent to medical professionals being able to access your complete medical profile when they scan your QR code or NFC tag. This access is intentional and designed for emergency medical situations.
4. How We Store Your Information
4.1 Cloud Storage (Firebase Firestore)
Your account information and medical profile are stored in Google Firebase Firestore, which provides:
- Encryption in transit - All data transmitted using HTTPS/TLS
- Encryption at rest - Data encrypted on Google's servers
- Geographic location - Data stored in Google Cloud data centers
- Backups - Regular automated backups maintained by Google
4.2 Local Device Storage
Encrypted Secure Storage (Sensitive Data):
Sensitive medical information and protected health information (PHI) is stored using platform-native encrypted storage:
- iOS: Apple Keychain with "first unlock this device" accessibility level
- Android: EncryptedSharedPreferences using AES-256-GCM encryption
Data stored in encrypted secure storage includes:
- Your medical profile data
- Medical conditions you've selected
- Cached patient records (for medical professionals)
- Biometric authentication preferences
Standard Storage (Non-Sensitive Data):
Non-sensitive preferences are stored in standard device storage:
- Display preferences and UI settings
- Category visibility toggles
- Onboarding completion status
Security Note: While we encrypt sensitive data, we still recommend:
- Enabling device encryption in your device settings
- Setting a strong device passcode
- Not using MedID on shared or public devices
- Enabling biometric authentication when prompted
4.3 Profile Photos
Profile photos are stored:
- In your device's local file system
- File path stored in app preferences
- Not automatically uploaded to cloud storage
5. Information Sharing and Disclosure
5.1 Medical Professional Access
Personal user medical profiles are accessible to:
- All medical professional account holders who scan your QR code or NFC tag
- This is by design for emergency medical access
- No additional patient consent is required for each access
5.2 Third-Party Services
We use the following third-party services that may have access to your data:
| Service |
Purpose |
Data Accessed |
| Firebase Authentication |
User login and authentication |
Email, password hash, Google OAuth tokens |
| Firebase Firestore |
Cloud database storage |
All profile and medical data |
| Google Sign-In |
OAuth authentication |
Google account email, ID token |
| Firebase Hosting |
Web page hosting (privacy policy, links) |
IP address, page views |
| Stripe |
Payment processing |
Payment card details, billing address, shipping address, email |
| Gmail (via Nodemailer) |
Email delivery |
Email addresses for account notifications |
| Firebase Cloud Functions |
Server-side processing |
Medical code validation, 2FA code generation and verification, email sending, server-side encryption/decryption, audit logging |
| Firebase App Check |
API protection and device attestation |
Device attestation tokens (DeviceCheck on iOS, Play Integrity on Android) |
| Firebase Secrets Manager |
Secure key storage |
None (encryption keys stored server-side only, never transmitted to devices) |
5.3 We Do NOT Share Your Data With:
- Advertisers or marketing companies
- Insurance companies
- Employers
- Data brokers
- Social media platforms (beyond Google Sign-In)
5.4 Legal Requirements
We may disclose your information if required by law or in response to:
- Valid legal process (subpoena, court order)
- Government or regulatory requests
- To protect the rights, property, or safety of MedID, our users, or the public
6. Your Privacy Rights
6.1 Access and Portability
You have the right to:
- Access your data - View all information in your profile within the app
- Export your data - Download your medical profile as a PDF document
- Share your data - Generate QR codes to share your profile with medical professionals
6.2 Correction and Updates
- Update your profile information at any time through the app settings
- Modify or remove medical conditions from your profile
- Change your emergency contact information
6.3 Deletion Rights
You can delete your data by:
- Account deletion - Delete your entire MedID account and all associated data through the app settings (requires password re-authentication)
- Profile editing - Clear or modify specific fields in your profile by editing them
For assistance with account deletion, contact us at: support@nurevamedical.com
6.4 Objection and Restriction
- Object to processing - Contact us to object to how we use your data
- Restrict processing - Request temporary suspension of data processing
7. Data Security
7.1 Security Measures
We implement comprehensive security measures to protect your medical information:
Encryption:
- Encryption in transit - HTTPS/TLS for all network communications
- Encryption at rest (Cloud) - Google-managed encryption for Firestore data
- Encryption at rest (Device) - AES-256-GCM encryption for sensitive local data via platform-native secure storage
- Patient ID encryption - Server-side AES-256-GCM encryption for patient identification tokens in QR codes and NFC tags
- Encryption key management - Keys stored in Firebase Secrets Manager, never exposed to client devices
Authentication & Access Control:
- Firebase Authentication - Secure password hashing and account management
- Two-Factor Authentication (2FA) - Email-based verification codes, mandatory for medical professionals
- Biometric authentication - Face ID, fingerprint, or other device biometrics (mandatory for medical professionals if device supports)
- Firestore security rules - Row-level access control limiting data visibility
- Role-based permissions - Different access levels for personal users vs. medical professionals
- Firebase App Check - Ensures only the genuine MedID app can access backend services
Session Security:
- Automatic session lock - Screen locks after 30 minutes (personal) or 15 minutes (medical) of inactivity, requiring biometric re-authentication
- Background lock - Screen locks when the app is in the background too long (medical professionals)
- Biometric re-authentication - Face ID, Touch ID, or fingerprint required to unlock after inactivity timeout
- Sensitive data clearing - All cached PHI is cleared from device on logout
Audit & Compliance:
- Immutable audit logs - All PHI access is logged server-side with cryptographic hash chain integrity
- 6-year retention - Audit logs retained per HIPAA requirements
- Rate limiting - Protection against brute-force attacks on 2FA and login
Code Security:
- 2FA code hashing - Verification codes are hashed with bcrypt before storage; plaintext codes are never stored
- Device code hashing - SHA-256 hashing for device activation codes
Device Security:
- Root/jailbreak detection - MedID checks if your device has been rooted (Android) or jailbroken (iOS) and warns you about potential security risks to your medical data
- Backup protection - On Android, MedID data is excluded from device backups to prevent unencrypted PHI exposure
7.2 Security Considerations
Please be aware of the following:
- Digital ID QR codes use server-side AES-256-GCM encryption to protect your user ID
- Physical MedID QR codes contain serial numbers (not patient IDs) that are used to look up linked accounts
- QR codes can be photographed, so protect your device from unauthorized access
- Medical professionals can access personal user profiles when they scan your QR code or NFC tag - this is by design for emergency access
- All such accesses are logged in our audit system
7.3 Your Responsibilities
- Use a strong, unique password for your MedID account
- Enable two-factor authentication when prompted
- Enable biometric authentication for added security
- Enable device encryption and screen lock on your mobile device
- Do not share your login credentials with others
- Log out of shared or public devices
- Protect your NFC tag and QR code from unauthorized access
8. Children's Privacy
MedID is not intended for use by children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us immediately.
9. International Data Transfers
Your data may be transferred to and stored in countries outside your country of residence, including the United States, where Firebase/Google Cloud Platform operates data centers. By using MedID, you consent to the transfer of your information to these countries, which may have different data protection laws than your country.
10. Data Retention
We retain your data for the following periods:
- Active accounts - Data retained as long as your account is active
- Deleted accounts - Data permanently deleted immediately upon account deletion confirmation (requires password re-authentication)
- Audit logs - Retained for a minimum of six (6) years as required by HIPAA regulations (immutable, cannot be deleted)
- Security events - Retained indefinitely for compliance and fraud prevention
- Two-factor authentication (2FA) codes - Automatically expire and are deleted after 10 minutes
- Session data - Cleared immediately upon logout or session timeout
- Scanned patient records - Medical professionals' local scan history retained until manually deleted or account deletion
- Backup data - Firebase backups retain data for up to 98 days
- Physical MedID devices - When your account is deleted, any linked devices are reset to "unclaimed" status and can be activated by a new user. Your previous ownership is recorded in audit logs.
11. HIPAA and Medical Privacy
IMPORTANT - HIPAA NOTICE:
MedID handles Protected Health Information (PHI) as defined by the Health Insurance Portability and Accountability Act (HIPAA). MedID has implemented comprehensive technical safeguards to protect your medical information.
HIPAA Security Features Implemented:
- Access Controls: Role-based permissions, mandatory two-factor authentication for medical professionals, biometric authentication
- Audit Controls: Comprehensive server-side audit logging of all PHI access with immutable hash chain integrity
- Integrity Controls: Cryptographic verification of audit logs, tamper-evident design
- Transmission Security: All data encrypted in transit using TLS/HTTPS
- Encryption: PHI encrypted at rest using AES-256-GCM on devices and Google-managed encryption in the cloud
- Automatic Session Lock: Screen locks after inactivity (15 minutes for medical, 30 minutes for personal), requiring biometric re-authentication to continue
- Audit Log Retention: Minimum 6-year retention of all access logs
Important Limitations:
- MedID is designed for patient-controlled emergency medical information sharing
- MedID should not be used as a primary electronic health record (EHR) system by healthcare providers
- Medical professionals should verify critical information with official medical records
- MedID does not currently provide Business Associate Agreements (BAAs) to healthcare organizations
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. When we make changes:
- We will update the "Last Updated" date at the top of this policy
- The updated policy will be posted on our website
- Continued use of MedID after changes constitutes acceptance of the updated policy
We encourage you to review this policy periodically for any updates.
13. State-Specific Privacy Rights
13.1 California Residents (CCPA/CPRA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):
- Right to know - Request disclosure of data collected about you
- Right to delete - Request deletion of your personal information
- Right to opt-out - Opt out of sale of personal information (we do not sell your data)
- Right to non-discrimination - Equal service regardless of privacy rights exercise
13.2 European Residents (GDPR)
If you are in the European Economic Area (EEA), you have rights under the General Data Protection Regulation (GDPR):
- Right to access, rectification, erasure, and portability
- Right to restrict or object to processing
- Right to withdraw consent at any time
- Right to lodge a complaint with a supervisory authority
14. Do Not Track Signals
MedID does not track users across third-party websites or respond to "Do Not Track" signals. We only collect data within the MedID application as described in this policy.
15. Contact Us
16. Consent
By creating a MedID account and using the application, you consent to:
- The collection and use of your information as described in this Privacy Policy
- Medical professionals accessing your complete medical profile when they scan your QR/NFC code
- Storage of your data in Firebase/Google Cloud Platform
- International data transfers as described in Section 9
© 2025 MedID. All rights reserved. |
Terms of Service |
Privacy Policy