KBT Chat privacy notice
Effective 27 October 2026 · version 2026-10-27-v1
KBT operates this invitation-only experimental beta. Your messages are sent through Cloudflare Pages and an HTTPS tunnel to KBT's local inference service. Our own native checkpoint generates responses. No external language-model provider receives your prompts.
Storage consent is optional and off by default. Without it, message content and output are used transiently for inference and are not written to the conversation database. Without saved turns, persistent history and feedback submission are unavailable. Invitation hashes, account identifiers and creation times are retained for access control. Sessions expire after eight hours and are kept in server memory.
If you opt in to storage before sending, we save your message, model response, conversation ID, checkpoint and tokenizer hashes, consent version, timestamps, ratings and submitted corrections in a separate local database. Storage alone does not permit training use. History uses only your saved turns; unsaved turns do not carry forward as context.
Training review has a separate opt-in. Only explicitly consented, human-reviewed corrections with administrator rights confirmation can be exported as candidates. Raw model outputs are not exported as training targets. Exports still need independent privacy, rights, validation-overlap, replay and release approval. No automatic training occurs.
Use Privacy & data → Delete all my saved conversations to delete your saved turns, ratings and corrections and revoke their pending export eligibility. Turning an option off applies to future turns; delete previous records to withdraw earlier consent. Deletion also removes administrator access to those records. Copies already downloaded for review require the KBT administrator to remove them from review storage before any training release; contact the person who invited you. Administrators must track export distribution and honor deletions. No automatic database backups are configured.
Cloudflare and the tunnel provider process network metadata under their own policies. Do not submit passwords, private project documents, sensitive personal data, or material you cannot share. The local gateway disables request-body and URL logging. HTTPS protects public transit; the local database is not application-encrypted and relies on Windows disk and account protection.
Beta records are retained until you delete them or the beta closes. Before release, KBT must set an operational retention schedule and verify its privacy/contact details. The administrator who invited you handles access, privacy requests and downloaded export deletion.