How we protect your data

Entergram holds the keys to your Telegram accounts. We take that seriously, and this page says exactly what we do rather than gesturing at “bank-grade security”.

1. Your Telegram session lives on our servers, encrypted

When you connect a Telegram account, you sign in with Telegram’s own login (QR code or a code sent to your Telegram app). The resulting session is held in Entergram’s backend - not in your browser and not on your device. There is no passphrase to manage and nothing to unlock; closing the tab or switching computers changes nothing about the connection.

Credentials stored by the app are encrypted at rest:

Cipher: AES-256-GCM (authenticated encryption - tampering is detectable, not just unreadable).
Key derivation: PBKDF2-HMAC-SHA256 at 600,000 iterations, the OWASP-recommended minimum, chosen to make offline brute-forcing of a stolen ciphertext impractical.

2. You can end the session from Telegram at any time

A connected account is an ordinary Telegram login session. Open Telegram → Settings → Devices and terminate it whenever you want, Entergram then shows the account as Reconnect Required and stops syncing until you sign it in again.

Your CRM data (custom fields, tickets, comments, notes) is never lost by disconnecting or reconnecting, only the live Telegram connection is affected.

3. Accounts connect through managed proxy infrastructure

Connected accounts reach Telegram through Entergram-operated proxies with stable per-account assignment, so an account’s traffic comes from a consistent place instead of whatever server happens to be free. Proxy credentials are stored encrypted, and none of this needs (or allows) configuration by you.

Full details: Proxies & IP isolation.

4. No message history in our database

Entergram fetches messages live from Telegram to show them to the workspace members allowed to see that chat, and keeps only short-lived caches that expire on their own. What it stores is chat metadata (chat ID, username, names, chat type, member counts) plus the data you add yourself: notes, custom fields, tickets and comments. Message text is also processed to deliver notifications.

Full details: What Entergram accesses.

5. Workspace data is isolated

Each workspace’s data is scoped to that workspace. Beyond that, messages are scoped to the account and CRM data is scoped to the chat, a teammate cannot read the messages of an account they have not signed into themselves.

Full details: What teammates can see.

When login-session management is enabled, Login sessions in Settings directly lists the browsers and apps currently signed in to your Entergram account. Signed-out sessions do not appear in this personal list. When inactivity sign-out is enabled, expired devices are also excluded from this list and from device counts, even if their browser is closed. They remain marked as ended in the owner/admin history. Each entry shows the device, available IP and location, when it signed in, and when it was last seen. Separate browsers on one computer appear as separate sessions. Tabs using the same login appear as one session.

Choose Sign out on a session and confirm to end that login. Ending the current login returns you to the sign-in screen. Other logins stay active. Ending an Entergram login does not disconnect its Telegram accounts.

A delayed status response for a previous login cannot sign out a replacement login. Temporary verification failures are retried without treating them as a sign-out.

Active login sessions shown directly in Settings

Owners and admins see a Devices summary in Seats & Members. Clicking a member’s summary opens their login history, including active and signed-out sessions. Team members cannot see this column or access member session history. Owners and admins can also end a current member’s selected Entergram login session. That login ends across all its workspaces. The seat’s Telegram accounts stay connected.

Sessions are recorded when a signed-in browser or app first contacts Entergram after this feature is released. Older devices that have not returned yet are not listed. An unknown location means Entergram did not receive trusted location information. Generic device labels use your interface language. Temporary session-verification outages do not sign you out; Entergram retries the check. When you sign out, Entergram confirms that the selected login has ended before clearing valid credentials. If the authentication service confirms that a login is no longer valid, Entergram can clear it locally so you can sign in again. Temporary authentication failures do not clear your login. A delayed response for an old login cannot clear a newer login or refreshed credentials. If sign-out confirmation is temporarily unavailable, retry once the connection is restored.

When inactivity sign-out is enabled, Entergram ends that login session after two hours without interaction and asks you to sign in again. Activity in another Entergram tab using the same login keeps it active. Background message updates and automatic refreshes do not count as activity. Your other devices have their own inactivity timers, and your connected Telegram accounts stay connected. Temporary login-check failures are retried without extending the inactivity deadline. A delayed response for old credentials does not sign out a refreshed login. If credentials refresh during the final login check, Entergram retries automatically and restores the page once the login is confirmed. On mobile, notification safety checks still run before signing out, even after the inactivity deadline. These checks do not restore access to workspace data.

Credentials and secrets

Secret	How it’s handled
Sign-in	No passwords at all, one-time email codes or Google
Telegram 2FA password	Used only to complete the Telegram login
Public API keys	Only a hash is stored. The plaintext key is shown once at creation
OAuth client secrets	Only a hash is stored - “After closing this dialog, you will only be able to rotate it, not reveal it again”
Proxy credentials	Stored encrypted
Payments	Handled entirely by Stripe. Entergram never stores card details

Every one of these follows the same rule: show once, store a hash, offer rotation.

Access controls you own

Control	Where
Hide Telegram login codes from members	Privacy settings
Stop members editing or deleting messages	Privacy settings
Restrict analytics to a member’s own data	Privacy settings
Lock excluded-chat management to the owner	Privacy settings
Restrict exports to owners and admins	Privacy settings
Keep a chat out of your CRM view entirely	Excluded chats
Scope an API key to specific permissions, an expiry date and an IP allowlist	Public API keys
Revoke an AI agent’s access instantly	Personal agents

Your data stays yours

Export everything as a ZIP or per-category files at any time.
Delete everything, type delete account and it’s permanently removed from our systems.
Delete the workspace and its tickets, logs, fields, comments, files, connectors, keys, views and templates go with it.

See Data export & deletion.

What we ask of you

Security is a shared job. The three things that actually matter:

Protect your email account with 2FA. Entergram sign-in is a one-time email code, so your inbox is the front door.
Give API keys and MCP clients the minimum scopes and a short expiry. Rotate on a schedule.
Set your workspace privacy toggles before inviting people, not after.

Ten-minute version: Privacy checklist.