LiveVoice
livevoice.io · Live audio and interpretation · checked 2026-09-12
Rank 2 of 3 in Live audio and interpretation, where the median is 41.
- 4 found
- 7 not found
- 1 not measured
We measured 11 of 12 criteria for LiveVoice on 2026-09-12. We found 4 with a source and did not find 7 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 41 out of 100, band D.
Overview
0 days since the newest finding, 0 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
LiveVoice
- A
- B
- C
- D
- E
- F
Published commitments2 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- 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 behaviour2 of 2 found, 1 not measured
- foundHTTPS enforced with HSTS×2
- foundNo third-party tracking before consent×2
- not measuredsecurity.txt (RFC 9116)×1
Checked 2026-09-12. 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 LiveVoice has no such document.
Where LiveVoice sits in Live audio and interpretation
- A0 0%
- B1 33%
- C0 0%
- D1 33%
- E0 0%
- F1 33%
The band of LiveVoice 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 they state
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.
- Locations named next to the hosting wording European Union.
Show the exact wording
audio data sent by the client in a save environment, assuring GDPR conformity with its DPA in place. Servers for EU customers are located exclusively in the European Union.
Read at https://livevoice.io/en/legal/privacy - HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://livevoice.io/ - HSTS options includeSubDomains.
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://livevoice.io/
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-12.
Show the 8 addresses we checked
https://livevoice.io/legal/dpa– reached, no match (HTTP 404)https://livevoice.io/dpa– reached, no match (HTTP 404)https://livevoice.io/legal/data-processing-agreement– reached, no match (HTTP 404)https://livevoice.io/data-processing-agreement– reached, no match (HTTP 404)https://livevoice.io/legal/data-processing-addendum– reached, no match (HTTP 404)https://livevoice.io/legal/gdpr– reached, no match (HTTP 404)https://livevoice.io/trust/dpa– reached, no match (HTTP 404)https://livevoice.io/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-12.
Show the 7 addresses we checked
https://livevoice.io/legal/subprocessors– reached, no match (HTTP 404)https://livevoice.io/subprocessors– reached, no match (HTTP 404)https://livevoice.io/sub-processors– reached, no match (HTTP 404)https://livevoice.io/legal/sub-processors– reached, no match (HTTP 404)https://livevoice.io/trust/subprocessors– reached, no match (HTTP 404)https://livevoice.io/privacy/subprocessors– reached, no match (HTTP 404)https://livevoice.io/legal/subprocessor-list– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-12.
Show the 3 addresses we checked
https://status.livevoice.io/– The name "status.livevoice.io" could not be resolved.https://livevoice.io/status– reached, no match (HTTP 404)https://livevoice.io.statuspage.io/– Could not be fetched: fetch failed.
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-12.
Show the 8 addresses we checked
https://livevoice.io/legal/subprocessors– reached, no match (HTTP 404)https://livevoice.io/subprocessors– reached, no match (HTTP 404)https://livevoice.io/sub-processors– reached, no match (HTTP 404)https://livevoice.io/legal/dpa– reached, no match (HTTP 404)https://livevoice.io/dpa– reached, no match (HTTP 404)https://livevoice.io/legal/data-processing-agreement– reached, no match (HTTP 404)https://livevoice.io/trust/subprocessors– reached, no match (HTTP 404)https://livevoice.io/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-12.
Show the 6 addresses we checked
https://livevoice.io/security– reached, no match (HTTP 404)https://livevoice.io/trust– reached, no match (HTTP 404)https://livevoice.io/trust-center– reached, no match (HTTP 404)https://livevoice.io/compliance– reached, no match (HTTP 404)https://livevoice.io/legal/security– reached, no match (HTTP 404)https://trust.livevoice.io/– The name "trust.livevoice.io" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-12.
Show the 6 addresses we checked
https://livevoice.io/legal/sla– reached, no match (HTTP 404)https://livevoice.io/sla– reached, no match (HTTP 404)https://livevoice.io/legal/service-level-agreement– reached, no match (HTTP 404)https://livevoice.io/trust/sla– reached, no match (HTTP 404)https://livevoice.io/uptime– reached, no match (HTTP 404)https://livevoice.io/legal/uptime-sla– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-12.
Show the 7 addresses we checked
https://livevoice.io/legal/privacy– reached, no match (HTTP 200)https://livevoice.io/privacy– reached, no match (HTTP 200)https://livevoice.io/privacy-policy– reached, no match (HTTP 404)https://livevoice.io/legal/privacy-policy– reached, no match (HTTP 404)https://livevoice.io/legal/privacy-notice– reached, no match (HTTP 404)https://livevoice.io/trust/privacy– reached, no match (HTTP 404)https://livevoice.io/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 4
Data location stated
weight 3 of 3The hosting location is stated on a public page.
- Locations named next to the hosting wording European Union.
Show the exact wording
audio data sent by the client in a save environment, assuring GDPR conformity with its DPA in place. Servers for EU customers are located exclusively in the European Union.
Read at https://livevoice.io/en/legal/privacy
Source: https://livevoice.io/en/legal/privacy · checked 2026-09-12
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://livevoice.io/en/pricing · checked 2026-09-12
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
- HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://livevoice.io/ - HSTS options includeSubDomains.
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://livevoice.io/
Source: https://livevoice.io/ · checked 2026-09-12
No third-party tracking before consent
weight 2 of 3No third-party requests before any interaction.
Source: https://livevoice.io/ · checked 2026-09-12
Not measured by us 1
security.txt (RFC 9116)
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 1 address we checked
https://livevoice.io/.well-known/security.txt– blocked or unavailable (HTTP 500)
History
Not enough completed runs yet to draw a line. The next runs fill this in.
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.