Privacy Policy

Who operates this product

Living Well is a product of Luminosity Development LLC, offered at getlivingwell.com. This policy describes the product as it works today. This is not legal advice. Counsel should review it before you rely on it for a regulated market.

To ask a question or request access or deletion, use Feedback on getlivingwell.com. That is the support path on the site. You can also download a JSON copy of your map or delete the account from Settings while you are signed in.

Designed for the United States

Living Well is designed for and marketed to people in the United States. We do not target or market it to the European Union, the European Economic Area, or the United Kingdom. We do not block visitors by country. If you reach this site from the EU, the EEA, the UK, or anywhere else, you may create an account. The same practices in this policy apply. Information is processed in the United States, as described under Where it is hosted and People outside the United States.

Account and sign-in

When you create an account we store:

• The email address you use to sign in.
• A password hash if you choose email and password. We do not store the password itself.
• If you sign in with Microsoft, the link Auth.js keeps for that Microsoft account so the sign-in can continue. We do not receive your Microsoft password.
• An optional display name, and the dates the account was created and updated.

What you put on the map

The map you type is stored with your account. That includes:

• People: name, relationship, roles, email, phone, and notes.
• Assets, assignments (who should receive an item, share, and notes), and photos.
• Life stories.
• Funeral wishes, including an optional cost band and a preferred funeral home name or website, and any obituary draft saved on the account.
• Healthcare wishes: preferences and a designated decision-maker (and an optional backup). These notes are not a living will, POLST, or DNR.
• The post-loss playbook (checklist items and notes).
• Settle-the-estate board tasks, including assignees and status. That board is not a court filing.
• Digital-account pointers: provider, what you want done, where credentials live, and an optional handle. Passwords for those accounts are not stored.
• Household operating-manual notes (utilities, keys, vendors, and similar, including an optional account label). Passwords are not stored there.
• Document metadata (title, category, notes, and link or file details). File bytes you upload, and asset photo bytes, go to private Azure Blob containers.
• Executor invites: who the invite is for, status, and the secret token in the link.
• Section-reveal preferences for each major section, including an in-app death confirmation timestamp if one is recorded (who confirmed, when, and which invite). That record is not legal proof of death.

Feedback

If you send Feedback from the header, we store the message, an optional subject, the page you were on (path and URL), and a user-agent string. Signed-in notes keep your account id. Anonymous notes do not. We email that note to the Living Well inbox (by default feedback@getlivingwell.com) through Azure Communication Services, from the configured sender (for example noreply@getlivingwell.com). The email for a signed-in note can include your account email so we know who wrote. Deleting your account unlinks your id from those rows. The note itself may remain.

The same Azure Communication Services channel is how this product sends transactional mail. We do not send advertising or newsletter email.

Connected apps

You can connect an assistant you already use (for example Grok Bot, Claude, or ChatGPT) from Settings. That app can read your stories and the names of people on your map, add or edit stories, create categories only you see, and attach photos. Stories and edits from an app stay drafts until you approve them. Connected apps cannot delete stories. Access uses a short-lived sign-in token or a personal token you create. We store only a hash of those tokens. You can revoke a connection immediately. Photos are reduced before storage, and the original file, including location data, is not kept.

Draft obituary with AI

If you choose Draft obituary with AI on Wishes, Living Well sends selected facts you already saved — your display name, people, life stories, and funeral notes — to Azure AI Services (OpenAI-compatible chat completions) to produce a draft. That draft stays in your account until you edit or delete it. The button does nothing until the Azure AI settings are configured on the server. We send those facts to produce the draft you asked for. We do not use them to show you ads.

Invites and section unlock

Executors you invite can see a view-only snapshot of the current map if they have the secret link. We do not email that link for you; you share it. For each major section you can choose executor-now, after an in-app proof of death, public now, or a release date and time. Public now is stored as the least-restricted option. Today it still uses the same invite link, because there is no separate public map. Locked content stays omitted from that view, the invite PDF, and the invite JSON until the chosen event. An in-app death confirmation records who confirmed and when. It is not legal proof of death. Invitees do not get your password or Settings.

Cookies

We use essential cookies only: Auth.js cookies for sign-in, and Azure App Service cookies that keep a browser on one instance. We do not use advertising or analytics cookies, and this site does not show a cookie-consent banner. Names and purposes are on the Cookies page.

Where it is hosted

Hosting is Azure App Service, Azure Database for MySQL, and Azure Blob Storage in the United States region we configured. The obituary draft request goes to Azure AI Services. Email goes through Azure Communication Services.

People outside the United States

If you use Living Well from outside the United States, including from the European Union, the European Economic Area, the United Kingdom, or another country, we process information as this policy describes. We do not block that access, and we do not market the product there. Hosting remains Azure in the United States, so use from outside the United States is an international transfer to the United States. We have not published a separate Standard Contractual Clauses packet. You may contact Luminosity Development LLC through Feedback on getlivingwell.com to ask for access to or deletion of the information we hold about you. While signed in, you can also download the JSON export or delete the account from Settings.

Ads and sales

We do not run ads on this product. We do not sell personal information, and we do not share it for cross-context behavioral advertising.

Export and deletion

From Settings you can download a JSON copy of your map: people, assets, assignments, stories, funeral and healthcare wishes, playbook, board tasks, digital-account pointers, household notes, document metadata, invite status, and section-reveal settings. Invite tokens, password hashes, and file bytes stay out of that file. Photo and document bytes remain in Azure Blob until deleted.

You can delete the account from Settings. Deletion removes the MySQL rows for your user (database cascade) and best-effort deletes your blobs. Invite links stop working because those rows are gone. After deletion we cannot restore the map. Feedback notes may remain with your account id removed.

Changes

This policy is effective September 22, 2026. If we change it, we will post the updated text on this page and change the effective date.

Questions: Luminosity Development LLC, through Feedback on getlivingwell.com. Living Well organizes your intentions. It is not a substitute for an attorney.