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.
Duplicate protection
The bot stores media identifiers after delivery so the same story or post is not sent repeatedly.
Public Instagram flow
The current guide assumes public Instagram profiles. Private profiles are not supported in the public-fetch flow.
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. Payment processing is not connected to this website. Future billing should be handled by a payment provider and verified by backend webhooks.
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.
Can users remove their setup?
Yes. The bot interface includes destination and target management actions.