Privacy and data
The Teleflows MCP server reads your Teleflows data when your assistant asks for it and passes it on. It keeps as little as possible.
What is stored
Section titled “What is stored”Only what sign-in needs:
- Your API key, encrypted. Each key is encrypted with its own data key, and that data key is itself encrypted with the server’s master key.
- Sign-in codes and tokens, only as hashes. The same goes for sign-ins in progress. A stored hash cannot be turned back into a code or token.
No Teleflows data is stored: no calls, no names and no responses.
How long it is kept
Section titled “How long it is kept”- Expired sign-in data is removed automatically.
- When a connection is revoked, its stored key is wiped at once. When a connection expires, its key is wiped at the next cleanup.
- The rest of an ended connection’s record is deleted 30 days later.
- The sign-in database is backed up nightly, and the newest 14 backups are kept. They hold only encrypted keys and hashed tokens.
What is logged
Section titled “What is logged”One line per request: the method, the path, the status, how long it took, whether a sign-in token was sent, and the app’s user agent.
The log never contains query strings, keys, tokens or request and response bodies.
Where answers are produced
Section titled “Where answers are produced”Answers are produced by your AI assistant. The data a tool returns is sent to that assistant’s provider, for example Anthropic or OpenAI, and handled under their terms.
To stop access, see Revoke access.