Your family's medical records deserve military-grade protection. Here's exactly how we keep your data secure.
We cannot access your decrypted medical records. Your encryption keys never leave your device. Even if our servers were compromised, your data would remain encrypted and unreadable.
Military-grade encryption standard used by governments worldwide. All medical records encrypted client-side before upload.
Your "digital safe combination" stored only by you. Uses BIP39 standard (same as cryptocurrency wallets).
Face ID / Touch ID for quick access on your device. Keys stay encrypted in device secure storage.
All connections use TLS 1.3. Content Security Policy headers. No third-party tracking scripts.
Encryption keys cleared from memory after 15 minutes of inactivity. Require re-authentication to access records.
Records stored encrypted on your device for offline access. Synced securely when connection is restored.
Your device generates a random 12-word recovery phrase using BIP39 standard. This phrase is converted into a 256-bit encryption key using PBKDF2 key derivation.
When you upload a medical record, it's encrypted in your browser using AES-256-GCM. Each file gets a unique initialization vector (IV). Only the encrypted blob and IV are sent to our servers.
Our servers (Supabase) store only encrypted data. We also store a hash of your encryption key (NOT the key itself) for verification purposes. The hash cannot be reversed to obtain the key.
When you view a record, the encrypted blob is downloaded to your device. Your locally-stored encryption key decrypts it in your browser. The decrypted data never touches our servers.
CarryForward is NOT a covered entity under HIPAA. We are not:
As a personal health record (PHR) tool, we are not bound by HIPAA. However, we take security just as seriously and follow industry best practices.
We comply with the FTC's requirements for non-HIPAA entities that handle health information.
In the unlikely event of a security incident, here's our response protocol:
Isolate affected systems, revoke compromised credentials, assess scope of breach.
Determine cause, identify affected users, document timeline, engage security experts if needed.
Email all affected users with details, recommended actions, and support resources. Notify FTC if required (500+ users).
Fix vulnerabilities, implement additional safeguards, conduct security audit, publish transparent post-mortem.
We're continuously improving our security posture. Upcoming enhancements:
We're transparent about our security practices. If you have questions or want to report a vulnerability:
Email: support@carryforward.app
For vulnerability reports, please include steps to reproduce. We aim to respond within 48 hours.