Legal

Privacy

How Flow handles what you share while you build a bot, and what your customers share with the bots you run on Flow.

Last updated September 2026
Customer chats
90 days, latest 200 messages a chat (by default)
Customers' files, photos, voice notes
90 days
Connection call records
30 days, never bodies or headers
Saved data and scheduled messages
Until you delete them

Your answers when you start

What you type into the chat on this site is used to write your bot's first draft, to keep your answers until you sign in, and, when you leave your contact details, to get back to you about it. That means the answers you give, any files you add, the contact details you share, and the transcript itself.

What we don't do with it

We don't sell it, we don't rent it to advertisers, and we don't train public models on it. If you'd rather we deleted it, email samyak@flow.engineer and we will.

Bots you build

Conversations, contacts and orders in a bot you build with Flow are yours, not ours. Flow processes them on your behalf so the bot can do its job, and keeps a log of the actions it takes so you can check them.

Connected apps

When you connect your own app or API to a bot you build on Flow, we store its address, the key or password you give us, and the choices you make for it (for example whether the bot may change things there). The key is encrypted before it is stored, with a data key that is itself kept in a separate key management service. Once it is saved, we never show it again (only the last four characters of a longer key), and disconnecting the app deletes it.

Your bot never holds the key: it is not in the bot's files, its code repository or what its language model sees. The bot's calls to your app go through Flow, which adds the key on the way out, sends them only to the address you connected, and takes the key out of any answer before the bot reads it. Calls that would change something in your app are blocked unless you allow them.

When an app signs you in instead of taking a key, we store the sign-in it gives us (the tokens that let your bot's calls act with the permissions you granted there) and, if you gave us one, your app's client secret, encrypted in the same way and never shown. We renew the sign-in as the app allows. Disconnecting signs Flow out at the app where the app supports that, and deletes the sign-in.

We record each call so you can check what your bot did: which connection, the method, the path, the result, how long it took and its size. We never record what was sent or received, the headers or the query string. These records are deleted after 30 days.

Your customers' chats, files and data

When your customers write to your bot on Telegram or WhatsApp, we keep their messages and the bot's replies (a voice note as its words) so the bot remembers the conversation. By default, chats are deleted after 90 days and we keep at most the latest 200 messages of each chat; if your business needs different limits, ask us and we can change them. The message as Telegram or WhatsApp delivered it to us is kept for 3 days after it reaches the bot, or 14 days if it could not be delivered.

Files, photos and voice notes your customers send are kept, as they were sent, in private storage for 90 days, so you can open them; then they are deleted. What your bot saves while it works (orders, bookings and the like) and the messages it schedules are kept until you delete them.

You can delete everything your bot keeps about one customer at once: what it saved, their scheduled messages, their chat and their files.

Who else handles it

Flow uses a small number of service providers to run: cloud hosting and storage (in the United States), sign-in, the AI models that write your bot's replies, speech-to-text for voice notes, and code storage for your bot's instructions. Each receives only what it needs for its part, under contract. The messaging apps you connect carry messages between your customers and your bot, and an app you connect receives what your bot sends it. Ask us for the current list of providers.

Analytics on this site

We measure how far people get in the chat on this site so we can shorten it. That's aggregate counts, not profiles built across the web.

Inside the app (not on these pages), we may use an error-reporting service to see when something breaks: the page, the error and what was clicked, tied to your account number. It never receives what you or your customers type, chat text, files or keys.

Questions

Questions, corrections or deletion requests: samyak@flow.engineer.

This page describes how we work. It is not legal advice, and it is not a substitute for a data processing agreement — ask us for one and we'll send it.