Secure Digital Inheritance Platform
A secure vault for preserving sensitive records and releasing them to a trusted successor only after verification and admin approval.
LiveOverview
LegacyVault is a digital inheritance platform that helps users organize documents, final wishes, future messages, verification questions, and successor instructions in one protected system. A successor can request access through a structured claim flow, but vault information is released only after answer scoring and admin review.
Problem / Purpose
The project addresses a sensitive real-world problem: important personal, legal, financial, and digital records are often scattered or inaccessible when their owner becomes unavailable. LegacyVault creates a controlled path for preserving that information and transferring access without exposing private data prematurely.
My Role / Contribution
This was a collaborative project. I built the complete frontend experience and owned the core document-claiming workflow end to end, implementing both its frontend interactions and backend behavior.
Key Features
Tech Stack
Architecture / How It Works
LegacyVault uses a React client with authenticated route groups and an Express API organized into feature modules. The backend owns claim verification, access decisions, persistence, and secure document operations.
The owner stores documents, wishes, messages, successor details, and verification questions through protected dashboard workflows.
A successor enters the claim portal, provides identity details, and answers the owner's verification questions.
The backend scores submitted answers and places the claim into an admin-controlled approval or rejection workflow.
After approval, the successor gains access only to the released vault documents, final wishes, and future messages.
Screenshots / Visual Walkthrough
The primary dashboard organizes documents, successors, questions, wishes, messages, claims, and settings.
Document screens support secure upload, categorization, retrieval, status changes, and deletion.
The claim experience guides successors through identity details and verification answers.
Admin views surface pending claims, verification results, approval controls, and audit history.
Challenges & Solutions
Challenge
Designing a sensitive claim workflow that does not expose vault data too early.
Solution
I separated claim submission, answer scoring, admin review, and released access into explicit states enforced across both the frontend and backend.
Challenge
Keeping several user experiences coherent within one frontend.
Solution
I created distinct public, owner, successor, and admin layouts while maintaining shared interaction and visual patterns throughout the application.
Challenge
Coordinating authentication, document storage, and workflow state across the stack.
Solution
I connected Firebase identity, protected API services, Cloudinary-backed files, and TanStack Query state through clear service and route boundaries.
What I Learned
Final Links / CTA
Open the live product, review the repository, or return to the full projects archive.