Security
What happens to your data
An agent works with tasks, documents and conversations from your business. This page explains how FlowAgents protects them. We only describe what the platform actually enforces.
Access within the team
You decide who works with FlowAgents.
-
Access per person
Access to FlowAgents is granted to each team member individually. Without it, a person sees neither agents nor boards.
-
Private board
Every person has their own board. No team member sees someone else’s board, owners and co-owners included. Other people’s cards answer as if they did not exist.
-
Support by us
Only we as the operator can look into a board from the admin area, to support you.
Servers and memory
Your agents do not share their server with other companies.
-
One server per customer
Every server is assigned to exactly one customer. Only your company’s agents run on it.
-
Memory on the server
An agent’s memory lives on its server. When you open it in the dashboard, it is read from there, and the access is logged without its content. To organise memories, the memory uses a language model.
-
Password-protected browser
You open the live view of the agent’s browser from the dashboard. It is protected by a password of its own that changes regularly.
Approvals
An approval only counts when it really comes from you.
-
Only your own message
When you answer a question in the chat, the platform checks that the message is yours and was written after the question. An earlier “yes” does not answer a later question.
-
Notices are not consent
What the platform passes to the agent as a notice in the chat never counts as an approval. Voice messages are transcribed by the platform itself, not by the agent.
-
Rules in the role sheet
What an agent may do without asking is set with you in its role sheet. The access it gets also limits what it can reach at all.
Telegram and phone
Who may talk to an agent is defined.
-
Only approved Telegram accounts
In the chat, an agent only answers the Telegram accounts registered for it.
-
Public bot with fixed limits
If an agent should be reachable for every Telegram user, for example in support, it only answers from the knowledge you release. Board, files, browser and memory are then technically blocked, and per-sender limits apply.
-
Clear rules on the phone
Callers outside your team hear at the start that a digital assistant is speaking. The agent only takes down their request and shares nothing internal. It recognises you by your stored phone numbers.
What this page does not cover
Which service providers are involved in language, phone and hosting, and how long data is kept, is set out in our privacy policy. If your company has specific requirements, we go through them in the first conversation.