Privacy & Security

Privacy and Security Overview

Amua is designed so that Telegram remains the system of record for communications. Amua adds an organizational layer for teams — the workspace, member management, chat management, subgroups, and related operations — without making Amua's backend a repository for Telegram content.

Security principle#

Amua is built to be as data-minimal as possible.

Telegram chat data stays with Telegram and on the user's device. Amua does not proxy Telegram messages through its backend, and it does not store message content, media, or chat history on its backend.

Amua stores only the workspace metadata required to provide workspace features.


What Amua stores#

Amua stores workspace metadata and limited account information required to operate the product. Depending on the features in use, this can include:

  • Amua account identifiers and Telegram user identifiers
  • Telegram username where needed for identity resolution or display
  • Workspace names and workspace branding settings
  • User-to-workspace and chat-to-workspace associations
  • Workspace role classification data needed for permissioning
  • User-generated metadata in connection with imported contacts
  • Subgroup structure
  • Subscription and billing records required to manage the service
  • Session, reliability, security, and abuse-prevention records
  • Basic billing details (e.g. only last 4 digits of card)

What Amua does not store#

  • Telegram message content or chat history
  • Telegram media and files
  • Your Telegram contact list
  • Telegram password
  • A user's Telegram session data
  • Full billing details

Protection of Amua data#

Amua protects data in transit using HTTPS/TLS. Workspace metadata stored by Amua is encrypted at rest in managed cloud infrastructure.

Access to workspace metadata is controlled through authenticated requests and authorization checks. Users can access workspace data only where their workspace membership and role permit it.


Telegram account connection#

When a user connects Telegram to Amua, Telegram authentication and session data are handled locally on the user’s device through Telegram’s client infrastructure. Amua does not see your Telegram password if you've enabled 2FA on the Telegram side.

Amua uses the connected account to present Telegram data in the Amua interface and to support the workspace features the user chooses to configure.

Workspace members who do not use Amua#

A workspace owner can organize Telegram-related workspace structure (members, chats and subgroups) without requiring every person on their team or in a chat to have an Amua account.

For people who have not joined Amua, the system uses only the minimum identifier-level information needed to represent the relevant workspace relationship. This has no impact on those users' Telegrams.

Amua only references those users' user IDs. It does not need to ingest any of those individuals' Telegram profile, message, contact, or chat data.

Retention and deletion#

Amua retains account-linking and workspace metadata only as needed to operate accounts, permissions, subscriptions, security controls, and service recovery. When an account or workspace is deleted, the corresponding Amua-side metadata is deleted or retained only as necessary for limited operational, recovery, or legal purposes.