Telegram
One SwiftTool plan across Telegram and the web
How verified Telegram linking keeps account access and subscription state consistent.

The bot remains the subscription source
Existing SwiftTool subscriptions are stored by the Telegram bot. The web application reads a normalized snapshot through a local compatibility bridge and does not guess a paid plan from profile data.
If no VIP record exists, the record is expired or verification fails, the web account remains on the Free plan. This prevents a first Telegram login from being upgraded accidentally.
Linking requires proof
A numeric Telegram ID alone is not proof of ownership. Mini App data and Telegram Login payloads are verified cryptographically before an identity is linked.
A shared account, separate interfaces
Telegram remains convenient for message-driven jobs while the web app provides project history, settings, privacy controls and a larger workspace. Both surfaces use the same verified subscription context.