Privacy
DirectFlow stores the Telegram identity needed to deliver updates and associate your choices with you.
After you connect Slack, DirectFlow stores your app conversation destination on the server and places an authenticated, HTTP-only reference in your browser. The reference contains no Slack credentials or Slack IDs and lets that browser reuse the destination for later follows. Choosing “Change Slack destination” clears only that browser reference; it does not remove existing follows. URLs sent to the app in Slack are stored as subscriptions or pending follow requests and Slack event IDs are retained to prevent duplicate processing.
We store addresses and domains you ask to follow. When no channel is found yet, the saved request is checked periodically. Channels discovered later may be proposed to you through Telegram.
We store subscriptions, discovered channel candidates, known source items, and notification-delivery state so updates can be delivered reliably without duplicates.
You can manage followed sources in Telegram with /following. To request deletion of other stored data, contact the operator of this DirectFlow instance using the contact information provided with the deployment.