Service Level Agreement
1. Scope and how this SLA works
1.1 This Service Level Agreement sets out our availability commitments, the remedies if we miss them, and our support targets. It forms part of the Agreement and is read with our Terms of Service.
1.2 It applies to paid subscriptions, monthly and annual, for as long as your account is in good standing and your Fees are paid.
1.3 It does not apply to free trials, to Beta Features, or to any period during which the Service is suspended under the Agreement for your breach or non-payment.
1.4 Section 7 sets out the remedy if we miss an availability target. Nothing here limits any liability that cannot lawfully be limited; the liability section of the Terms of Service governs everything else.
2. Definitions
Terms defined in the Terms of Service have the same meaning here.
| Term | Meaning |
|---|---|
| Core Platform | Tender search and filtering, saved searches, the generation and delivery of alerts, account and authentication, the Bidwhistle website and any API — that is, the Service other than AI Features |
| AI Features | Olivia and the other generative features of the Service, including the Response Workspace (uploading a tender pack and having it read, having answers drafted, having a requirement explained, having a draft bid reviewed), AI summaries, fit scores, AI-generated explanations and the knowledge base’s semantic search. They depend on Anam (Olivia’s avatar, voice and speech-to-text), a Google model contracted through Anam (Olivia’s reasoning), Anthropic (the Response Workspace) and Voyage AI (semantic retrieval) |
| Error Rate | For a given minute and a given part of the Service, the proportion of valid requests that fail — returning a server error, timing out, or failing to return a usable response |
| Downtime | A period during which the Error Rate for the Core Platform or for AI Features exceeds 5%. Availability is measured by whether the Service works, not by whether it can be reached: a page that loads but fails most requests is Downtime |
| Downtime Minutes | The number of whole minutes in a calendar month classified as Downtime for the relevant part of the Service, measured in one-minute intervals and counted separately for the Core Platform and for AI Features |
| Excluded Downtime | Minutes falling within any exclusion in clauses 5.1 to 5.10. They are removed from both sides of the calculation, so they neither count against us nor inflate the result |
| Monthly Uptime Percentage | Calculated for each part of the Service as set out in clause 4.2 |
| Business Hours | 09:00–17:00 UK time, Monday to Friday, excluding bank holidays in England and Wales |
| Business Day | A day on which Business Hours occur |
3. Availability commitments
3.1 For each calendar month we aim to achieve:
| Part of the Service | Monthly Uptime Percentage target |
|---|---|
| Core Platform | 99.5% |
| AI Features, including Olivia | 99.0% |
3.2 Why AI Features carry a lower target. An AI Feature has more moving parts that we run ourselves than a search page does: the Olivia embed, the session pipeline that carries audio and context to and from the provider, the retrieval layer behind the knowledge base, and the request routing that ties them together. Each of those is ours, each can fail on its own, and a fault in any of them shows as an AI Feature that will not work. On top of that, our model providers — Anam for Olivia’s avatar, voice and speech-to-text, a Google model reached through Anam for her reasoning, Anthropic for the Response Workspace, Voyage AI for semantic search — can degrade without going down, and degradation short of an outage usually reaches you as a slower or poorer AI response rather than as an error we could exclude. A lower target is the honest way to price all of that in. 99.0% a month is roughly seven hours; we expect to do better, and we would rather set a target we can meet than one that reads well.
3.3 The two targets are measured and reported separately. Downtime in AI Features does not count against the Core Platform, and the reverse.
3.4 The Core Platform has dependencies too. The system of record — the application backend, authentication and everything stored in your account — runs on Xano, and the tender ingestion and scoring pipeline runs on Hetzner in Nuremberg, Germany. An outage at either is Excluded Downtime — see clause 5.10.1. We choose our providers carefully and we will move if one lets us down, but we do not pay compensation for an outage at infrastructure we do not run.
4. How availability is measured, and by whom
4.1 Who measures it. We do, using our own monitoring system. We are a small company and we do not use an independent third-party auditor. We would rather tell you that than imply an assurance we do not have.
4.2 The calculation. For each part of the Service, and each calendar month:
Monthly Uptime Percentage = ((T − E − D) ÷ (T − E)) × 100
where T = total minutes in the calendar month, E = Excluded Downtime Minutes, and D = Downtime Minutes not already counted in E.
4.3 What we will share. On request to support@bidwhistle.com we will give you, for any of the last twelve months (or for as long as the Service has been available, if shorter): the Monthly Uptime Percentage for each part of the Service, the Downtime Minutes, and a short description of each incident that contributed — what happened, how long it lasted and what we did. We will not share raw monitoring data or anything that would reveal another customer’s information or our security configuration.
5. Exclusions
The following are Excluded Downtime and do not count against a target:
5.1 Scheduled maintenance notified in advance under section 6.
5.2 Emergency maintenance needed to protect the security, integrity or availability of the Service, or to apply an urgent fix.
5.3 Customer-caused issues — anything arising from your configuration, your integrations, your use of the Service other than as documented, an act or omission of you or your Authorised Users, or a suspension or rate limit applied under the Acceptable Use Policy.
5.4 Your network or equipment — your internet connection, DNS, firewall, proxy, VPN, browser, device, microphone or local network.
5.5 AI model provider outages — a failure, degradation, deprecation, rate limit or capacity restriction at a third-party AI provider, which affects AI Features only. The providers this covers today are Anam (Olivia’s avatar, voice and speech-to-text), Google (Olivia’s reasoning model, reached through Anam), Anthropic (the Response Workspace) and Voyage AI (semantic retrieval). This is why AI Features carry a lower target than the Core Platform.
5.6 Beta Features, previews and early-access features, which are outside this SLA entirely.
5.7 Force majeure — anything outside our reasonable control, including internet or utility failure, natural events, industrial action, war, terrorism, cyber attack on infrastructure we do not control, and government action.
5.8 Suspension for breach or non-payment under the Terms of Service.
5.9 Delay, incompleteness or error in Procurement Data at source is not Downtime. Our Terms of Service deals with data accuracy, and no credit or refund is available for claimed inaccuracies in Procurement Data.
5.10 Third-party providers, and the portals
5.10.1 Our own hosting. An outage at Xano, Hetzner, WeWeb or Vercel — the providers that run the Core Platform — is Excluded Downtime and does not count against our Core Platform target. We chose them and we are responsible for choosing well and for moving if one lets us down. We do not accept liability, and we do not pay compensation, for an outage at a provider we do not run. The same applies to Resend for alert email and Stripe for payments to the extent a failure there makes the Core Platform unusable.
5.10.2 Public procurement portals. A delay, outage or change at a source portal we ingest from is not Downtime, because it is not our Service that is unavailable — but nor is it an exclusion under this section. Clause 5.9 deals with the data itself.
6. Maintenance windows
6.1 Scheduled maintenance. We give at least 5 Business Days’ notice by email to your account’s administrative contact and in the Service, saying what we are doing, when, and what will be affected.
6.2 Preferred window. We schedule planned maintenance for Sundays between 22:00 and 02:00 UK time wherever we can, and we aim to keep planned maintenance under four hours in any calendar month.
6.3 Emergency maintenance. Sometimes we must act immediately — a security patch, a failing dependency, a fault that is making things worse. We give as much notice as the circumstances allow, and tell you afterwards what happened.
6.4 Maintenance notified under clause 6.1, and emergency maintenance under clause 6.3, is Excluded Downtime.
7. Remedies
7.1 No service credits. We do not offer service credits on any plan. Instead you get a right to leave:
If we miss the target for the same part of the Service in two consecutive calendar months, you may terminate your subscription and we will refund the pro-rata portion of any prepaid Fees for the unused remainder of the period. You must exercise that right within 30 days of the end of the second month, by emailing billing@bidwhistle.com.
We prefer this to credits on a monthly plan. A credit against next month’s fee on a small monthly subscription is worth very little; the ability to leave without penalty is worth something.
7.2 Chronic failure. The termination right in clause 7.1 applies to monthly and annual plans alike: two consecutive calendar months below target for the same part of the Service, exercisable within 30 days of the end of the second month, with a pro-rata refund of prepaid Fees.
7.3 Sole and exclusive remedy. The remedies in this section are your sole and exclusive remedy for our failure to meet an availability target. This does not affect any liability that cannot lawfully be excluded or limited, your rights if you are a consumer, or the liability provisions of the Terms of Service in respect of anything other than a missed availability target.
8. Support
8.1 How to reach us. Support is email only, at support@bidwhistle.com. We do not offer telephone or live chat support, and Olivia is not a support channel — she can help you use the product, but a support request needs a person.
8.2 When. Business Hours: 09:00–17:00 UK time, Monday to Friday, excluding bank holidays in England and Wales. Requests arriving outside those hours are treated as arriving at the start of the next Business Day.
8.3 First response targets.
| Priority | What it means | First response target |
|---|---|---|
| Urgent | The Service, or a core function of it, is unavailable or unusable for you and there is no workaround — you cannot log in, search is down, alerts have stopped, or you cannot access your data | 1 Business Day |
| Non-urgent | Everything else: questions, feature guidance, billing queries, minor faults, cosmetic issues, feature requests, and anything with a workaround | 3 Business Days |
8.4 These are targets, not guarantees. We will not always meet them. Missing a support target is not a breach of the Agreement and does not entitle you to a refund. We are a small team, and we would rather say that plainly than publish a response time we cannot honour. If your request is genuinely urgent and time-critical — a deadline that day — say so in the subject line and we will do what we can.
8.5 No resolution-time commitment. We commit to a first response, not to a fix by any particular time. Some problems are ours and quick; some are ours and slow; some sit with a third-party provider and are not ours to fix at all. We will tell you honestly which kind you have.
8.6 What to include in a support request. Your account email and organisation; what you were trying to do; what happened instead; the exact error message; the tender or notice reference if it is about a specific record; screenshots; your browser and device; when it started and whether it is still happening; and how urgent it is and why.
8.7 What support does not cover. Support helps you use Bidwhistle. It is not:
- bid writing — we will not draft, review, edit or advise on your bid;
- procurement, legal, tax, financial or eligibility advice — see our AI Use Disclosure and the Terms of Service;
- support for third-party tools — your CRM, spreadsheet software, email client, network or devices;
- custom development, integration work or data migration, unless separately agreed in writing; or
- training beyond reasonable guidance on how a feature works.
9. Incident communication
9.1 Email. For an incident that materially affects many customers, or that affects your account specifically, we email your account’s administrative contact — when it starts, when the position changes materially, and when it is resolved.
9.2 What we say. What is affected, what is not, what we know about the cause, what we are doing, and when we will next update. If we do not yet know the cause, we say so instead of guessing.
9.3 After a significant incident. For a significant incident we e-mail the account's administrative contact a short note: what happened, how long it lasted, what caused it, and what we are changing. We aim to do that within 10 Business Days of resolution.
9.4 Where an incident involves personal data, our Data Processing Agreement and Privacy Notice govern what we tell you and when. Those obligations are separate from, and are not limited by, this section.
10. Changes to this Service Level Agreement
10.1 The current version is always at Service Level Agreement, with its version number and effective date at the top.
10.2 If a change would, on balance, disadvantage you in a way that matters — lowering an uptime target, narrowing a remedy, or lengthening a support target — we will give at least 30 days’ notice by email and in the Service before it takes effect, and you may terminate before then on the terms in our Terms of Service. A change does not affect a claim relating to a month that has already ended.
10.3 Clarifications, corrections and improvements to a target may take effect when published.
| Version | Effective date | Changes |
|---|---|---|
| 1.0 | 31 August 2026 | First published version |
| 1.1 | 4 November 2026 | Outages at our own hosting providers excluded from the availability commitment (3.4, 5.10.1). Clause 4.1 states that we measure uptime with our own monitoring system. |
| 1.2 | 4 November 2026 | Service credits removed entirely: former 7.2 to 7.4, the credit bands and the claims section deleted, so the termination right is the only remedy. Former 4.2 (check frequency and locations) and former 10.1 (incident page) removed, and the maintenance-window annotation in 6.2 deleted. Sections renumbered, and the Excluded Downtime definition corrected to reach clause 5.10 so that the hosting exclusion introduced in v1.1 actually takes effect. |
11. How to contact us
Bidwhistle OÜ · Registry code 17567745 · Sepapaja tn 6, 15551 Tallinn, Estonia · https://www.bidwhistle.com
| What you need | |
|---|---|
| Support requests, uptime reports | support@bidwhistle.com |
| SLA claims, credits and refunds | billing@bidwhistle.com |
| Formal legal notices | legal@bidwhistle.com |
| Security issues and vulnerability reports | security@bidwhistle.com |
| Privacy and data protection | privacy@bidwhistle.com |
Related documents: our Terms of Service, Acceptable Use Policy, Data Processing Agreement, Refund and Cancellation Policy, AI Use Disclosure and Complaints Policy.