Last updated July 18, 2026
Consumer Health Data Privacy
This policy explains how the guide handles consumer health data. Share only what is useful for educational planning and attorney preparation.
Categories we collect
Health and care information
Conditions, diagnoses, cognitive or functional status, activities-of-daily-living needs, safety concerns, care setting, care needs, health coverage, long-term-care coverage, and benefits information you choose to provide.
Related planning context
Age or age range, state, family and caregiver relationships, legal-authority status, financial ranges, housing, veteran status, planning goals, and similar facts when they are linked or reasonably linkable to health or care needs.
Health-related inferences
Readiness flags, summaries, care-planning context, and other inferences the guide creates from the information you provide.
Security metadata when reasonably linkable to health use
Country-level location derived from a public IP address, a short-lived anonymous session identifier, HMAC-protected session and IP identifiers, request counts, verification results, timestamps, response status, and similar access-control or abuse-prevention data.
We do not need Social Security numbers, benefit ID numbers, account numbers, passwords, full medical records, or exact financial-account credentials. Do not enter them.
Sources
- You, when you type a message, answer a question, select a state, build a planning profile, or request a report.
- A family member, caregiver, or other person using the guide when they provide information about someone else.
- The guide itself, when it organizes answers into a profile or infers planning and attorney-preparation topics from those answers.
- The browser and ordinary web infrastructure, only for the limited session, security, and verification metadata described above.
We do not buy consumer health data or obtain it from data brokers.
Why we collect and use it
- Provide the educational conversation and organize the facts the user asks us to process.
- Personalize attorney-preparation questions, education, state context, and the online or downloadable report.
- Maintain the browser-saved session and let the user clear or restart it.
- Enforce the service restriction to requests geolocated to the United States.
- Validate requests, prevent automated abuse, enforce usage limits, troubleshoot failures, and protect the service.
- Comply with applicable law and respond to valid privacy requests.
We do not sell consumer health data or use it for targeted advertising, cross-context behavioral advertising, or unrelated marketing.
Processor and recipient categories
We disclose only the categories needed for providers to perform the service functions below on our behalf and consistently with the purpose for which the data was collected. We do not share consumer health data with affiliates, and we do not disclose it to third parties for their independent advertising, profiling, or marketing use.
AI processing provider
Processes the conversation, planning profile, and related prompt context needed to generate a response. Under the current standard API controls, inputs and outputs are automatically deleted within 30 days, subject to security, legal, or account-specific exceptions.
Hosting and application-infrastructure provider
Derives a country code from the requester's public IP address to enforce US-only access, transmits and processes allowed requests, responses, and report inputs, and may keep routine short-window infrastructure and security logs. We do not intentionally place chat or profile content in routine application logs.
Counter-storage provider
Stores HMAC-protected session/IP identifiers and request, token, and verification counters. It is not intentionally sent chat messages or planning profiles. Burst counters expire after about 10 minutes and the other current counters expire within about 24 hours.
Bot-verification provider
Processes browser, device, network, challenge, and token signals if a verification step is triggered. It is not intentionally sent the chat transcript or planning profile.
Retention
The conversation and planning profile saved in your browser remain there until you use New Conversation, clear this site's browser data, or the browser removes them. Anyone with access to that browser profile may be able to see them.
We do not maintain a server-side conversation database. Chat content sent to the AI processing provider is subject to the standard API retention period of up to 30 days described above. The security cookie and current daily counters expire within about 24 hours, and burst counters expire after about 10 minutes.
Routine application and infrastructure logs remain only for the provider or account retention window used to operate and secure the service. They are not copied into a long-term user analytics database.
Your consumer health data rights
Depending on applicable law, you may ask us to confirm whether we collect, share, or sell consumer health data concerning you; access that data; withdraw consent; or delete that data, including deletion requests passed to processors where required. We do not sell consumer health data.
You can delete the browser-saved conversation and profile by using New Conversation or clearing this site's browser storage. To make another request, email privacy@elderlawprep.com. Because the guide has no accounts and avoids a server-side conversation database, we may need enough information to authenticate the request and determine whether any responsive data still exists.
If we deny a request, you may appeal by replying to our decision or emailing the same address with “Privacy appeal” in the subject line. We will explain the result and any further complaint option required by applicable law.
Changes to categories or purposes
We will update this policy before collecting, using, or disclosing additional categories of consumer health data or using existing data for a materially different purpose. Where required, we will request a new affirmative consent before that additional processing.