> For the complete documentation index, see [llms.txt](https://kyela-inbox.gitbook.io/kyela-inbox-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kyela-inbox.gitbook.io/kyela-inbox-docs/privacy.md). # Your account and privacy **Your Telegram login code, password and saved session stay on your device.** The connection page signs in directly with Telegram. Kyela does not receive those credentials. No bot joins your groups, and other Kyela customers cannot browse your inbox or change your settings. ## Why you sign in Creating or opening a bot does not give it access to the private groups in your Telegram account. The connection page needs your approval to read the groups you select. Signing in creates a Telegram connection on your device. The saved session lets that device continue without asking for a new code every time. It is not transferred to another customer's device or stored by Kyela. ## What Kyela receives To prepare and deliver your feed, Kyela receives selected address records: addresses, caller and group labels, timestamps, source links and related flags. It also stores your inbox settings and associates them with your Telegram account. Full conversations are not stored as an archive. Images and voice notes are not downloaded for recognition. Protected groups are excluded. “Credentials stay on your device” does not mean no data leaves it: your selected feed records must reach Kyela for delivery. ## Why Telegram sends a new-login alert Telegram sends this when you approve a new connection. Check that its time and device match the sign-in you just performed. Telegram may display the application's registered name, which can differ from the name shown in the bot. The approximate location comes from the connection's IP address. The alert is private to your Telegram account; it does not show your location to other Kyela users. If you did not make the sign-in, end that session in Telegram's device settings. ## How to end access Open **Your connection → Disconnect this device** on the connection page. You can also revoke the connection directly in **Telegram → Settings → Devices**; the menu can be called **Active sessions** on some versions. Keep your device protected. Device-local storage is not a promise of zero risk, and a Telegram session remains sensitive. Clearing app data or changing devices may require signing in again. ## History and support Your history setting controls retained feed records. Messages already delivered in Telegram, and copies made by recipients, may remain. Telegram does not reliably report every deletion, so perfect recall cannot be promised. Support diagnostics hide group names, caller names and source links. Exact addresses in support samples are hidden by default. You can permit them for a short support session. [How support access works](/kyela-inbox-docs/help.md#ask-for-help-with-an-address). ## Recovery copies Private recovery backups protect saved inbox settings and feed records if the service fails. Application backups retain the last 14 successful daily snapshots; provider backups may also retain those copies. An older record may remain in a recovery copy after it disappears from your live history. Your device-held Telegram session is never included. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kyela-inbox.gitbook.io/kyela-inbox-docs/privacy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.