KinLume

Consumer Health Data Notice

Draft notice about care information, its uses and your choices.

Template version: 2026-11-16-sms-authentication-draft

Draft policy text, pending final approval. The app currently requests acknowledgment of this template version. Final policy text and publication details are still under review.

Scope and sources

KWJ Ventures LLC offers KinLume, which lets adult account holders and authorized family members organize a care recipient's information. Consumer health data may include medications, doses, vital readings, appointments, care notes, emergency contacts, uploaded records, voice drafts, and health details in messages or receipts. It comes from adult care recipients, family members and caregivers, uploads, and optional features they choose to use. An authorized adult may also enter information about a minor care recipient. [Confirm all sources, any future integrations, and the jurisdictions covered, including minors' information.]

A role in a family group does not itself prove authority to provide another person's information. Do not enter or share health data unless you have the person's permission or another valid basis to act for them.

How health data is used

KinLume stores care information so authorized members can coordinate schedules, medication lists, documents and other requested care tasks. Selected health data may be used for optional AI, voice entry, emailed receipt processing or scheduled briefings only under the applicable separate controls. Manual entry remains available without optional AI processing.

[Confirm all categories, purposes and any data derived or inferred from health information before publication.] Policy acknowledgment records that a notice was reviewed; it does not by itself turn on optional data sharing.

Who can receive it

Health information entered into a family group is available to other members according to their role and recipient access. KinLume uses AWS services for identity, storage, messaging and requested processing. Optional AI uses Amazon Bedrock and voice entry uses Amazon Transcribe; payment providers receive subscription information rather than care records in the ordinary purchase flow. [Verify each processor, affiliate, recipient category and any other disclosures, including legal requests.]

Family AI and voice permissions are in the app’s Privacy & Safety settings. Organization document AI separately requires organization enablement, employee opt-in, documented care-recipient or authorized-representative approval, and any required permission for the exact family-shared file version. Withdrawing AI permission stops new processing; revoking a family document share ends organization access to that document and its dependent analyses. [Confirm whether any consumer health data is sold or shared for advertising; do not enable such use based on this notice.]

Storage, location and retention

The backend deployment is configured in AWS US East (N. Virginia); Bedrock inference may process through a cross-region profile. [Verify the deployed AWS regions, vendor locations and international transfer practices.] Family records and organization originals have separate deletion controls. Hiding or deleting a family copy does not delete the facility original or its version history. Applicable account-deletion and retention exceptions are described in the Privacy Policy. [Approve category-specific periods, backups, vendor retention and legal holds.]

Your choices and requests

In the app, Privacy & Safety provides permission controls, account export and deletion requests, and family-admin review of corrections for family records other than tasks and events. Family task and event requests are managed in Agenda → Change requests, where the record’s creator can update or decline them. You can also ask to access, correct or delete health information, withdraw optional sharing permission, or question a decision by contacting support@kin-lume.io. Please do not send medical records in ordinary support email; we may need to verify identity and authority through a secure method.

[Confirm jurisdiction-specific rights, request deadlines, appeals, and a way to identify recipients of disclosures before publication.] For general handling, read the Privacy Policy.