Botsense: what they publish
botsense.io · Conversational AI · checked 2026-09-24
Rank 37 of 42 in Conversational AI, where the median is 26.
- 0 found
- 12 not found
- 0 not measured
We measured 12 of 12 criteria for Botsense on 2026-09-24. We found 0 with a source and did not find 12 at the addresses we checked. That is a transparency score of 0 out of 100, band F.
Jump to a criterion 12
- Data processing agreement (DPA)
- Subprocessors: the published list
- Data location: where they say data is hosted
- Status page with incident history
- Public pricing with figures
- HTTPS enforced with HSTS
- No third-party tracking before consent
- Notice before subprocessors change
- Certifications named (SOC 2, ISO 27001)
- Uptime SLA with a figure
- security.txt (RFC 9116)
- Named privacy contact (DPO or privacy address)
Overview
4 days since the newest finding, 4 since the oldest. 12 of 12 criteria measured in the last 30 days.
Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.
Transparency labelsaas-ranking.com
Botsense
- A
- B
- C
- D
- E
- F
Published commitments0 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour0 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-24. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Botsense has no such document.
Where Botsense sits in Conversational AI
- A0 0%
- B0 0%
- C4 10%
- D7 17%
- E11 26%
- F20 48%
The band of Botsense is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.
What Botsense states
The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.
- Third-party hosts we saw on the first load 5 google-analytics.com, googleapis.com, googletagmanager.com, gstatic.com, ui-avatars.com.
Show the 5 exact wordings
region1.google-analytics.com
Read at https://botsense.io/fonts.googleapis.com
Read at https://botsense.io/www.googletagmanager.com
Read at https://botsense.io/fonts.gstatic.com
Read at https://botsense.io/ui-avatars.com
Read at https://botsense.io/
Gaps, heaviest first
Data processing agreement (DPA)
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-24.
Show the 8 addresses we checked
https://botsense.io/legal/dpa– reached, no match (HTTP 404)https://botsense.io/dpa– reached, no match (HTTP 404)https://botsense.io/legal/data-processing-agreement– reached, no match (HTTP 404)https://botsense.io/data-processing-agreement– reached, no match (HTTP 404)https://botsense.io/legal/data-processing-addendum– reached, no match (HTTP 404)https://botsense.io/legal/gdpr– reached, no match (HTTP 404)https://botsense.io/trust/dpa– reached, no match (HTTP 404)https://botsense.io/privacy/dpa– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data processing agreement in Conversational AI: 8 of 42 companies
Subprocessors: the published list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-24.
Show the 7 addresses we checked
https://botsense.io/legal/subprocessors– reached, no match (HTTP 404)https://botsense.io/subprocessors– reached, no match (HTTP 404)https://botsense.io/sub-processors– reached, no match (HTTP 404)https://botsense.io/legal/sub-processors– reached, no match (HTTP 404)https://botsense.io/trust/subprocessors– reached, no match (HTTP 404)https://botsense.io/privacy/subprocessors– reached, no match (HTTP 404)https://botsense.io/legal/subprocessor-list– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Subprocessor list in Conversational AI: 2 of 42 companies
Data location: where they say data is hosted
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-24.
Show the 7 addresses we checked
https://botsense.io/security– reached, no match (HTTP 404)https://botsense.io/trust– reached, no match (HTTP 404)https://botsense.io/legal/privacy– reached, no match (HTTP 404)https://botsense.io/privacy– reached, no match (HTTP 404)https://botsense.io/privacy-policy– reached, no match (HTTP 200)https://botsense.io/compliance– reached, no match (HTTP 404)https://botsense.io/legal/privacy-policy– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data location stated in Conversational AI: 16 of 42 companies
Status page with incident history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-24.
Show the 3 addresses we checked
https://status.botsense.io/– The name "status.botsense.io" could not be resolved.https://botsense.io/status– reached, no match (HTTP 404)https://botsense.io.statuspage.io/– Could not be fetched: fetch failed.
Is this wrong? Send us the URL
Across the market: Status page with history in Conversational AI: 11 of 43 companies
Public pricing with figures
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-24.
Show the 5 addresses we checked
https://botsense.io/pricing– reached and rendered, no matchhttps://botsense.io/pricing/– reached, no match (HTTP 200)https://botsense.io/plans– reached, no match (HTTP 404)https://botsense.io/en/pricing– reached, no match (HTTP 404)https://botsense.io/pricing-plans– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Public pricing in Conversational AI: 16 of 42 companies
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-24.
Show the 2 addresses we checked
http://botsense.io/– redirects to https://botsense.io/https://botsense.io/– no HSTS header
Is this wrong? Send us the URL
Across the market: HTTPS enforced with HSTS in Conversational AI: 29 of 44 companies
No third-party tracking before consent
weight 2 of 3Third-party requests seen on the first load, before any interaction.
- Third-party hosts we saw on the first load 5 google-analytics.com, googleapis.com, googletagmanager.com, gstatic.com, ui-avatars.com.
Show the 5 exact wordings
region1.google-analytics.com
Read at https://botsense.io/fonts.googleapis.com
Read at https://botsense.io/www.googletagmanager.com
Read at https://botsense.io/fonts.gstatic.com
Read at https://botsense.io/ui-avatars.com
Read at https://botsense.io/
Checked 1 address on 2026-09-24.
Show the 1 address we checked
https://botsense.io/– third-party requests before any interaction: fonts.googleapis.com, fonts.gstatic.com, region1.google-analytics.com, ui-avatars.com, www.googletagmanager.com
Is this wrong? Send us the URL
Across the market: No third-party tracking before consent in Conversational AI: 2 of 44 companies
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-24.
Show the 8 addresses we checked
https://botsense.io/legal/subprocessors– reached, no match (HTTP 404)https://botsense.io/subprocessors– reached, no match (HTTP 404)https://botsense.io/sub-processors– reached, no match (HTTP 404)https://botsense.io/legal/dpa– reached, no match (HTTP 404)https://botsense.io/dpa– reached, no match (HTTP 404)https://botsense.io/legal/data-processing-agreement– reached, no match (HTTP 404)https://botsense.io/trust/subprocessors– reached, no match (HTTP 404)https://botsense.io/legal/sub-processors– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Notice before subprocessors change in Conversational AI: 9 of 42 companies
Certifications named (SOC 2, ISO 27001)
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-24.
Show the 6 addresses we checked
https://botsense.io/security– reached, no match (HTTP 404)https://botsense.io/trust– reached, no match (HTTP 404)https://botsense.io/trust-center– reached, no match (HTTP 404)https://botsense.io/compliance– reached, no match (HTTP 404)https://botsense.io/legal/security– reached, no match (HTTP 404)https://trust.botsense.io/– The name "trust.botsense.io" could not be resolved.
Is this wrong? Send us the URL
Across the market: Certifications named in Conversational AI: 15 of 43 companies
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-24.
Show the 6 addresses we checked
https://botsense.io/legal/sla– reached, no match (HTTP 404)https://botsense.io/sla– reached, no match (HTTP 404)https://botsense.io/legal/service-level-agreement– reached, no match (HTTP 404)https://botsense.io/trust/sla– reached, no match (HTTP 404)https://botsense.io/uptime– reached, no match (HTTP 404)https://botsense.io/legal/uptime-sla– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Uptime SLA with a figure in Conversational AI: 3 of 42 companies
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-24.
Show the 1 address we checked
https://botsense.io/.well-known/security.txt– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: security.txt (RFC 9116) in Conversational AI: 6 of 40 companies
Named privacy contact (DPO or privacy address)
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-24.
Show the 7 addresses we checked
https://botsense.io/legal/privacy– reached, no match (HTTP 404)https://botsense.io/privacy– reached, no match (HTTP 404)https://botsense.io/privacy-policy– reached, no match (HTTP 200)https://botsense.io/legal/privacy-policy– reached, no match (HTTP 404)https://botsense.io/legal/privacy-notice– reached, no match (HTTP 404)https://botsense.io/trust/privacy– reached, no match (HTTP 404)https://botsense.io/datenschutz– reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Named privacy contact in Conversational AI: 23 of 42 companies
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Nothing to show here yet.
History
Compare
A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.