Data transparency
Where your data lives, and who is allowed to see it
Every run leaves a trace naming the provider that handled each step, where it ran and what it cost. This page is the map behind that trace: where your data is stored, the providers a run can reach, how long anything is kept, and what is sealed where nobody reads it in passing.
- Stored in the EU, on one server in Germany
- On paid plans, you choose the model, agent by agent
- Documents and credentials sealed at rest
- Download your results; delete files and agents yourself
Where your data lives
One workspace setting decides which models your agents can be set to: Allowed data regions. It has exactly three values and is checked when an agent is saved — a model outside your policy cannot be chosen. It is not a filter on every run: a template's own default models are exempt, trial and demo runs use the platform's default model, and narrowing the setting later does not re-check agents already saved.
euEU only
Only EU-hosted models can be chosen for your agents. None of them is connected in production yet, so today an agent on this setting runs on its template's default models, which are hosted in the US.
eu_usEU + US
EU and US-hosted models. Most frontier models are hosted in the US today, so this is the setting that keeps the strongest ones available without opening the door any wider.
anyAny region
No residency restriction. Every provider below becomes selectable, including models routed to their maker's own cloud outside the EU and the US.
The workspace owner sets the policy; an agent can pin a stricter one of its own, which is then applied to every model call that agent's runs make. Your documents, results and traces live in our own database and file storage — one database and one data volume on a single server in Germany, rented from Hetzner, whatever this setting says — separate from every model provider: a provider sees the content of the one request it was asked to process, never your account.
Which providers a run can reach
Our templates run on Claude and Gemini by default — some plan with Claude and do the work with Gemini, others use Gemini throughout — and an agent can be set to another model instead. The model that checks each answer is one of them too: today a run's work and its check are both processed in the US. Each card carries the narrowest Allowed data regions setting that still lets you select it. The two Alibaba cards are the same open-weight model on two different hosts; the EU-hosted one, like Mistral, is in the catalogue but not yet connected in production.
Anthropic
Selectable under: EU + USClaude Opus 5 · Claude Sonnet 5 · Claude Haiku 4.5
- Hosted by
- OpenRouter
- Runs in
- United States
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
Template defaultTo be verifiedGoogle
Selectable under: EU + USGemini 2.5 Flash
- Hosted by
- OpenRouter
- Runs in
- United States
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
Template defaultTo be verifiedMistral AI
Selectable under: EU onlyMistral Large
- Hosted by
- Mistral AI (France)
- Runs in
- European Union
- Provider retention
- 30 days
- Training use
- Not used for training
To be verifiedAlibaba
Selectable under: EU onlyQwen 3
- Hosted by
- Scaleway
- Runs in
- European Union
- Provider retention
- Not retained, per the host's terms
- Training use
- Not used for training
Open weightsTo be verifiedOpenAI
Selectable under: EU + USGPT-5 mini
- Hosted by
- OpenRouter
- Runs in
- United States
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
To be verifiedxAI
Selectable under: EU + USGrok 4.1 Fast
- Hosted by
- OpenRouter
- Runs in
- United States
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
To be verifiedAlibaba
Selectable under: Any regionQwen3 235B
- Hosted by
- OpenRouter
- Runs in
- China or the United States — the aggregator can route upstream to the maker's own API
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
Open weightsTo be verifiedDeepSeek
Selectable under: Any regionDeepSeek Chat
- Hosted by
- OpenRouter
- Runs in
- China or the United States — the aggregator can route upstream to the maker's own API
- Provider retention
- Not stated
- Training use
- May be used for training on the maker's own API
Open weightsTo be verifiedZhipu AI · Moonshot AI
Selectable under: Any regionGLM 4.6 · Kimi K2
- Hosted by
- OpenRouter
- Runs in
- China or the United States — the aggregator can route upstream to the maker's own API
- Provider retention
- As the upstream host's policy states
- Training use
- As the upstream host's policy states
Open weightsTo be verified
This list is maintained by hand against the model catalogue the product ships with. Rows marked “to be verified” are seed data: the claim is re-checked against the provider's own terms before it goes anywhere near a contract. Retention and training use describe each provider's policy, not ours — we train no models, on your data or on anyone else's.
What a provider costs you is a separate question, and a run answers it twice: an estimate before it starts, then the metered truth from the trace once it finishes. See pricing for how credits become euros.
How long it is kept, and how it leaves
Your workspace has a retention setting. Your plan sets its starting value — from 30 days on the free trial to 365 on Scale — and you can change it, from 1 to 3,650 days. When those days run out, runs with their files and results, library files, calls with their recordings and transcripts, and WhatsApp messages are deleted automatically, once a day.
- Deleted automatically
- Three things. After your retention days, everything listed above goes, and the request log keeps the method, path and status of each request but no longer its IP address or browser. In no-retention mode, a run's uploaded files, the text extracted from them and its intermediate steps are destroyed as soon as it finishes; its structured result and its record stay until the retention days run out. And a run in this site's public demo is deleted 24 hours after it starts.
- Export
- Download each run's results and files from the run itself; your finance movements come out as a CSV through the API's finance export. An owner downloads the whole workspace from Settings → General as one ZIP of JSON — members, agents, runs with their results, the list of files, calls with their transcripts, WhatsApp threads, published apps' users, credits and the activity log.
- Deletion
- In the console you delete your files, agents and connections yourself, and a phone call with its recording and transcript, at the voice provider too. An owner deletes the whole workspace from Settings: it closes at once and is deleted after 14 days, and can be restored until then. Each person deletes their own account from Settings → Profile. A single run cannot be deleted on its own: it goes when the retention runs out. Credit movements and invoices are kept, as the law requires. For anything else, write to contact@agentflowbind.com.
- The trace is the receipt
- Every run records which provider handled each step, the region it ran in and what it cost — so “where did this go?” stays a question with an answer afterwards, step by step.
What is sealed, and what we cannot read back
Two kinds of data never sit in plaintext where anyone — us included — could read them in passing.
- Files and run data
- Uploaded files, the files runs produce, and run data — inputs, results, steps and logs — are encrypted at rest with AES-256-GCM, in our own storage on our server in Germany. Not everything is: the items of your price lists and the definitions of your datasets are stored unencrypted.
- Connection credentials
- The credentials for your ERP, accounting software, calendar or mailbox are sealed at rest, never sent to a model provider, and never returned by the API — not to you, not to an integration. Only the tool call that needs one gets to use it.
- API keys
- A key is random, shown to you exactly once, and stored on our side only as a SHA-256 hash beside its non-secret eight-character prefix. We cannot read yours back either: a lost key is revoked and replaced, not recovered.
Who else is involved — and what this page will not claim
Being useful about sub-processors means being exact about the line between what a web page can tell you and what belongs in a signed document.
- Model providers, through OpenRouter
- In production every model call goes through OpenRouter, which routes it to the maker or host of the model a run uses — the rows above — and so sees each request it routes. Which rows those are depends on the models your agents run on: the ones you choose and your templates' defaults. Trial and demo runs use the platform's default model, a deliberately cheap one, so trying the product does not cost what running it costs.
- Hosting: Hetzner
- One server in Germany, rented from Hetzner, runs the platform — its database and its file storage included.
- Email: Resend
- Sends the platform's emails — account and alert emails — and the emails your flows and agents send, which can carry what a run read or produced. It also delivers the messages sent through this site's contact form to our mailbox.
- Cloudflare
- Runs the DNS for our domains, and the bot check (Turnstile) when it is switched on.
- Payments: Stripe
- Processes your payments.
- Phone and WhatsApp
- Only if you use them. ElevenLabs runs the phone agent's voice, and calls reach it through the number you import — from Twilio, Exotel or a SIP trunk. WhatsApp messages go through Meta or Twilio, depending on the number you connect.
- Only if you connect Google Sheets or BigQuery as a data source.
- This site's chat
- What you type in the chat goes to the platform's default model, through OpenRouter.
- What is not on this page
- A DPA, a sub-processor annex with named entities and dates, an SLA, security certifications, a specific GDPR article applied to your case. Those are a conversation with a person and a document you can sign — a page that improvised them would be worth less than nothing.
Have a question this page does not answer?
Send it to the same inbox everything else on this site reaches, and a person answers. If it is a contract question, say so — we will bring the document instead of a paragraph.
Ask us about your data
We answer in Italian, German or English.