Security & Privacy at MemoryShield
Your passwords, documents and final messages are protected by multiple, independent layers of security—Google-grade infrastructure, end-to-end encryption, granular access rules and optional multi-factor login. Even our own engineers can’t read your vault, and we publish our roadmap so you always know what’s coming next.
Frequently Asked Questions
How do I sign in securely?+
We delegate all identity checks to Google Firebase Authentication. Passwords are never stored on our servers, and tokens are signed with Google-managed keys, then auto-rotated to stop session hijacking.
Can I add multi-factor authentication (MFA)?+
Yes—SMS 2-Factor Authentication is one click away in your profile. Each login then requires your password and a one-time code sent to your phone, blocking the vast majority of credential-stuffing attacks.
Is my data encrypted in transit and at rest?+
Absolutely. All traffic is shielded by TLS 1.3 to prevent man-in-the-middle snooping, and every Firestore record is automatically wrapped in AES-256 before it touches disk on Google Cloud.
Can MemoryShield staff read my vault contents?+
No. Today your data is server-encrypted, and our schema is already prepared for full client-side, zero-knowledge encryption so only you hold the key—never us.
How is access controlled inside the app?+
Least-privilege Firestore rules. Regular users can read/write only their own /users/{uid}/… paths, while a single hard-coded admin has read-only analytics access. All other requests are denied by default.
What happens when I export my data?+
Your export is zipped and emailed solely to your verified address. Links self-destruct after a single download and we display strong warnings about handling sensitive files.
How do you secure payments?+
We never touch card numbers. Paddle processes all payments and signs every webhook with an HMAC key; we verify that signature against the secret stored in Google Secret Manager before saving any event.
Who can access my account if something happens to me?+
You appoint trustees. They must confirm identity via a single-use, cryptographically signed link, and they see nothing until our Life-Check system plus a manual review confirms access is warranted—fully aligned with the Revised Uniform Fiduciary Access to Digital Assets Act.
Why do you plan to add hardware-key MFA?+
SMS codes stop most automated attacks, but they’re vulnerable to SIM-swaps; hardware keys (WebAuthn/FIDO2) remove that risk entirely. We are already prototyping this upgrade.