Consent and Privacy Rules¶
This page describes how the GiveCare SMS runtime contract treats consent and privacy. Each rule below comes from the pinned implementation contract; it is not proof of what is deployed.
Consent controls¶
Gate decisions are deterministic for exact STOP and HELP texts, which get transport-managed SMS responses.1 The STOP, START, and PAUSE controls update consent.1 Text from a paused or held caregiver, or text whose identity is uncertain, is screened by the input guardrail alone.1
Signup¶
Signup requires explicit SMS consent, and publication consent is a separate consent.1 Repeated enrollment with the same phone does not overwrite identity or reactivate stopped consent.1 Before the welcome message is delivered, delivery re-checks permission and welcome expiry.1 A single silent-signup follow-up remains bound by permission and quiet hours.1
Checks before sending¶
Every send re-checks channel state, so a caregiver who opts out while a turn runs is not texted.1 Tools are vetoed while consent is not active or a safety hold stands.1
Check-ins¶
A check-in is queued only when the caregiver asked for it, and code reads the day and time from the caregiver's message.1
Saved notes and private identifiers¶
Code-owned saved-note controls remove selected saved facts and hide thread entries carrying their words from model context.1 Private identifiers are redacted before any model and before the thread.1