Why you can trust it
Every architectural decision was driven by one question: how do we keep your Telegram safe and your data private?
Your data stays on your VPS.
Each customer runs on their own VPS. Telegram session, messages, AI keys — all on your server. We can't read them.
Backups are zero-knowledge encrypted with a passphrase only you hold. We hold ciphertext only.
Your VPS
Telegram TOS — the honest answer
"Scraping prohibited"
The carve-out allows "ordinary use as a user." You ARE the user. Channels blocked, groups capped at 100. Not a scraper.
"Actions without consent"
Every send originates from your click. AI proposes, you dispose.
Group cap is hardcoded
Managed beta: ≤50 members. Channels always blocked. Cannot be raised via config.
Full analysis: docs/TOSSAFETY.md
What we refuse to do
No central database of customer data.
No AI proxy. Your VPS calls the vendor directly.
No group-size bypass. 100-member cap in source code.
No shared api_id. Each customer registers their own.