As of 4 October 2026 · checked against the source code
How Biwak is built, at a glance: which service does what, and what goes where.
Tap a tile or an arrow: who runs it, what flows, what stays, the contracts. Simplified to one service per task; all recipients with their addresses are listed in section 9 of the privacy policy.
The agent reads, writes and makes checkpoints in your project folder.
biwak.ai, your account and the workspace in the browser.
Dictation in the workspace uses your browser's speech recognition. Chrome sends the audio to Google for this.
Cookies and statisticsSupabase Pte. Ltd · based in Singapore
A relay checks account and quota and passes the task on to the language model. The database holds account, plan, usage and the conversations from the browser.
In the admin area, Biwak only opens stored content when there is a reason; every access stays in the log for one year. Error reports also arrive in full by email at kontakt@biwak.ai.
Vercel Inc. · based in the USA
Serves biwak.ai and runs the account: sign-in, plan, invoices, tasks from the browser.
Scaleway SAS · based in France
Biwak on our server, when you work in the browser without the app.
Microsoft Ireland Operations Limited · based in Ireland
Runs the language models for every performance level.
Stripe Payments Europe, Ltd. · based in Ireland
Takes the payment. You enter your card or bank account directly at Stripe; Biwak never sees it.
Plus Five Five, Inc. · based in the USA
Sends sign-in codes and confirmations to you, error reports and notifications to us.
Linkup Technologies SAS · based in France
Searches the web when a task in the browser needs information.
If the agent opens a web page, it requests it directly: in the browser from our server in Paris, in the app from your computer. Both can be switched off.
GitHub, Inc. · based in the USA
Holds the app and its updates. Your computer downloads directly from there; every update is signed.
The app's engine also fetches a model list from ZenMux at start-up and, once, a memory model from npm and Hugging Face. These sources only see your IP address.
All details in the privacy policySTRATO GmbH · based in Germany
What you write to us, and copies of your error reports, are kept here.
Your task text, the conversation history it needs and the file contents the agent reads for it. They go encrypted to the Biwak relay at Supabase, which runs in the nearest data centre — from Germany in Frankfurt am Main — and from there, without any details of your account, to the language model at Microsoft Azure. Your files, conversations and checkpoints are stored only on your computer.
Not from the app. The relay passes the task through and, for allowance and billing, records only time, model, tokens, cost and a checksum; the conversation stays on your computer. In the workspace in the browser, conversations are stored in the account database in Frankfurt until you delete them, and your files, together with copies of the conversations, on our server in Paris, with no fixed period.
Conversations from the app are stored only on your computer; Biwak does not have them. Biwak opens conversations from the browser in the admin area only when there is a reason, such as support or troubleshooting, and every such access stays in the log for one year. If you send an error report, we also receive it in full by email.
In the workspace in the browser, the search terms the agent forms go to Linkup; your files are not sent with them. When the agent opens a web page, it requests it directly: in the browser from our server in Paris, in the app from your computer. Both can be switched off in the settings.
Behind every station on this map, and collected in section 9 of the privacy policy, each with version, checksum and the original from the provider.