Security
Security at Antenna
The threat model is simple: a platform that posts to many channels must never be the weak link in any of them.
Operating practices6 controls
No customer-held tokensYou never create or store a bot token. Antenna operates one platform bot; its credential lives in our secret store, and no customer, contractor or channel admin is ever given it.
Verified webhooks, both directionsTelegram updates are accepted only with our secret token header; payment notifications verify an HMAC signature before anything is credited.
Least-privilege rightsThe bot asks for Post Messages and nothing more on channels. Rights are re-verified before every scheduled send and on every membership change event.
Tenant isolation by constructionEvery bot event is routed by chat identifier to exactly one customer's configuration. Cross-tenant routing is a tested, launch-blocking defect class.
Data minimisationWe store what operating your channels requires: identifiers, post content you wrote, delivery statuses, counts. Export or delete it any time from Settings.
Abuse kill-switchesTemplate behaviour that looks like flooding is auto-disabled and reported — protecting your group and everyone else sharing the bot.
Report a security issue
Found a vulnerability? Tell us through the contact form — email to support@antenna.builders cannot currently be delivered and will bounce. Please don't test against channels you don't own.
Open the contact form