GDPR Compliant
Aligned with the principles of the General Data Protection Regulation
Security
Your Telegram, safeguarded.
When you log in to Entergram with your Telegram account, we store your Telegram session — encrypted — so the platform can act on your behalf reliably. We're upfront about that responsibility and we treat it seriously: every session is encrypted at rest with AES-256-GCM, every Telegram account you connect runs through its own dedicated proxy IP, and the whole platform is aligned with GDPR.
AES-256-GCM Encrypted Keys
Session keys are encrypted at rest with authenticated encryption
Dedicated Proxy Per Account
Every Telegram account gets its own unique IP — no shared fingerprints
Data Protection
GDPR Compliance
We are fully committed to the principles of the General Data Protection Regulation (GDPR). This means we process personal data lawfully, transparently, and with appropriate safeguards — including minimizing data collection, respecting your rights (access, rectification, erasure, etc.), and implementing technical measures to protect your information.
Our practices align with GDPR requirements for data security, accountability, and user control. For full details on how we handle your personal data, please see our Privacy Policy.
Data Storage
How We Protect Your Telegram Accounts
Two design choices do most of the work: how we hold your session keys, and how every account you connect reaches Telegram.
The two pillars
1. Encrypted custody of your Telegram session
When you connect a Telegram account to Entergram, we store your Telegram session so the platform can act on your behalf — sending messages, syncing chats, running automations and so on. We're upfront about that: a CRM connected to Telegram needs to hold a session to function. What we don't do is hold it in the clear. Every session is encrypted at rest with AES-256-GCM, an authenticated encryption standard that protects both confidentiality and integrity, and access to decrypt is tightly scoped, audited, and limited to the systems that strictly need it.
2. Dedicated proxy per Telegram account
Every Telegram account you connect is routed through its own dedicated proxy IP. Accounts don't share network fingerprints with each other or with other Entergram users. This protects against IP-based correlation, reduces the risk of Telegram flagging legitimate activity, and ensures each account behaves as if it were running from a single, consistent location.
Encryption at Rest
Sessions are never stored in plaintext. Each one is sealed with AES-256-GCM before it touches our database, and decryption happens only inside the systems that need to use it, only for as long as it's needed. The encryption keys themselves are managed separately from the encrypted data, so a database snapshot on its own doesn't expose anything usable.
If You Lose Access
If you lose access to your Entergram account, you can re-authenticate through the standard account recovery flow — and if a Telegram account ever needs to be re-linked (for example, after a Telegram-side change), simply disconnect it and reconnect. There's no extra passphrase to remember and nothing to recover from us.
What We Hold, and What We Don't
Being upfront matters more than marketing here. Yes — we store your Telegram session, because the product needs it to act on your behalf. We don't pretend otherwise. What we do is store as little as possible, encrypt what we store, and avoid warehousing the rest: chat history, message bodies and other Telegram data are not retained beyond what the live product surface requires.
Practically, that means:
- —
Sessions are encrypted at rest
AES-256-GCM with authenticated integrity checks. A tampered or partially-leaked encrypted blob is rejected, not silently accepted.
- —
Encryption keys are managed separately
The keys used to encrypt your session are isolated from the database that stores it, so neither half is useful without the other.
- —
Least-privilege access
Only the production systems that genuinely need to use a session can decrypt one, and every access path is auditable.
Dedicated Proxy Infrastructure
Each Telegram account you connect is bound to its own dedicated proxy IP for the lifetime of that connection. This means Account A and Account B — even within the same workspace — never appear to Telegram from the same egress point. Proxy IPs are dedicated (not shared with other Entergram customers), monitored for health, and rotated only when operationally necessary. The result: more stable Telegram sessions, fewer false-positive flags, and a clean separation between accounts at the network layer.
Additional Security Measures
Alongside the architecture above, we apply standard hardening across the platform:
- HTTPS everywhere (TLS encryption in transit for all connections)
- Strict access controls and least-privilege principles
- Continuous monitoring for suspicious activity
- Secure development practices to prevent common vulnerabilities
Get in Touch
Your Security is Our Priority
We continuously evolve these protections to keep pace with emerging threats while keeping the experience fast and frictionless.
If you have questions about our security practices or want to exercise any data rights, feel free to contact us at hello@entergram.com
