Security
A brief security overview of the Interchat service.
Hosting and Infrastructure
- Hosting provider: Heroku (running on AWS us-east-1, Northern Virginia, USA)
- Infrastructure isolation: Separate production and sandbox environments
- Network security: External connections use HTTPS/TLS, with network controls provided by Heroku/AWS
System Architecture
Interchat runs on Heroku Dynos. Messages are processed to relay conversations between Telegram and Intercom; Interchat does not persist chat message bodies as application records. Stored access tokens are encrypted at rest.
Data Security
- In transit: TLS 1.2/1.3 for all connections
- At rest: AES-256 encryption for Telegram Bot tokens, Telegram Account sessions, and Intercom user tokens
- Data minimization: Interchat retains credentials, account configuration, and operational logs needed to run the service. It does not store chat message history as application data.
- Token lifecycle: Intercom tokens are revoked on uninstall where supported; stored Telegram credentials are removed during data deletion
Access Management
- Role-based access to production systems
- Production access is limited to authorized staff who need it to operate and support the service
- MFA/2FA enforced on all admin accounts
Monitoring and Logging
- Application and infrastructure logs collected
- Alerts configured for unusual activity
- Logs restricted to authorized staff only
Incident Response
- Process: Detection -> Containment -> Remediation -> Notification
- Notification: Customers informed promptly if required by law
- Review: Post-incident analysis conducted to prevent recurrence
Operational Security
- Regular dependency updates and security patching
- Secure coding practices
- Backups handled by Heroku/AWS with standard recovery options
Security Roadmap
- Planning external penetration testing
- Evaluating certifications (e.g., ISO 27001, SOC 2)
Contact
For any security or privacy questions, please contact support@interchat.io.