EverPacket Digital Product, Delivery, Compatibility and Local-Storage Disclosure

Effective date: August 26, 2026

Read this disclosure before creating a packet or buying EverPacket Full. It describes the product that is actually delivered, the local-storage boundary, known compatibility limits, and the actions needed to protect your work.

1. Product summary

EverPacket is a browser-based, local-first household-continuity organizer. It asks guided questions, stores the editable working packet in the browser profile on the device you use, and generates selected documents locally from that packet.

The product is delivered as a website and progressive web application. There is no physical shipment, no native app-store purchase in the current product, and no cloud repository of packet contents.

The exact checkout review and current product interface control if a feature changes. EverPacket will update this disclosure before offering a materially different product.

2. What an account does

An account stores identity, account settings, session, purchase, activation, recovery, consent, and other operational information described in the Privacy Policy. It can restore eligible Full access on another device after sign-in. Sign-in may use email verification codes and, when enabled and displayed, Google, Meta/Facebook, or Microsoft. A provider option may be temporarily unavailable while its production configuration or provider review is incomplete; no information is sent to a provider that you do not select.

An account does not:

• upload or synchronize a packet;

• transfer a packet to another device;

• back up packet contents;

• restore a packet after browser data is cleared or a device is lost; or

• give EverPacket support access to inspect a packet.

To move a packet, export an .EverPacket project file from the source browser and import that file in the destination browser.

3. Digital delivery

The initial paid launch is limited to transactions for which the Payment Merchant verifies a United States billing country. EverPacket may use a Cloudflare-provided country signal as a preliminary pre-check, but it relies on the Payment Merchant’s final billing-country record for fulfillment. A verified paid transaction reported with a United States billing country is ordinarily fulfilled even if the customer later uses EverPacket while travelling or from another country. If the Payment Merchant’s final record reports a billing country outside an approved market, EverPacket does not activate Full and arranges a prompt full refund through the Payment Merchant after provider reconciliation. Outside the approved paid market, the initial public experience is limited to public information, a content-free country-interest count, and ordinary outbound social-profile links; it does not create an account or authorize email.

EverPacket Full is delivered electronically. Delivery ordinarily requires:

1. review and acceptance of the current legal documents;

2. completion of hosted checkout with the Payment Merchant;

3. verified successful payment;

4. creation or sign-in to an eligible EverPacket account; and

5. attachment of the purchase to the account and confirmation of Full entitlement.

A purchase completed while signed out may require email-based setup or recovery before Full is available. A claim or return cookie helps continue that setup but is not itself the license.

Internet access is required for purchase review, checkout, payment verification, account setup, sign-in, entitlement refresh, recovery, refund, support email, and account changes. There is no download package containing your packet from EverPacket's servers.

4. Local storage model

4.1 IndexedDB

The editable packet, project metadata, revisions, checklist state, review state, local output history, and local backup history are stored in the browser's IndexedDB database for the browser profile you use. The current database name is everpacket.

The data remains until you delete it, the browser profile is removed, the browser or operating system clears it, storage is evicted, the device is reset or lost, or another device event removes it. Browser storage is not a guaranteed backup location.

4.2 Local and session storage

The product uses local storage and session storage for items such as theme, analytics choice, anonymous installation identifier, optional marketing visitor and session identifiers, closed attribution context, feedback and layout preferences, offline entitlement receipt, free-use acceptance receipt, short-lived writer leases, and tab identity. Optional marketing identifiers are created only after analytics is allowed and are removed or stopped when analytics is withdrawn as described in the Cookie and Device-Storage Notice.

4.3 Cache Storage and service worker

In production, a service worker may cache selected application-shell and public pages so the app can load or continue local work when connectivity is unavailable. Sign-in, checkout, purchase, account, and API requests are excluded from the ordinary offline cache.

A cached public page may be older than the live page. Do not rely on an offline legal page for a new purchase; the live version presented in checkout controls.

4.4 Cookies

Account, checkout, recovery, remember-session, security, and legal-flow functions use strictly necessary or preference cookies. When optional analytics is allowed, EverPacket may also use a server-readable analytics-permission cookie and a signed marketing-experiment assignment cookie. Disabling or clearing cookies may sign you out, interrupt activation, remove an optional experiment assignment, or require a new privacy choice. Cookie names, purposes, and durations are listed in the Cookie and Device-Storage Notice.

5. No EverPacket encryption of packet content

The current product does not encrypt packet records in browser IndexedDB and does not encrypt the exported .EverPacket project file.

An .EverPacket file is structured JSON data with a project envelope, packet contents, portable state, lineage information, history, and integrity values. The integrity value detects accidental change or corruption; it is not encryption and does not prevent reading or deliberate modification.

Anyone with access to the following may be able to read the packet:

