mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 23:33:29 +00:00
fix(copy): say what the AI provider receives and what is encrypted
The "Send raw data" switch promised anonymised single readings from the last 30 days. It sends bucket averages from the rollup table: per day for the last 90 days, per week for the year before, per month back to five years, each with its date and reading count. The label, both descriptions and the warning now say that, and the "off" text no longer claims the summaries carry no individual value (they include the latest one). The data-posture line and the Coach's own description of the app said all health data is encrypted at rest and nothing leaves the instance beyond the AI provider. Free text, documents, questionnaire answers, AI-written text and tokens are encrypted; measurement values, lab values, medication names and mood scores are not. Both now say so, and the Coach is told not to claim otherwise. Two narrower absolutes are scoped to what they cover: the local-model onboarding title and the off-host backup card. All seven locales.
This commit is contained in:
1 parent
13db7935f6
commit
228c5c9da6
9 files changed
+59
-54
No files matched your search
@@ -134,7 +134,7 @@ describe("<DoneScreen> AI panel", () => {
|
||||
const html = render();
|
||||
expect(html).toContain('data-slot="onboarding-ai-panel"');
|
||||
// Local model is surfaced first (the calm private default).
|
||||
expect(html).toContain("nothing leaves your network");
|
||||
expect(html).toContain("AI requests stay on your network");
|
||||
// The honest release valve is present and prominent.
|
||||
expect(html).toContain('data-slot="onboarding-ai-keyless"');
|
||||
expect(html).toContain("fully useful without AI");
|
||||
|
||||
@@ -294,10 +294,15 @@ GROUND RULES
|
||||
visualise and export their OWN data. It is NOT a medical device and does
|
||||
NOT diagnose, treat, cure or prevent any disease; you are an
|
||||
informational assistant, not a doctor, and what you offer is not medical
|
||||
advice. On data: the user's health data stays on their own instance,
|
||||
encrypted at rest; AI runs on a provider key they bring or a local
|
||||
model, so nothing leaves their instance beyond the provider they
|
||||
configured, and there is no third-party analytics on their health data.
|
||||
advice. On data: the user's health data lives in their own instance's
|
||||
database. Notes and other free text, documents, questionnaire answers,
|
||||
AI-written text and access tokens are encrypted at rest; measurement
|
||||
values, lab values, medication names and mood scores are stored
|
||||
unencrypted and rely on the security of the server. AI features send
|
||||
data only to the AI provider set up for the account, and there is no
|
||||
third-party analytics on their health data. Do not claim that
|
||||
everything is encrypted or that nothing ever leaves the server: the
|
||||
operator can connect integrations, backups and other services.
|
||||
State this plainly and calmly when relevant; never oversell it as
|
||||
confidential like a clinician's, and keep deferring diagnosis /
|
||||
treatment / dose questions to a healthcare professional.
|
||||
|
||||
Reference in new issue
Block a user