A privacy-first household continuity tool that turns critical personal information into a structured, portable packet for the people who may need it most.
The problem
Most households have critical details scattered across apps, folders, documents, and people’s heads. This includes emergency contacts, insurance records, medical information, accounts, instructions, and everyday logistics. That arrangement works until someone else suddenly needs to find or act on the information.
I designed EverPacket to guide users through organizing those details once, then generate focused outputs for emergencies, travel, surgery, caregiving, or transferring responsibilities to another family member. Recipients do not need to navigate the original application. Users can export the result as portable PDFs, contact cards, QR codes, and an editable EverPacket file.
Privacy as a system boundary
Privacy shaped the architecture from the beginning. Packet contents can be highly personal, so EverPacket stores them locally in the browser with IndexedDB. Document generation and local search also run client-side. The application backend handles authentication, purchase entitlements, and other account-level metadata without storing the contents of a household’s packet.
This boundary keeps the product useful without turning it into a centralized vault of sensitive household data. Signing in restores a purchase, not a packet.
Technical highlights
- Built the application with Next.js, TypeScript, and React, then deployed it on Cloudflare.
- Designed a local-first data model backed by IndexedDB, keeping sensitive packet contents on the user’s device.
- Implemented client-side generation of synchronized PDF variants, allowing one source packet to produce different views for different situations.
- Created a portable
.EverPacketfile format so users can retain an editable copy outside browser storage. - Added contact export through vCard files in the
.vcfformat and QR codes for compatibility with existing phone and contact workflows. - Built authentication and entitlement infrastructure with Supabase, separating account state from locally stored household data.
- Integrated a checkout-first, one-time purchase model with account-linked purchases and entitlement revocation after refunds or disputes.
- Designed concurrency and file-lineage safeguards to prevent conflicts when the same packet is opened or modified in multiple places.
Product and system design
EverPacket required more than implementing individual features. I defined the product scope, information architecture, privacy model, authentication flow, monetization strategy, export system, visual identity, and supporting infrastructure from the ground up.
One of the central design challenges was balancing completeness with usability. Asking users to document everything at once creates an overwhelming experience, while collecting too little defeats the purpose of an emergency handoff. I structured the product around guided data entry and reusable source information. Users maintain one underlying packet, then generate smaller outputs for the person and situation that actually need them.
Designed for handoff
EverPacket is designed around handoff rather than storage. The goal is not simply to hold information. It is to make sure the right information can be understood and used by someone else when the original user may not be available.