• your logged-in device account or browser profile;

• browser developer tools or local device backups;

• the download folder or file-history service;

• a cloud drive, email attachment, messaging service, removable drive, or shared folder used to move the file;

• a PDF, contact card, QR code, printout, screenshot, or photocopy; or

• a recipient or third-party application that opens the output.

Use full-disk or device encryption, a screen lock, a private device account, protected backups, and careful sharing. EverPacket is not a password manager or encrypted vault.

6. Information that should not be stored

EverPacket is designed to point to the location of sensitive or official records rather than contain the records or secrets themselves. It may include limited healthcare contacts, care instructions, and locations of medication lists, allergy lists, advance directives, or other records. Those entries remain local through ordinary product use and are addressed in the Consumer Health Data Privacy Notice. Do not enter:

• passwords, passcodes, PINs, one-time codes, recovery codes, private keys, or authentication answers;

• complete payment-card, bank-account, brokerage-account, loan-account, insurance-policy, Social Security, tax-identification, passport, driver's-license, or other government-identification numbers;

• detailed medical records, clinical notes, test results, prescriptions, or information that belongs in a healthcare system;

• information whose disclosure would create a serious safety, identity-theft, financial, legal, or stalking risk; or

• unlawful content or information you do not have a lawful basis to record or share.

Product warnings cannot detect every risky entry. Review your content and outputs yourself.

7. Project-file format and import limits

The current .EverPacket project-file implementation uses a versioned JSON envelope. The parser accepts the supported format version, validates structure and integrity, and imposes safety limits including approximately:

• maximum file size: 5 megabytes;

• maximum structural depth: 32 levels; and

• maximum entity count: 2,000 items.

A file produced by a newer unsupported format may require an application update. A damaged, modified, oversized, deeply nested, or invalid file may be rejected. Import creates a new local project and is designed not to overwrite an existing project.

File-format limits may change to address security, compatibility, or product needs. The app's current import message controls. Keep at least one known-good backup and test imports periodically.

8. Generated outputs

EverPacket can generate outputs such as:

• a free one-page emergency sheet;

• a full packet PDF;

• situation-specific or custom PDFs;

• a vCard/contact-card file; and

• a QR code containing a contact-card payload.

PDF generation occurs in the browser. Current paper options include U.S. Letter and A4, and current text-size options include standard and large. The browser's PDF viewer, print dialog, fonts, printer driver, page scaling, margins, duplex settings, and paper supply can affect the result.

Review every output before relying on or sharing it. Verify that text is complete, pages are present, QR codes scan correctly, contact cards import correctly, and print settings match the intended paper.

9. Paid-output authorization during the refund window

During an applicable voluntary refund window, a paid PDF or contact card may require a short online authorization tied to the signed-in purchase. The authorization must not reveal packet contents.

A refund-disqualifying event is recorded only after successful local file creation and a permitted user-initiated handoff. For a paid PDF, the permitted completion bases are download, print, or share. For a contact-card file, they are download or share. A QR preview, PDF preview, project-file import or export, authorization request, failed render, closed tab, blocked handoff, or other unsuccessful attempt is not a completed paid output. See the Refund, Cancellation and Withdrawal Policy.

Outside the refund window, after a valid paid-output completion has already been recorded for the purchase, or where the current entitlement receipt otherwise permits, supported outputs may operate offline. The exact behavior can vary by release and legal requirements.

10. Compatibility requirements

EverPacket requires a device and browser that support the following:

• a reasonably current JavaScript implementation;

• IndexedDB and local storage;

• cookies for account, purchase, or recovery features;

• Web Crypto or equivalent browser cryptographic functions used for integrity and signed receipt verification;

• Blob, object URL, file input, file download, and JSON parsing;

• PDF rendering or download and a print workflow;

• service workers and Cache Storage for full offline-shell behavior, where supported; and

• BroadcastChannel or fallback browser coordination for multi-tab safety, where supported.

The product's automated browser suite currently exercises representative versions of desktop Chromium/Chrome, desktop WebKit/Safari, desktop Firefox, a Pixel-class mobile Chromium profile, and an iPad Safari profile. Test coverage is not a warranty that every device, version, extension, managed-browser policy, embedded browser, or assistive technology will work.

11. Known compatibility and storage risks

The Service may be limited or fail when:

• JavaScript, cookies, IndexedDB, downloads, pop-ups, or service workers are disabled;

• the browser is in private, incognito, guest, kiosk, or ephemeral mode;

• an enterprise or school policy blocks storage, downloads, identity providers, Stripe, Supabase, Cloudflare, or email codes;

• storage quota is exhausted or the operating system evicts website data;

• a content blocker changes scripts, cookies, network requests, fonts, or downloads;

• an in-app browser lacks complete file or PDF support;

