We work with sensitive data — Telegram authorization sessions. That's why security for us is not a marketing section but part of the architecture. Below is exactly what we do.
Encryption
- All traffic between you and Neurogram is transmitted over HTTPS (TLS).
- Telegram sessions and 2FA passwords are encrypted at rest, and the encryption key is stored separately from the database — a database dump alone does not reveal the sessions.
- Sessions are tied to your account and are not accessible to other users of the Service.
Payments
We do not store or process bank card data. All payments go through third-party payment services — card data never reaches our servers.
Storage and access
- Servers are hosted in secure data centers.
- Access to production infrastructure is limited to a strictly narrow circle of people.
- Database backups are created automatically and regularly.
Authentication
- User passwords are stored only as hashes — the original password cannot be recovered from the database.
- Two-factor authentication via an email code is supported.
Monitoring
Infrastructure and errors are monitored; the team sees anomalies and failures and handles them as a priority.
Recommendations for users
Any cloud service working with Telegram sessions becomes a trusted party. We recommend:
- use separate working accounts for automation, not your personal Telegram;
- enable 2FA and keep passwords in a password manager;
- remove accounts you no longer use from the Service.
Report a vulnerability
Found a vulnerability? Write to us directly — support@neurogram.one or Telegram @neurogram_support. We handle such reports as a priority and do not pursue good-faith researchers.