Website data
This static website does not need user accounts, payment details, or Telegram login to display the guide.
Privacy overview
Clear expectations for what the bot needs.
This page explains the website and product behavior at a high level. It is intentionally generic until final terms, billing, and production hosting are decided.
Bot destinations
The bot stores selected Telegram destinations so it knows where to deliver stories and posts.
Saved targets
The bot stores chosen Snapchat or Instagram targets so scheduled runs can continue automatically.
Job and history state
The bot stores job records, timestamps, and delivery outcomes so users can review recent history and understand what ran.
Duplicate protection
The bot stores media identifiers after delivery so the same story or post is not sent repeatedly.
Subscription state
If a paid plan is activated, the bot stores subscription and payment state against the Telegram user so plan limits can be enforced correctly.
Public Instagram flow
The current guide assumes public Instagram profiles. Private profiles are not supported in the public-fetch flow.
Support relay
The separate support bot keeps support chats away from the main automation bot and routes replies through a dedicated support workflow.
User control
Users can pause, resume, and delete saved targets or destinations through the Telegram bot controls.
Safety FAQ
Plain answers for common concerns.
Does the website store payment information?
No. The public website is informational. Plan activation and payment handling happen inside the Telegram bot flow, not on this static site.
Does the website reveal the operator identity?
No. The website is branded around Story Control and links only to the public bot username.
Why does the bot store media identifiers?
Media identifiers make duplicate prevention possible. Without them, scheduled runs could resend the same story or post.
What does the bot store besides targets and destinations?
The current product also stores job history, duplicate-prevention state, support-thread routing, and subscription state when a paid plan is active.
Does the public website need a Telegram login or account?
No. The site is a static guide. Telegram identity matters inside the bot, where destinations, targets, support, and subscriptions are tied to the user who actually runs the service.
Can users remove their setup?
Yes. The bot interface includes destination and target management actions.