Privacy Policy
How information is handled when you use KinLume and the KinLume website.
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.
Who we are
This draft Privacy Policy describes how KWJ Ventures LLC, operating as KinLume, handles information in the mobile app, public website, organization portal, and separate staff support portal.
[Confirm geographic scope before publication.]
Information we collect
Depending on the features you use, information may include name, email, date of birth provided at registration to check adult eligibility, account and device identifiers, family memberships, schedules and tasks, care records, medications, vitals, documents, receipts, expenses, uploaded files, messages, and support correspondence.
Information about a care recipient may be entered by that person or by family members and caregivers. Only share information you are authorized to provide.
The service also processes sign-in and security events, API and operational logs, subscription verification and transaction records, and device tokens if you enable push notifications. [Confirm each automatically collected field and any analytics or advertising technology.]
How we use information
We use information to screen accounts for the 18-and-older requirement, authenticate accounts, manage family access, store and display requested care information, send configured notifications, verify purchases, handle support and privacy requests, prevent abuse, and maintain security and reliability.
Optional AI, voice, automatic email receipt extraction and scheduled briefings have separate in-app data-sharing permissions. [Confirm any analytics, product improvement, marketing or other uses before publication.]
If you type in the optional event-venue search, the venue query alone is sent to Google Maps Platform to suggest places. Event titles, care recipient names and notes are not included by the app. You can enter a venue manually without using suggestions or granting location permission. Google's handling of a search is described in the Google Privacy Policy.
Phone verification and account texts
If you choose phone registration or password recovery and agree to the separate text-message disclosure, KinLume uses your phone number to send the authentication codes you request through AWS and telecommunications delivery providers. This permission is for account verification and password recovery, not marketing. Phone numbers are account identifiers; delivery and security processing can include limited service records. The text consent shown during signup or recovery is distinct from optional AI permissions.
We do not sell or share phone numbers or text-message opt-in consent with third parties for their own marketing or promotional purposes. Providers may process the information needed to deliver and protect the authentication service.
One code text is sent per request; message frequency varies with your requests, and message and data rates may apply. Reply STOP to stop texts or HELP for help. After STOP, text START or UNSTOP to the same sender number to resume. Requesting another code alone does not resume texts. Stopping texts can prevent phone verification and password recovery; email registration is an alternative. For help or questions about your information, contact support@kin-lume.io. See the account verification text terms.
Organizations and family connections
Organizations may provide their company name and logo, facility details, resident identifiers and care profiles, staff/contact emails, assignments, work records, and billing information. Roster uploads support organization-defined columns and reviewed mappings. Imports create care profiles and invitation drafts; verified registration is required for sign-in access.
Organization roles and current resident assignments govern staff access. Facility-only work stays outside family feeds. A connected family can receive shared work and documents, explicitly share selected family records, revoke those shares, or disconnect the organization. Organization membership does not give staff general access to a family's Vault.
Facility work and document originals stay with the resident’s organization enrollment. Family copies are separate: family edits, hiding, deletion or disconnection do not change the facility original or its version history. Earlier facility records and document offers require family review before acceptance; later corrections can be reviewed as new copies. Families can withdraw their submitted request text while the organization keeps its own handling history.
Company branding appears in the organization workspace and on sponsored recipients' app headers. Uploaded roster data is cleared after a successful import; abandoned staging expires after 24 hours. Saved resident, work, audit, and billing records follow their applicable retention rules. Closing an organization does not delete an independent family's records. [Approve organization-specific retention and contractual responsibilities before launch.]
Voice and AI features
Optional AI may send selected care history, documents, receipts or questions to Amazon Bedrock for Anthropic Claude processing. Voice entry can send audio to Amazon Transcribe, then a transcript to Bedrock to suggest form fields. AI can be wrong; review suggested results and original records before saving or relying on them.
Use Privacy & Safety in the app for family AI and voice permissions. Organization document AI has separate controls in the organization workspace and family connection: organization enablement, employee opt-in, documented recipient approval, and explicit permission for a family-shared file version are distinct choices. Withdrawing stops new transmissions but cannot recall a request already sent. Unsaved voice drafts are scheduled to expire after 24 hours; saved records follow their ordinary retention rules. [Verify vendor-managed model and transcript retention.]
Organization document analyses remain tied to their source version and do not change care records automatically. Completed organization-original results remain with the organization’s records. Withdrawing AI permission stops new processing; revoking a family document share also ends organization access to that document’s dependent analyses.
For the current product controls, see Privacy & Safety.
Retention and security
Retention depends on the record’s source and applicable deletion controls. Organization originals and their earlier versions remain separate from family copies and family deletion controls. Account deletion can remove user-authored content while necessary shared care facts and limited consent or payment audit records may remain. Registration date of birth is held with the account for eligibility checks. Backend receipt-email staging expires after seven days; the separate website support inbox's raw mail expires after 30 days. Export files become unavailable after 24 hours. [Approve a category-by-category retention schedule, including date of birth, support conversation TTL, vendor periods, backups and legal holds.]
Backend deployment is configured in AWS US East (N. Virginia), but some Bedrock inference may cross regions. [Confirm all processing and storage locations, international transfers and vendor terms.] Access controls, encryption and short-lived file links protect information, but no system can guarantee absolute security.
Your choices and requests
You can contact us at support@kin-lume.io with questions or requests about your information.
Privacy & Safety provides optional data-sharing controls, account export and deletion requests, safety reporting, and family-admin review of corrections for family records other than tasks and events. Family task and event change requests are managed in Agenda → Change requests, where the record’s creator can update or decline them and family admins can view family requests. You can also request access, correction, deletion or information about sharing by contacting us. We may need to verify identity and authority, especially for another person's care data. [Add applicable regional rights, response deadlines, appeals and provider-notification procedures.]
Minors and international use
KinLume accounts are for adults age 18 or older. A minor cannot create or use an account. An authorized adult may enter care information about a minor in a care profile, including health information, when they have the authority to provide it. [Before launch, confirm how minors' care information, authority verification, and unintended submissions are handled.]
See our Consumer Health Data Notice for categories and choices concerning care information. [Confirm intended service countries and transfer safeguards.]
Changes and contact
Material changes will receive a new policy version and require an in-app acknowledgment. [Approve notification lead time and effective-date procedure.]
For privacy questions, contact KinLume at support@kin-lume.io.
See also our Terms of Use.