Privacy

Aggregate analytics: Values in Care uses its own analytics service, run by its owner, to produce aggregate usage statistics. It sets no cookies and builds no profiles. The service is built not to read or store your IP address or browser details, though your browser's request reaches its host as any web request does. It records the page path (with identifiers and anything after a ? or # removed), device class, referring site, browser language, scroll depth, time on page, clicks on links and buttons (their visible label, never text typed into a field), outbound and download links, form submissions (the form's name only), and browser error messages. A random session ID lives in this tab's session storage and ends when the tab closes. Counts are kept for 400 days. The service honors Do Not Track and Global Privacy Control. To opt out in this browser, turn on either signal or open any Values in Care page with ?ah_optout=1 added to its address.

Hosting statistics: The site is hosted on Lovable. Its hosting platform loads a first-party script that sends page-view requests to this site's own address and stores a random visitor ID and a session ID in this browser's local storage (keys beginning with __lovable_). The platform uses these to show the site owner aggregate counts of visits, pages viewed, referring sites, device types, and countries. The preparation tools never put what you type into page addresses, so these requests do not include it.

Fonts: Page text uses fonts served by Google Fonts. Loading them sends your IP address and browser details to Google, as any web request does. If the request is blocked, your device's own fonts display instead.

Which actions are counted: Beyond page views and clicks, the service counts five event families, and this is the complete list:

• lens-select: which audience view was chosen.
• tool-complete: that a tool was finished, and which one.
• print-or-export: that a page or local tool was copied, printed, or exported, and which feature/method was used.
• share: that a page was shared, and by which method.
• partner-inquiry: that someone followed a Get Involved route or submitted the form, and from where. Never the message itself.

Each analytics event carries short page, feature, or method labels and no free text. Each event has its own list of allowed labels in the code, and anything outside the list is dropped before it is sent. Anything you type into a preparation tool is excluded from analytics by construction, including selected priorities, spiritual concerns and draft identifiers. Search terms stay in the page and are not written to the address bar.

What stays on your device: Content created in the Decision Guide, My Values, and the Conversation Brief Workspace is stored in your browser's local storage so you can return to it on that device. On a shared device, each of these tools can keep it in this tab only instead. A thought written on the Reflect page is different: it stays in the page's memory and goes into storage only when you choose Save on this device (or Save in this tab on a shared device). Leaving the page without saving discards it. Saving and including are separate choices. Only thoughts you mark Include in my note appear in the note you can copy, download or print, and the note does not name or count the rest. Source Watch stores only the IDs of sources you choose to watch. Nothing typed into the preparation tools, and no Source Watch list, is intentionally transmitted to a Values in Care server. Aggregate analytics may record that a tool was completed or exported, never what was written or which sources you watch.

The Decision Guide is deliberately bounded: Free-text fields have length limits, stored value identifiers are validated when reloaded, and Start blank removes the local Decision Guide draft. Saved copies are capped at twelve and can be deleted one at a time or all at once. These controls reduce accidental browser-storage growth; they do not turn local storage into a secure medical record. Conversation mode keeps its marks in memory and discards them on close unless you carry them to the debrief. The debrief is stored with the draft. The revisit calendar file is built in your browser, and its title is generic.

The optional ConditionMap link: If the condition you type names exactly one ConditionMap page, the Decision Guide shows a link to it. The match runs in your browser against a list of condition names bundled with Values in Care. Nothing is sent unless you click. If you click, your browser opens that condition's page on conditionmap.com, so ConditionMap receives the page address like any visit. No notes, priorities, or other text go with it.

Shared devices: The Conversation Brief Workspace can keep a draft in this tab's session storage instead of the browser's lasting storage. Browsers usually discard session storage when the tab closes, but reopening a closed tab or restoring a session can bring it back, and duplicating the tab copies it. It is not secure erasure. Drafts and saved copies already on the device are not removed or overwritten when you switch; delete them separately. Only what you mark to share appears in the preview, printout, download or handoff, and those outputs do not list what you held back. Deleting the current draft does not delete saved copies, and deleting saved copies does not delete the current draft. Saved thoughts on the Reflect page follow the same tab choice and can be deleted one at a time or all at once; thoughts saved in the other store are not deleted when you switch. Nothing here can recall a file you downloaded, a page you printed, or text you copied. If your browser blocks storage, the page says the draft was not saved. None of this makes a browser suitable for patient records; institution-approved research or clinical use needs a different, governed system.

Local storage is still data: A draft can contain sensitive health-related priorities or questions even though Values in Care does not receive it. Anyone with access to the same browser profile or device can read what is stored there. Use Reset, clear this browser's storage for Values in Care, or work in a private browser window when that risk matters to you.

No tracking cookies or required accounts: Values in Care does not use tracking cookies, and core public decision tools do not require a user account.

Do not submit health data: The interactive preparation tools are not a medical record. Please do not put patient names, diagnoses, medical-record numbers, or other health information in the Get Involved form. If you type health-related information into a local preparation tool, keep in mind the device-access risk described above.

No third-party advertising: Values in Care has no ads, no ad networks, and no behavioral targeting.