Security and reliability
TickerShare turns TradingView webhook alerts into branded signal cards and delivers them to Telegram through your own bot.
Your bot and your channel
Delivery runs through a Telegram bot YOU create and own. Subscribers see your bot posting, never a third-party name. Remove the bot and the access is gone.
Encrypted bot token
Your bot token is validated with Telegram when you add it, then stored encrypted with AES-256-GCM. It is never displayed again and never appears in logs.
Private webhook URLs
Each webhook URL contains a long random token (up to 48 hex characters). Requests are rate limited (60/min default), capped at 64 KB and deduplicated within 30 seconds.
Text fallback, always lands
If a card ever fails to render, delivery automatically degrades to a clean text message. A render problem never costs you an alert.
Delivery logs
Every delivery is recorded with status, speed, mode, symbol and error. Failed deliveries show the reason and can be retried in place.
No permanent image archive
Cards are rendered, delivered and then hosted by Telegram itself. TickerShare keeps the delivery log, not an archive of your images.
Performance, honestly framed
Cards render in a fraction of a second on our image engine (typically ~60 ms, measured in our own testing). End to end delivery is usually a few seconds for cards, dominated by Telegram's photo upload, and about a second or two for text-only and forward-as-is alerts. TradingView always gets its response within milliseconds, well inside its 3 second timeout, because delivery runs asynchronously behind it. Telegram flood control (429 retry_after) is honored automatically, so bursts self-heal.
Your data and your rights
We aim to collect the minimum needed to run the service. You can delete your account and all associated data at any time from Settings. Details in the Privacy Policy and webhook security docs.