Local AI
A compatible model can work beside your local files and tools. Install its runtime and model first.
Understand the connection
Local inference, hosted AI, and phone transport have different data paths.
A compatible model can work beside your local files and tools. Install its runtime and model first.
Choose a supported provider for the task. Requests and relevant context are processed under that provider’s terms.
Messages and attachments travel through your configured relay or Telegram. Local inference does not make phone transport offline.
This policy covers Telethryve and the Telethryve iOS app. Telethryve lets a phone, a Telethryve relay, and a computer bridge exchange messages, media, and live-stream events that the user chooses to send.
Data is used to deliver chat messages, route bridge traffic, store and retrieve media, support user reports, prevent abuse, troubleshoot service issues, and keep the service secure. Telethryve does not use this data for third-party advertising or cross-app tracking.
Telethryve may run on customer-controlled infrastructure or on hosted infrastructure selected by the operator. The hosted relay may use Cloudflare Workers and R2 for message routing and media storage. Billing flows may use Stripe. Optional legacy or customer-configured providers may have their own terms and privacy practices.
The computer iOS app includes Delete Telethryve Data in Settings. This asks the configured relay to delete the active token, sessions, messages, reports, updates, stream events, and stored media associated with that token. Local app session credentials are also removed when the user resets or deletes the active Telethryve data.
Telethryve tokens should be treated like credentials. Users and operators are responsible for protecting relay URLs, tokens, admin secrets, bridge credentials, and the host computer that performs the work.
Support and reporting paths are listed at telethryve.com/support.
Our website records page and button events to understand the purchase flow. Events use page paths and action names; these events do not include query strings, project content, or purchase tokens. The payment service records purchase and download events as part of providing the service.