• the device has insufficient memory for a large PDF;

• the browser is outdated or no longer supported by its vendor;

• the operating system cannot open .EverPacket, .pdf, or .vcf files with the chosen application;

• a printer, PDF viewer, QR scanner, or contacts app interprets the file differently; or

• the same packet is edited simultaneously in multiple tabs or copied browser profiles despite writer-lease protections.

Use a current standalone browser, keep one editing tab, allow local storage, and maintain backups. For a purchase decision, test the free workflow and emergency-sheet generation on the intended device first.

12. Offline behavior

After a successful online load in a supported production browser, the cached application shell and local data may permit continued editing and supported local outputs without a network connection.

The following ordinarily remain online-only:

• sign-in and identity-provider redirects;

• account creation, recovery, and deletion;

• checkout, payment, activation, refund, and dispute functions;

• entitlement refresh and any paid-output authorization required during a refund window;

• support submission and transactional email; and

• server-recorded consent, legal acceptance, security, or account operations.

Offline operation is not guaranteed. A service-worker update, browser policy, cache eviction, corrupted cache, or unsupported feature may require reconnection.

13. Moving to another device

To move a packet:

1. export a current .EverPacket project file from the original device;

2. save it through a storage or transfer method you trust;

3. sign in on the destination device if Full access is needed;

4. import the project file; and

5. verify the imported project, output settings, and backup status.

Signing in alone will not move the packet. Emailing or cloud-syncing the project file may expose its unencrypted contents to the chosen provider or anyone with access to the account.

14. Backup responsibility

Maintain at least one recent project-file backup outside the browser profile. The appropriate location depends on sensitivity. Consider an encrypted device or encrypted storage container that you control.

A useful backup practice is:

• export after material edits;

• retain a small number of dated versions;

• keep one copy separate from the primary device;

• test an import periodically; and

• securely remove obsolete copies.

EverPacket's backup-status indicator is an organizational reminder. It is not proof that the file still exists, is readable, is secure, or is stored off-device.

15. Updates and support lifecycle

A Full purchase includes the generally available product edition and updates that EverPacket identifies as included, plus any security, compatibility, conformity, accessibility, or other updates required by applicable law.

The product must not promise “lifetime updates” or perpetual compatibility. A future separately sold edition may require a new purchase, but a new edition label does not remove a mandatory duty to keep the purchased digital content conforming and secure for the period reasonably expected under applicable law.

16. Accessibility

EverPacket aims to support keyboard navigation, readable structure, scalable text, high-contrast interfaces, and accessible output options, but it does not claim complete conformance until an accessibility audit confirms it. The Accessibility Statement identifies current status, known limits, and a support route.

Some browser PDF viewers, print dialogs, generated PDFs, QR scanners, contact applications, or third-party checkout and identity pages may have separate accessibility limitations.

17. Customer responsibilities before purchase

Before purchasing Full:

• use the free workflow on the intended device and browser;

• confirm that local storage and file downloads work;

• read the Terms, Privacy Policy, Refund Policy, Consumer Health Data Privacy Notice, and this disclosure;

• understand that packet contents are not synced or recovered by the account;

• understand that local packet data and project files are not encrypted by EverPacket;

• confirm that the displayed checkout total and currency are acceptable; and

• save the receipt and accepted legal documents.

18. Product support and defects

Contact support@everpacket.com with content-blind information such as the application version, browser family, operating-system or device category, generic error code, approximate time, and steps needed to reproduce the problem.

When the support form displays an attachment control, you may submit one optional, redacted PNG or JPEG image no larger than 15 MiB, subject to the Terms of Use and Privacy Policy. The image may show only the application shell, a generic error state, or another content-free interface, browser, payment, or support problem.

Do not submit an .EverPacket project file, generated packet PDF, contact card, QR output, screenshot showing packet entries or a QR payload, credentials, recovery information, payment information, identification, medical information, household information, or other sensitive content. EverPacket cannot inspect, recover, or repair a local packet through a support attachment.

If the digital product is defective, unavailable, misdescribed, incompatible with a disclosed supported environment, or otherwise non-conforming, EverPacket will provide the repair, replacement, price reduction, cancellation, refund, or other remedy required by applicable law. The voluntary refund policy is additional to those rights.

19. Seller and contact information

Software operator, provider, and licensor
Kimi Chen, a California sole proprietor doing business as EverPacket
8843 Villa La Jolla Drive Apt 2, La Jolla, CA 92037
San Diego, California, USA
Support: support@everpacket.com

Payment Merchant
The legal entity identified by Stripe or Link at checkout and on the receipt is the merchant of record for the transaction. Its legal name, address, final price, tax, payment terms, and transaction-support channel are shown in the hosted checkout or receipt.