Sub-processors
This is the customer-facing page derived from our internal Sub-processor Register (BWB-02.08). Where this page states a fact, it is the fact recorded in that register, including where the register records that something is not yet confirmed.
This page lists the companies we use to help us run Bidwhistle, and what each of them does with data. It is the authoritative list referred to in our Data Processing Agreement, and it is reproduced in Annex III of that document.
We publish it because you should not have to take our word for how your data is handled. Most companies in our sector do not publish a list like this. We think that is the wrong way round.
Where something is genuinely not settled — a hosting region a supplier has not stated, a transfer mechanism we have not yet recorded — this page says so rather than filling the gap with a reassuring guess. Where a position IS published, we quote it.
1. What a sub-processor is, in plain English
1.1 When you use Bidwhistle, you trust us with data — your saved searches and notes, the questions you ask Olivia, and the documents you upload to the Response Workspace. Under data protection law we are a processor of that data: you decide what goes in and why, and we handle it only to run the Service for you. (We are an independent controller of your account, billing and usage data; our Privacy Notice explains that separately.)
1.2 We do not build everything ourselves. We use other companies to host the application, store data, send emails and text messages, take payments, and run the AI models behind Olivia and behind the Response Workspace. Where one of those companies handles data on our behalf, it is a sub-processor.
1.3 A sub-processor is not free to do what it likes with your data. Each one is under a written contract requiring it to use the data only to provide its service to us, to keep it secure and confidential, to help with data subject requests and breach notification, and to delete the data when we tell it to. Two providers in Table B — the Google model behind Olivia, and Cartesia, which generates her voice — are reached through Anam rather than contracted by us directly, so the terms covering them are Anam’s, not ours. We say so in the table rather than leave you to work it out.
1.4 Three things are not on this list:
- companies we use for our own back office in a way that does not involve your data, such as our accountant or our bank — they are data controllers or processors for our own business records, and we describe them in our Privacy Notice;
- the public sources we collect Procurement Data from. Those are official government portals, not sub-processors — see section 8; and
- providers that handle no personal data at all. Two of those are listed anyway, in Table C, because a reviewer would otherwise wonder where they had gone.
2. How we choose sub-processors
2.1 Before we add a sub-processor we check its data protection terms, its security documentation, where it processes data, how long it keeps it, and — for AI providers — whether it would use data to train models. We prefer providers hosted in the EU or offering EU data residency.
2.2 We do not train AI models on your data ourselves, and we do not sell your data. What our AI providers do with it is a separate question, and we would rather be precise about it than reassuring. Each provider's position below is taken from that provider's own published terms, and quoted so you can check it against the source rather than take our word for it.
Our AI providers are a different question, and we would rather be precise about it than reassuring:
- Anam, which provides Olivia’s voice, avatar and speech, has confirmed that it does not use conversations for model training.
- The Google model that Olivia reasons on is reached through Anam and runs under Google’s standard terms, which do not give us a specific no-training commitment.
- Anthropic, which powers the Response Workspace, commits in its published Commercial Terms that “Anthropic may not train models on Customer Content from Services”. Its Data Processing Addendum, which carries the EU Standard Contractual Clauses, is incorporated automatically when those terms are accepted, so the commitment is contractual rather than an assurance given to us.
Voyage AI, which powers the knowledge search, is the exception, and we would rather say so plainly than bury it. Its published Terms of Service grant it a licence to use Customer Content “to train, improve, and otherwise further develop the Service” unless the customer opts out, and an opt-out “will apply only to Customer Content you submit after the time at which you opt out”. What reaches Voyage is the question you ask Olivia; no account identity travels with it. Bidwhistle has exercised the opt-out (James Rehman, 10 September 2026).
Table B records each AI provider’s position, as it stands today, so you can check it rather than take our word for it.
2.3 We remain fully responsible to you for what our sub-processors do with your data.
2.4 What “confirmed” means on this page. A position is only described as confirmed where the provider has told us so in writing or committed to it in terms we hold. Where our evidence is good but the paperwork is not yet in place, this page says that too.
3. How we notify changes
3.1 We give at least 30 days’ notice before a new sub-processor starts processing personal data on our behalf, or before an existing one takes on a materially different role.
3.2 We notify you in two ways: by updating this page, and by emailing everyone subscribed to sub-processor notifications.
3.3 Subscribe. Email privacy@bidwhistle.com with the subject line “Subscribe: sub-processor notifications” and the address you want us to use. Please subscribe someone whose inbox is monitored — a shared legal, security or operations address is usually better than one person’s. You can unsubscribe the same way.
3.4 An honest note about AI providers. Some AI and inference providers give us less than 30 days’ notice of their own changes, and occasionally we need to switch a model provider quickly to keep Olivia working. In those cases we cannot give you 30 days’ advance notice. We will notify you as soon as reasonably practicable and no later than the day the change takes effect, and your 30-day objection period runs from the date of our notice instead.
4. How to object
4.1 You can object to a new sub-processor within 30 days of our notice, on reasonable grounds relating to data protection. Email privacy@bidwhistle.com and tell us what your concern is.
4.2 If you do not object within 30 days, you are treated as having accepted the change.
4.3 If you do object, we will work with you in good faith for up to 30 days to find a resolution — explaining the safeguards, changing how the provider is configured, excluding your data where that is technically possible, or offering an alternative.
4.4 If we cannot resolve it, you may terminate the affected part of the Service and we will refund the fees you have paid for that part on a pro-rata basis for the unused remainder of your subscription period.
5. Table A — Infrastructure and platform sub-processors
The processing location column says where the data is processed, which is what matters for a transfer assessment. Where the company we contract with sits in a different country from the place it processes data, our contract is with the entity named in that provider’s own data processing terms. They are listed below, as each provider’s own terms named them on 28 September 2026; registration numbers are shown where the provider publishes them.
- Xano — Xano, Inc., 21600 Oxnard Street, Suite 910, Woodland Hills, California 91367, United States.
- Hetzner — Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany; Ansbach commercial register HRB 6089.
- WeWeb — WeWeb, Inc., 251 Little Falls Drive, Wilmington, Delaware 19808, United States, as named in its data processing agreement. WeWeb’s Terms and Conditions name WEWEB SAS, 128 rue La Boétie, 75008 Paris, RCS 839 313 848. We are settling which entity we contract with.
- Vercel — Vercel Inc., 440 N Barranca Ave #4133, Covina, California 91723, United States; Delaware registration 5857312.
- Anam — ANAM.AI LTD, White Collar Factory, Old Street Yard, London EC1Y 8AF, United Kingdom; company number 15214363.
- Google and Cartesia — contracted by Anam, not by us. Cartesia is Cartesia AI, Inc., 555 De Haro Street, Suite 300, San Francisco, California 94107, United States.
- Anthropic — Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland.
- Voyage AI — Voyage AI Innovations, Inc., United States, part of MongoDB, Inc.; its address is not published.
- Resend — Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, California 94114, United States.
- Stripe — Stripe Payments Europe, Limited, Ireland, joined by Stripe Technology Europe, Limited where Stripe’s service terms say so.
- Twilio — Twilio Ireland Limited, 70 Sir John Rogerson’s Quay, Dublin 2, D02 R296, Ireland.
- Hostinger — Hostinger International Limited, 61 Lordou Vironos str., 6023 Larnaca, Cyprus.
- Telegram and GitHub — handle no personal data.
| Name | Purpose | Data processed | Processing location | Transfer mechanism |
|---|---|---|---|---|
| Xano | System of record — the application backend, authentication, and all stored customer data | Name, e-mail address, company, sector, preferences, saved tenders, bids, alerts, usage and login events | London, United Kingdom (Google Cloud europe-west2). Our evidence points to London, but the supplier has not confirmed this in writing, including for backups. | None required for the storage leg on the evidence we have: the European Commission renewed its adequacy decisions for the United Kingdom on 19 December 2025, valid until 27 December 2031, so an EU-to-UK transfer needs no further mechanism. Xano, Inc. is a US company: its data processing addendum includes the EU standard contractual clauses, and it is certified under the EU–US Data Privacy Framework and its UK Extension, which covers any access from the United States, including by its own support tools. If the location turns out to be elsewhere we will put a mechanism in place and update this page |
| Hetzner | Ingestion host — the tender ingestion and scoring pipeline | Reads customer profiles in order to score them against tenders; holds no customer data at rest beyond logs | Nuremberg, Germany (EU) | None required (EU). Hetzner’s data processing agreement keeps processing inside the EU and EEA. We are recording our acceptance of Hetzner’s data processing agreement in our account. |
| WeWeb | The application front end — the Bidwhistle interface you use in your browser | Delivery of the interface. Your data passes between your browser and our system of record rather than resting with WeWeb, and your session token lives in your own browser | United States. WeWeb’s data processing agreement states that both its editor and the applications published with it are hosted on Amazon Web Services in the USA | EU standard contractual clauses, under WeWeb’s data processing agreement. WeWeb does not delete data automatically when a contract ends, so we will ask it to if we leave |
| Vercel | Hosting of the Olivia assistant embed | Static delivery of the embed. Session context passes through your browser, not through storage | Vercel edge; the region is immaterial because nothing rests there | None required — no personal data at rest. Should that change, Vercel’s data processing addendum includes the EU standard contractual clauses and the UK IDTA, and Vercel Inc. is certified under the EU–US Data Privacy Framework |
6. Table B — AI and inference sub-processors
These providers power Olivia — our AI assistant with a synthetic voice and animated avatar — and the Response Workspace, where you can have an uploaded tender pack read, have answers drafted, have a requirement explained and have a draft bid reviewed. The retention and training columns are the ones that matter most and that almost nobody publishes. They record the position as it actually stands, including where it is not yet confirmed.
| Name | Purpose | Data processed | Processing location | Retention | Uses data to train models? | Transfer mechanism |
|---|---|---|---|---|---|---|
| Anam | Olivia’s avatar, voice, speech-to-text and hosted reasoning | Your voice audio, the conversation transcript, and the profile context injected into the session | Anam runs production on CoreWeave in Spain (EU) and the eastern United States, and the region for a session is its choice. Region selection is an account entitlement that is not available on our current plan, so we cannot pin it to the EU today. Region selection and zero data retention are not available to us on the plan we hold. We are discussing both with the provider. | The session recording — your audio and the avatar video — and the transcript are kept 30 days, then deleted automatically; we also delete each session at Anam ourselves once it is 30 days old. Zero data retention is an account entitlement that is not available on our current plan | No — Anam has confirmed that it does not use conversations for model training | None required for our transfer to Anam: ANAM.AI LTD is a UK company, and the European Commission’s adequacy decisions for the United Kingdom cover it. Anam’s own onward transfers, including to the United States, are made under the UK transfer tools named in its data processing addendum. |
| Google (reached through Anam) | The reasoning model behind Olivia, contracted through Anam rather than directly by us | Whatever reaches the model during a conversation with Olivia | Reached through Anam; the processing location is not confirmed to us | Runs under Google’s standard terms. We hold no zero-retention commitment covering it | Not confirmed. It runs under Google’s standard terms, which do not give us a specific no-training commitment. This is the weakest data commitment in our chain and we would rather say so | An onward transfer made by Anam under its own contract with Google. We hold no direct contract with Google covering it and no no-training commitment for it, which is why it is described above as the weakest data commitment in our supply chain. |
| Cartesia (reached through Anam) | Olivia’s synthetic voice — turning her replies into speech — contracted through Anam rather than directly by us | The text of Olivia’s replies, as they are spoken | Not published. Cartesia AI, Inc. is a US company | Not stated to us | Not confirmed to us | An onward transfer made by Anam under its own contract. Cartesia’s data processing addendum uses the EU standard contractual clauses (Modules 2 and 3) and the UK Addendum. It also refers to the EU–US Data Privacy Framework, but Cartesia does not appear on the Framework’s official list (checked 28 September 2026) |
| Anthropic | The reasoning model behind the Response Workspace — reading an uploaded tender pack, drafting an answer, explaining a requirement, reviewing a draft bid | The uploaded document, your own bid text and your company name. A tender pack routinely carries personal data about other people, including staff of the incumbent supplier | Stored in the United States, the only storage region Anthropic offers; processed in any region by default | Anthropic states that it deletes API inputs and outputs within 30 days, except where its terms allow longer — for example to enforce its usage policy or meet a legal requirement | No. Anthropic's Commercial Terms state: “Anthropic may not train models on Customer Content from Services.” | Our contract is with Anthropic Ireland, Limited. Its Data Processing Addendum, incorporating the EU Standard Contractual Clauses (Module 2 or 3) with the UK Addendum and a Swiss addendum, is accepted automatically together with its Commercial Terms. |
| Voyage AI | Semantic retrieval for the assistant’s knowledge base — turning a question into a vector so we can find the right material | The question you ask, typed or spoken. No account identity travels with it | Not published. Voyage AI is a US company, part of MongoDB, and names Amazon Web Services, Google and Baseten as its own providers, so we treat the processing as taking place in the United States. | Not stated by default. Voyage's opt-out for its hosted model API endpoints also gives zero-day retention, so retention here follows the opt-out position in the next column. | Training: NO — Bidwhistle has exercised Voyage's opt-out (confirmed by James Rehman, 10 September 2026), so the questions customers ask are not used to train or improve Voyage's models, and their hosted endpoints hold them with zero-day retention. ⚠️ Voyage's terms take that licence BY DEFAULT unless a customer opts out, and an opt-out binds only Customer Content submitted after it — so the position rests on our having opted out, not on their default terms. Voyage AI was acquired by MongoDB on 24 February 2025 and the licence runs to its “successors and assigns”. Processing location: not stated in its published terms. Read 10 September 2026. | Voyage AI’s data processing addendum includes the EU standard contractual clauses, the UK Addendum and a Swiss addendum, and MongoDB, Inc.’s EU–US Data Privacy Framework certification covers Voyage AI Innovations, Inc. Voyage AI was acquired by MongoDB on 24 February 2025, and the licence in its terms runs to its “successors and assigns”. |
6.1 What this table is not. These positions are read from each provider's published terms, not from assurances given to us privately, and where a provider's terms are silent the column says so rather than implying a promise. One of them - Voyage AI - publishes a position we would rather not have to report, and it is stated in full above instead of being softened. We have not written “no” in a column where we do not hold the commitment, and we will not.
6.2 What we never send to an AI provider. Passwords, authentication secrets and session tokens; payment card data and billing records; your customer list or the identity of other Bidwhistle customers; and any content beyond what is needed to answer the request in hand.
6.3 We do not create voice embeddings, voiceprints or other derived voice data, and we do not store any. Olivia’s voice is synthetic; it is not a clone of any identifiable person’s voice.
6.4 Uploaded documents. When you upload a tender pack to the Response Workspace, the pack is passed through to Anthropic to answer your request and is not stored by us; only a usage row — token counts and a reference, no content — is written. You are the controller of everything in that pack, including personal data about people who are not your own staff. Our Data Processing Agreement and our Acceptable Use Policy explain what that means for you.
7. Table C — Business operations sub-processors
| Name | Purpose | Data processed | Processing location | Transfer mechanism |
|---|---|---|---|---|
| Resend | Alert and transactional e-mail — tender alerts, renewal reminders, and account and security notifications | E-mail address, name, and the tender content of the message | United States. Resend sends through Amazon SES in Ireland but stores message content, delivery logs, webhook payloads and account records in the United States, and keeps e-mail and log data for 30 days | EU standard contractual clauses (Module 2) with the UK Addendum, under Resend’s data processing addendum. Resend is also listed under the EU–US Data Privacy Framework (its re-certification was under review on 28 September 2026) |
| Stripe | Billing — card payments, subscriptions, invoicing and refunds | Name, e-mail address, billing address and payment method. Stripe holds the card details; we never do | United States (Stripe, LLC), under Stripe’s own terms | Stripe’s Data Transfers Addendum relies first on the EU–US Data Privacy Framework, under which Stripe, LLC is certified, and then on the EU standard contractual clauses and the UK Addendum. For fraud prevention and anti-money-laundering checks Stripe acts as a controller in its own right |
| Twilio | Text-message (SMS) alerts | Your mobile number and the text of the alert | Twilio’s default region is the eastern United States; its Dublin region also handles text messages. We have not confirmed which Twilio region our account uses. | Twilio’s data protection addendum relies on the EU–US Data Privacy Framework (Twilio Inc. is certified), then Twilio’s binding corporate rules, then the EU standard contractual clauses and the UK IDTA. Twilio also acts as a controller in its own right for some account and usage data |
| Hostinger | Our e-mail mailboxes — support, privacy, legal and security correspondence | Anything you write to us by e-mail, and our replies | Not published for a mailbox: Hostinger states data may be stored in the United Kingdom, the Netherlands, Lithuania or Cyprus, and in other places where necessary | EU standard contractual clauses (Module 2 or 3) with the UK Addendum, under Hostinger’s data processing agreement, for anything held outside the EEA |
| Telegram | Fault alerting — operational messages telling us something has broken | None. Operational messages only. Listed for completeness, not because it processes personal data | Global | None required — no personal data |
| GitHub | Source control | None, provided no customer data reaches the repository. Keeping it that way is a rule we apply to ourselves | Global | None required — no personal data |
7.1 Analytics. We do not use a separate third-party product analytics provider at present. If we introduce one, it will appear in this table and we will notify subscribers under section 3.
7.2 Support. Support is email only, through support@bidwhistle.com. Our mailboxes are hosted by Hostinger (Table C). We do not use a separate helpdesk product.
8. Sources, not sub-processors
8.1 The public procurement sources we collect Procurement Data from — in the UK the Find a Tender Service, Contracts Finder, Public Contracts Scotland, Sell2Wales, ProContract and local authority contract registers; Tenders Electronic Daily for the EU; and the national public procurement portals of Ireland, France, Spain, Germany, the Netherlands, Portugal, Poland, Finland, Austria, Estonia, Latvia, Denmark, Luxembourg, Hungary, Greece, Malta, the Czech Republic, Romania, Slovenia and Italy, each listed in our Privacy Notice (clause 4.4) — are sources, not sub-processors.
8.2 The difference matters. Data flows one way: from them to us. We do not send them your data, your searches, your questions or anything else about you, and they process nothing on our behalf. They are therefore not on this page, and no transfer mechanism arises for them.
8.3 We are an independent controller of the Procurement Data we collect from those sources, including the named public-sector contacts published in a notice. Our Privacy Notice explains that, the lawful basis for it, and how someone named in a notice can object.
9. International transfers
9.1 We are established in Estonia, so we are an EU exporter.
9.2 Two things that need no mechanism. If you are in the United Kingdom, transferring your data to us in Estonia is covered by the UK’s own adequacy regulations for the EEA, so nothing further is needed at your end. And our system of record sits in the United Kingdom (Xano, Table A), which makes that leg an EU-to-UK transfer covered by the European Commission’s renewed adequacy decisions of 19 December 2025, valid until 27 December 2031 with a review at the four-year point. Our transfer to Anam, a company established in the United Kingdom, is covered by the same decisions. No standard contractual clauses are required for any of these.
9.3 What does need a mechanism is processing in the United States: WeWeb, Anthropic, Voyage AI, Resend, Stripe and Twilio, and — through Anam — the Google model and Cartesia. Hetzner (Germany) is in the EU and needs nothing, and Hostinger (Cyprus) uses the EU standard contractual clauses for anything it holds outside the EEA.
9.4 For those onward transfers we use the EU standard contractual clauses (Commission Implementing Decision (EU) 2021/914), with the UK International Data Transfer Addendum for UK transfers and the Swiss overlay for Swiss transfers. Where a US provider is certified under the EU–US Data Privacy Framework we may rely on that certification, but we always put the standard contractual clauses in place as a fallback, so protection does not lapse if the framework is invalidated or a certification expires.
9.5 The mechanism for every provider is now recorded above, taken from each provider’s own terms on 28 September 2026. What is still open is marked in the tables as still to be confirmed, and sits on our action list ahead of launch. The training positions are no longer among those gaps: they are taken from each provider's published terms, and the Voyage opt-out is exercised.
9.6 The full detail, including our transfer impact assessment and the supplementary measures we apply, is in our Data Processing Agreement at Data Processing Agreement.
How to contact us
| What you need | Where to write |
|---|---|
| Subscribe to sub-processor notifications, or object to a sub-processor | privacy@bidwhistle.com |
| A signed copy of our Data Processing Agreement, or a formal legal notice | legal@bidwhistle.com |
| Security questions or vulnerability reports | security@bidwhistle.com |
| Anything else | support@bidwhistle.com |
Bidwhistle OÜ, Sepapaja tn 6, 15551 Tallinn, Estonia. Registry code 17567745.
Changes to this Sub-processors page
We update this page whenever our sub-processors change, and whenever one of the points marked above as still to be confirmed is answered — a confirmed hosting region, a confirmed retention or training position. Additions are notified at least 30 days in advance under section 3, with the exception in section 3.4 for AI providers who give us shorter notice. Removals, and changes that only correct a detail such as an entity name or a hosting region, are reflected here without advance notice but are recorded in the change log below.
| Version | Date | Change |
|---|---|---|
| 1.0 | 31 August 2026 | First published version of the sub-processor list. |
| 1.1 | 28 September 2026 | Every supplier checked against its own published terms on 28 September 2026: the company we contract with added for each; Resend and WeWeb corrected to storage in the United States; Cartesia, Twilio and Hostinger added; each transfer mechanism recorded; the notes on analytics and the support mailbox answered, and the remaining open points narrowed. |
| 1.2 | 29 September 2026 | Section 8.1 lists every public procurement source we read, to match the Privacy Notice (clause 4.4) of the same day: eTendersNI removed (never read); Germany, ProContract, local authority contract registers and 18 national portals added. Jim: "Yes, put the legal corrections live". |
| 1.3 | 15 November 2026 | Made publishable. The one open note — which Twilio region the account uses — is replaced by the plain statement that it has not been confirmed, so the page carries no bracketed note to ourselves. No supplier, purpose, location, retention or transfer mechanism changes. |