Consent and clear boundaries
Kin coordinates everyday care. It cannot establish whether somebody is safe, assess their health, advise on medication or handle an emergency. If you need to know how someone is doing, contact them directly. Do not wait for Kin to answer a safety concern.
A record is not an inference
Kin shares what the family reports. A completed check-in records a response; it is not independent proof that the activity happened. A missing reply, skipped check-in, empty day or acknowledged follow-up does not establish safety.
Names identify the account used, not a verified physical speaker. Keep account credentials private and consider who can use a shared phone, browser session or linked Echo.
Choose what to share
The hosted workspace requires sign-in and active circle membership. Roles limit which operations an account may perform. Accepted membership is separate from appearing on the care roster.
Only record the everyday information the circle needs. Do not use the local story for real family information; it uses synthetic identities rather than production authentication. Do not put passwords, invitation codes, tokens or private care history in a screenshot, public issue or shared demo.
This guide describes product boundaries. It does not promise that the hosted service is available for unrestricted public use or replace a formal data retention or privacy agreement.
Voice input and models are separate choices
Browser dictation starts only when requested. The browser may send audio to its speech-service provider; recognized text becomes a draft you can edit. It does not identify who spoke or silently save a care reply.
Optional model-assisted interpretation is a separate operation. In the local story, Nova mode requires explicit launch configuration and per-request consent. It can propose a reviewed response, not save it. AWS model charges may apply. The default local story makes no model calls.
Weekly summaries are tied to recorded source facts. Model errors or rejected selections fall back to a deterministic brief. Neither mode provides medical advice.
Notifications are best-effort
Phone enrollment, device permission, caregiver assignment, automatic processing and verified delivery are different states. Enabling one does not prove all the others are ready. Installing Kin on a phone does not turn notifications on.
Lock-screen follow-ups contain no check-in details. Provider acceptance is not proof of physical receipt, and acknowledgment records seen—not completed or contacted. Delivery can be delayed, fail or have an uncertain outcome.
General recurring missed-check-in processing is currently off in the hosted deployment. Check the plan directly rather than relying on an alert. A past bounded test or the local story does not promise continuous notification service.
Reminders can be heard nearby
An Alexa reminder needs separate consent. Kin requests cancellation when applicable; a cancellation request is not proof Alexa has removed it. Check the Alexa app before creating another reminder if the result is uncertain.