Privacy Policy

Family Elder Planning is designed to help families organize practical elder-care tasks without asking for sensitive medical details.

Last updated: August 12, 2026

Privacy at a glance

Planner notes stay on your device

The custom planner runs in your browser. We do not save your planner notes, loved-one names, medication names, symptoms, family notes, or other free-text planning details on our servers.

Family Care Coordination System

The Family Care System uses IndexedDB to autosave care-plan information in this browser on this device. Family Elder Planning does not receive the names, notes, medication information, appointments, tasks, coverage details, handoffs, or other free text entered in the local plan. There is no cloud care profile or live cloud collaboration. Another person using the same browser profile may be able to see local information, and clearing site data can erase it.

A Family File is an optional portable backup/export containing the full plan. It is created and checked in the browser and should be handled like a sensitive document. Sponsor branding, entitlement records, checkout metadata, and partner reporting identifiers are not stored in the Family File.

First Night Home Quick Sheet delivery

The Quick Sheet is available immediately in the browser without providing an email address. If you ask us to email the return link, we use your email address and optional first name only to send that requested resource through the existing Resend email provider. Requesting the resource does not add you to a marketing audience or mailing list.

To prevent misuse of the delivery form, short-lived rate-limit counters are kept in the site's existing private storage. The counter keys use keyed one-way fingerprints rather than raw email or network addresses, contain no form content, and expire by time window. Resend also receives a non-identifying idempotency key so a repeated request does not send the same delivery again within its provider window.

A separate future-email checkbox is optional and unchecked by default. If you check it, the current bounded workflow sends a consent record to the site operator for manual review. It is not bundled with transactional delivery, and there is no automated audience database. If that consent record cannot be captured, the site says so and does not treat the resource request as marketing consent.

Future-service interest

If you join the future guided-help interest list, we collect first name, email address, selected planning category, selected care phase, urgency band, and source page. This interest form is for validation and future resource updates only; it does not start a guided-planning service. Do not include medical details.

Support messages

If you contact support, we collect the information you choose to send, such as your name, email, order email, issue type, and message. Please do not include medical details, diagnosis details, medication names, Social Security numbers, payment card numbers, or other sensitive information in a support message.

Home Kit suggestions

If you suggest an addition to the First 14 Days Home Kit, we store only a generalized topic for review and may send that topic to the site operator by email. We do not store or email your exact suggestion text. Public voting is limited to approved request categories. New suggestion topics are not posted publicly unless they are reviewed, normalized, and added as a general category. Please do not include names, diagnoses, medication names, urgent symptoms, phone numbers, email addresses, or other sensitive details in a suggestion.

Analytics

We use privacy-safe event tracking to understand whether visitors use the checklist, planner, Quick Sheet, professional sharing handout, print/copy buttons, feedback buttons, paid-kit links, topic chooser, and next-step assessment. Analytics events are limited to allowlisted metadata such as page path, source, counts, booleans, selected care phase, selected scenario type, selected planning category, urgency band, destination type, recommendation rank, feedback context, delivery-provider configuration status, and a random anonymous browser-session ID.

Analytics events do not include emails, names, consent text or selections, form bodies, loved-one names, symptoms, medication names, free-text notes, family notes, IP addresses, query strings, full referrer URLs, or user-agent logs.

Partner-sponsored activity

Real partner activity collection is currently disabled. If a legally reviewed sponsored pilot is later activated, the system may count only eight allowlisted operational activity events plus authoritative successful activation exchanges and separately aggregated support records. These counts contain no family identity, care-plan value, free text, Family File, URL, IP address, persistent visitor identifier, or raw token. Test, demo, owner, and professional-evaluation traffic is excluded. Partner-visible values 1–4 are suppressed, raw accepted events are limited to 120 days, and aggregate briefs are limited to 24 months unless reviewed terms or law require a different period.

A sponsor cannot see a family’s local plan. Optional sponsor contact actions leave Family Elder Planning, do not attach plan information, and are then governed by the sponsor’s own privacy practices.

Payments

Payments are handled by Stripe. Family Elder Planning does not collect or store payment card numbers. Stripe may process your payment and receipt information according to Stripe's own privacy and security practices. Family Elder Planning entitlement records contain product/payment-state metadata needed to provide or revoke access, not care-plan information. Care details and Family Files are not sent to Stripe metadata or email.

Cookies and local storage

The site may use browser features needed for normal page behavior, local IndexedDB autosave, signed HttpOnly product-access cookies, payment checkout through Stripe, the Home Kit request voting control, or internal testing controls. Product access metadata is separate from care-plan content. We do not use the planner to store your health notes on our servers.

Contact

For privacy or support questions, use the contact page. For medical and editorial boundaries, read the medical disclaimer and editorial policy.