[Nayira]

Summary

Lets users disconnect a health app and permanently delete the data imported from it, from a new "Connected health apps" section in Account Settings, with clear privacy messaging.

Closes #207
Part of #151

Stacked PR: based on #202 (feat/202-integration-architecture), which isn't merged yet. Until it is, this PR also shows the #202 commit. Please review only the top commit, "feat: add disconnect, delete-imported-data and privacy flows (#207)".

Changes Made

• Added POST /api/v1/users/me/connections/{id}/disconnect. It stops all future imports, keeps already imported data by default, and can delete it in the same step with { "delete_imported_data": true }. Disconnecting twice is not an error.
• Added DELETE /api/v1/users/me/connections/{id}/measurements, which permanently deletes that connection's imported records and returns deleted_count. Manually entered data is never touched.
• Both actions are scoped to the signed-in user. Other users' connections return the same 404 CONNECTION_NOT_FOUND as missing ones, so IDs cannot be probed.
• Both actions work without health consent and with the feature flag off, so users can always withdraw access and remove imported data.
• Connections now include imported_count.
• The user data export ([Small Rock] Add user data export and privacy controls #200) now includes connections and imported measurements (schema 1.2), so users can download a copy before deleting.
• Added a "Connected health apps" section to Account Settings → Privacy and your data. For each connection it shows the provider, status, allowed data types and imported record count, with Disconnect and Delete imported data buttons.
• Both actions need confirmation:
  • The disconnect dialog offers to delete imported data in the same step.
  • The delete dialog warns that deletion is permanent, and that a still-connected app may import again.
• The section handles loading, empty, load-failure with retry, success, failure, and connection-no-longer-exists states.
• Accessibility:
  • Results are announced through status and alert regions.
  • Dialogs open with Cancel focused, close on Escape and keep keyboard focus inside.
  • Focus returns to a sensible place after each action.
  • Buttons have provider-specific accessible names.
• Extended the shared ConfirmDialog with optional extra content, Escape to cancel, a focus trap and an initialFocus option. Its default behaviour is unchanged.
• Added translations for English, Spanish, Hindi, Arabic and Chinese, including plural forms. Updated the retention and export text so it no longer says no self-service deletion exists.
• Updated docs/integrations.md and docs/user-data-export.md.

Testing

• Full backend test suite passed (89 tests), including 14 new tests covering:
  • disconnecting, with and without deletion
  • disconnecting twice
  • deleting only one connection's records
  • deleting when there is nothing to delete
  • ownership (404 for other users)
  • malformed IDs
  • working without consent or the flag
  • authentication
  • reconnecting
  • the export section
• Full frontend test suite passed (209 tests), including 24 new tests covering every state, both flows, keyboard behaviour, Arabic right-to-left with plural forms, and a check that every locale has every connected-apps string.
• Frontend lint and production build passed.
• All 5 locale files validated as JSON.

Checklist

• The code follows project conventions
• Documentation has been updated if needed
• No sensitive information is included
• Breaking changes are clearly documented
• Reviewers have enough context to review this PR

Additional Notes

• There is no "connect a provider" screen yet. That belongs to the provider and device integration issues under [Big Rock] Add optional connected-health integrations #151. Until then, the section shows its empty state for real users.
• To try the flows locally, set INTEGRATIONS_ENABLED=true, grant a connection and import sample values through /docs, then open Account Settings.
• Deleting imported data does not change anything in the provider's own app.
• No breaking changes. The export schema_version moves from 1.1 to 1.2, adding a new integrations section.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud