How Kinpath handles Circle messaging data

Scope

This policy is limited to the Kinpath Circle messages program for recipients in the United States and Canada. The program sends non-marketing Circle logistics only after the recipient chooses text messages and proves possession of the mobile number.

Information the program processes

• The mobile number, stored by Kinpath as encrypted data plus a keyed fingerprint used for consent, duplicate prevention, and suppression.
• Consent evidence, including the disclosure version, source, time, scope, and phone-possession result.
• Bounded send and delivery facts such as template version, time, state, segment count, and a limited provider failure category.
• Inbound reply classes such as STOP, START, HELP, YES, MAYBE, NO, or other. Kinpath does not keep the inbound message body.
• A facilitator-approved public display name and an expiring Kinpath invitation link where the message template requires them.

Kinpath Circle messages do not contain Circle speech, feedback, attendance history, private reasons, Guide memory, crisis content, health information, contact lists, access tokens, account identifiers, or a participant roster.

Why the information is used

Kinpath uses the information to prove recipient consent, send the Circle logistics messages, prevent duplicate or over-frequency sends, report bounded delivery state, respond to HELP, honor STOP and other reasonable revocation requests, secure the service, and account for provider cost.

Provider and carrier handling

Kinpath uses Twilio in its United States region. Twilio and downstream mobile carriers necessarily receive the destination number and message while routing SMS. SMS is not end-to-end encrypted, and selecting a United States provider region does not promise that carrier routing remains in one country.

Kinpath enables Twilio message-body redaction. Twilio's documentation says ordinary production access to unredacted message data can continue for up to 24 hours and that separate limited-access compliance storage remains for an unspecified period.

Twilio's standard toll-free STOP filter retains opted-out numbers needed to block later sends, so Kinpath cannot promise complete phone-number redaction for numbers in Twilio's opt-out list. The Help page describes how STOP is handled.

Sharing and sale

Kinpath discloses SMS data to Twilio and mobile carriers only as needed to route messages, operate STOP and HELP, provide delivery facts, protect the service, and meet binding legal requirements. Kinpath does not sell mobile information and does not use SMS consent for third-party marketing.

All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

Access and security

Kinpath encrypts phone numbers, keeps encryption and fingerprint keys separate, restricts provider-console production-data access to an owner and one operational backup using phishing-resistant multifactor authentication, and does not store message bodies in application logs. Facilitators see at most a masked last-two-digit number while an invitation is active.

Retention and deletion

Kinpath deletes encrypted phone data 30 days after no active invitation, consent, or unresolved delivery needs it. Provider, send, and inbound-event rows are deleted 30 days after content-free counts are produced. Consent evidence is kept for 24 months after expiry or revocation.

A verified deletion request removes the phone ciphertext and the account linkages. A keyed suppression fingerprint remains while an opt-out is in force, so deletion never causes a later text to someone who said STOP.

Provider and carrier retention are governed by their own systems, described under Provider and carrier handling above.

Your choices

SMS consent is optional and separate from using Kinpath. Reply STOP to opt out of all Kinpath texts to that number. Reply HELP for help.

You can ask what Kinpath holds about your number, correct it, revoke consent, or ask Kinpath to delete it. Email info@kinpath.community, or read the Help page for how each request is handled.