Your data
Conflu is a pipe, not a warehouse. Your mail and files travel from your provider, through Conflu, to the AI client you chose — and nothing of them stays behind. This page says precisely what that means, with an example.
What we never store
- — Email bodies, subjects, senders, recipients and attachments
- — Calendar event titles, descriptions and attendees
- — Contacts, tasks, files and filenames
- — The arguments your AI client sends — search terms, folder names, date ranges
Content is held in memory only while a request is being answered, then it is gone. We do not cache it, index it, or log it.
Nobody can read your tokens
The only credentials Conflu holds are the OAuth tokens you grant when you connect an account. They are encrypted in Google Cloud Secret Manager, one secret per account, never in our database. Only the MCP server can decrypt one, and only while answering a request that carries your own API key.
No employee of RT Consulting FZE — including its founder — can read those tokens, sign in as you, browse your mailboxes, or pass your access to a third party. There is no support tool that impersonates a customer, because this design leaves no way to build one. Disconnecting an account deletes its secret immediately.
What we store, and for how long
- Account metadata · kept until you disconnect the account
- The email address of each connected account, its provider, its status and when you connected it. This is what your dashboard shows you.
- Request metadata · kept 30 days
- For each call: which tool ran, which account it used, how long it took, how many bytes came back, and the error code if it failed. Never the content, never the parameters.
- Usage counters · kept 400 days
- Requests and data volume per day and per connector. This is what enforces your plan quota and draws your charts.
- Your MCP API key · kept until you rotate or delete it
- The key your AI client sends with every call. Encrypted in Secret Manager so your dashboard can show it to you again; verification uses a separate bcrypt hash. Rotating it revokes the previous key immediately.
- Billing records · kept as long as accounting law requires
- Your Stripe subscription and invoices.
An example
You ask your AI client for your last five emails. It calls Conflu, which decrypts the token for that mailbox, asks Microsoft Graph, streams the five emails straight back to the client, and forgets them.
What is left in Conflu afterwards is one line: tool=microsoft_list_emails · account=you@example.com · 812 ms · 48 KB · ok — no sender, no subject, no body. It is deleted automatically after 30 days.
Where this runs
Conflu runs on Google Cloud with processing in the European Union. Traffic is encrypted in transit and at rest. For the security architecture, see Security; for the legal text, see our Privacy Policy.