Privacy Policy
Version: September 19, 2026
Operator: Kith.
What this covers
This notice describes Kith's website-to-Messages onboarding and private-chat capture. Accepting at signup gives permission to save new messages in your private chat with Kith. It does not grant access to past messages, contacts or other conversations. Group capture requires each participant's separate agreement.
Information Kith handles
Signup and connection. Kith processes your invite code, phone number, acceptance and connection request. Pending enrollment stores hashes of the phone number and connection token, along with the consent version, acceptance time, expiry and request identifiers. A hash is a comparison value; it is not a claim that the information is anonymous.
Verified chat. Once you send the prepared message from the matching number, Kith records the verified number, chat and participant identifiers, permission and connection state. While permission is active, Kith saves new messages from you and Kith, edits, reactions, attachment references and related delivery data received from its messaging provider. Attachment references can include names, types and links; this version does not promise a complete archive of attachment files.
Account and profile. Kith creates an account in Amazon Cognito using your verified phone number and links it to your profile and chat connection. Your name and timezone remain unset until you provide them. Kith can share its own contact card in iMessage and records whether that request was accepted, failed or had an unknown outcome. Sharing Kith's card does not give Kith access to your address book.
Operational records. Kith retains identifiers, timestamps, consent and control receipts, delivery outcomes and error/status metadata to operate the connection, handle retries and honor pause or deletion. Before activation, incoming messages can be processed to handle onboarding and controls, but ordinary message bodies are not saved to Kith's capture database. Verified incoming webhooks first enter an encrypted delivery buffer so outages can be recovered. The buffer is deleted after processing; unresolved deliveries remain for operational recovery and are not permission to archive or send content to a model.
Why and where information is processed
Kith uses this information to verify your number, enforce your permission, receive and document allowed messages, send service replies and maintain the service. For replies in your private chat, Kith sends your message and limited recent context from that same chat to OpenRouter and Google. Kith can save a name you provide to your profile. We do not use your messages for model training or research, and we do not use other people’s private chats to answer you.
Amazon Web Services hosts Kith's application and database in the US East (Northern Virginia) region. Linq carries messages between Kith and your messaging service. OpenRouter routes private-chat reply requests to Google; Kith selects a provider endpoint eligible for zero data retention and disables model-provider fallbacks. This routing does not mean every provider processes information only in the AWS region. These providers process information needed for their roles; your carrier or messaging platform also handles your messages under its own terms. Kith's deletion control does not delete their copies. See Linq's privacy policy for its practices.
Browser storage
The website uses a signed, secure invitation cookie that lasts 30 minutes. It keeps your invite check available while you connect. The prepared connection token expires after 15 minutes and can be claimed only by the matching phone number. Token expiry ends its ability to connect; it does not delete the consent or request record.
Retention and deletion
Captured content. Saving permission lasts one year unless paused or deleted sooner. Expiry or Kith pause stops new capture and conversational replies but leaves saved records in place. Saved content remains until you send Kith delete.
What deletion changes. Kith delete removes the chat's raw message content, captured documents and stored model conversation content from its active database and closes that connection. Kith keeps limited operational records, including identifiers, hashes, consent history, delivery receipts and a record that the source was deleted. These records prevent stale requests from restoring the connection and do not yet have an automatic deletion schedule.
Account removal. Deleting a chat does not automatically remove your profile or Cognito account. Contact the privacy email below to request account removal. Account deletion redacts the local profile and its stored verified phone number; removal from Cognito is a separate cleanup step and is not yet automatic.
Backups and logs. Automated database backups have a seven-day retention window. Separate manual or final database snapshots can remain longer until removed. Application logs have configured retention of seven days for message processing and 30 days for the production public website service. Deleting a chat does not immediately erase existing backups or logs, and it does not erase messages on your device or with Linq, your carrier or other messaging providers.
Your choices and questions
You can decline signup, send Kith status to check the connection, Kith pause to stop saving, or Kith delete to delete captured content as described above. A new website consent can reconnect a paused chat. A deleted connection stays closed. Carrier opt-out commands such as STOP also stop capture and suppress Kith's replies.
For privacy questions or requests the chat controls do not cover, contact udit@verma.fyi.
This notice has a version date so changes can be identified. A later notice does not itself expand the permission you already gave. Read the Terms of Use for the service's current scope and use conditions.