Truthring vs aivoicedetector.com
Checked on 31 August 2026, aivoicedetector.com states that “Truthring publishes our methodology” and that “The methodology is published and versioned”, and frames that versioning as what makes a verdict defensible in a deposition. On the same date, ten paths where such a document would live each returned HTTP 404, their sitemap listed none of them, and both on-page links labelled “methodology” resolved elsewhere.
They also publish two things we do not: a deletion window measured in hours, and a named list of the generators they cover. This page says so before it says anything else.
We make a competing product, so this is not a neutral document. It compares what each of us has put in public, at a stated URL on a stated date. Nothing rests on our word — every finding can be re-run in a browser in about ten minutes.
Start with what they do better
Their privacy policy, marked v1.0 and dated 25 May 2026, states that submitted audio is “deleted within 24 hours by default”, with a one-way 256-bit hash kept afterwards. That is a commitment expressed in a unit of time, under a version and a date. Our own retention page is honest that our windows are not fixed yet — the correct thing to write and a worse thing to offer. On this row they are ahead of us.
Second, on 31 August 2026 their /detect page named twenty specific generator systems. Naming the systems a detector was built against is more informative than counting them, and most of this field counts. The list carries no date and the copy says “24+” where twenty are named — but naming twenty beats naming none.
What each of us publishes
Their column records what was found at the stated URL on 31 August 2026. Ours records what Truthring commits to publish: we are pre-launch and hold no measured figures, and rows saying so are saying exactly that.
| Published item | Truthring | aivoicedetector.com — checked 31 Aug 2026 |
|---|---|---|
| False positive rate Genuine speech flagged as synthetic | Committed, both directions, by condition — no measured figure yet | Not found. Eight pages of aivoicedetector.com read on 31 Aug 2026 contained zero occurrences of the phrase “false positive”. |
| Written method, reachable | Published and versioned; the version that produced a verdict is named on the verdict | Referenced, not reachable. /methodology, /accuracy, /research, /security, /trust, /team, /whitepaper, /benchmarks, /methodology-v3 and /docs/methodology each returned HTTP 404 on 31 Aug 2026. Their sitemap.xml (53 URLs) contains none of them. The footer link “Read the methodology” resolves to /about-us; a second on-page “methodology” link resolves to a blog post. |
| Stated failure conditions | A dedicated page | Stated in prose, no dedicated page found. On 31 Aug 2026: “On heavily compressed audio (phone calls, low-bitrate WhatsApp), expect lower confidence”, and a stated minimum of “about half a second of clear speech”. |
| Accuracy broken out by condition | Framework published in advance; figures to follow with sample sizes | One figure only, on 31 Aug 2026: “99% on clean audio”. Compressed audio is described qualitatively with no number attached. |
| Generator coverage | Named and dated [VERIFY: publish the list and its date before launch] | Twenty systems named at aivoicedetector.com/detect on 31 Aug 2026, described in the copy as “24+”. The list carries no date. |
| Engine version shown on a result | Yes, on every verdict | Their published API sample shows "methodology": "v3.2" (documentation read 31 Aug 2026). We read the sample, not a live result. [VERIFY: confirm against a live verdict] |
| Reference for re-examination | Yes, on every verdict | Documented: “Every verdict gets a permanent URL and an APA-style citation”, and their API sample shows a citation_url with a sha256 fingerprint (read 31 Aug 2026). Documentation, not a live check. [VERIFY: confirm against a live verdict] |
| Named people behind the analysis | Committed before launch [VERIFY: names and roles] | None found on 31 Aug 2026. Their about page states “10 researchers and engineers” and names no one; /team returned HTTP 404; blog posts are bylined “AI Voice Detector Editorial Team”. |
| Audio retention, in units of time | Window not yet fixed — stated as undecided rather than rounded | Published and specific. “Deleted within 24 hours by default”, one-way 256-bit hash retained. Privacy policy v1.0, 25 May 2026. Ahead of us on this row. |
| Registered company identity | Lacewing Technologies, Navi Mumbai, India [VERIFY: registered trading name and number before launch] | An address is published — 71–75 Shelton Street, Covent Garden, London WC2H 9JQ — with the footer line “Filed in London since January 2023”. No registered company name and no company number were found at /about-us, /contact, /terms-and-conditions or /privacy on 31 Aug 2026. |
| Press citations, linked | No press coverage claimed — we are pre-launch and have none | “As cited in Forbes BBC Reuters Wired TechCrunch” appeared as plain unlinked text on 31 Aug 2026, with no article links, headlines or dates. The only external links on the homepage that day pointed at Google Fonts. |
Recorded as found at those URLs on 31 August 2026 and nothing more. A page we could not reach is recorded as not reached, never as not published. Corrections, published with a date: corrections@aivoicedetctor.com
The document the argument rests on
Most of the table is ordinary. Plenty of detectors omit a false positive rate; plenty name nobody. One row is different in kind, because it is not an omission but a load-bearing claim.
Their case for being usable in a dispute reads: “Each verdict carries a methodology version stamp, so the same test can be run against the same snapshot later, which is what makes it defensible.” The homepage compresses that to “Defensible methodology in deposition.” The whole structure depends on a snapshot existing somewhere a third party can read. A version number pointing at nothing cannot be re-run by opposing counsel, a regulator, or you.
So we looked, on 31 August 2026. Ten plausible paths — the ones a reader would try and a search engine would index — each returned HTTP 404. Their sitemap.xml lists 53 URLs and includes none of them. The footer link reading “Read the methodology” lands on their about page; a second link labelled with the word resolves to a blog post. That is four routes to the document, and on that date none arrived.
We are stating what those requests returned on one day, not what exists on their servers. The document may sit somewhere we did not look, or behind a login, and if so we will correct this page and date the correction. But a snapshot a reader cannot locate does not do the job the claim assigns it, and a deposition is exactly the setting where unlocatable and absent come to the same thing.
The check is worth learning regardless of vendor. Find the sentence claiming a published method, find the link, follow it. That sequence separates rigour from a claim about rigour, and it takes less time than reading the page the claim appears on.
What is missing from “99% on clean audio”
Their headline, verbatim on 31 August 2026: “99% on clean audio across 24+ generator models. We always report the confidence number; we never claim certainty we do not have.” The second sentence is a good instinct. The difficulty is not the figure but everything not attached to it.
A detection number measures one model against one set of clips at one threshold on one date. Strip those away and 99% is unfalsifiable: no dataset, no sample size, no test date, and no reachable method to consult, so it cannot be reproduced, challenged or aged. It is also one-directional. A detection rate rises simply by flagging more aggressively, and that is paid for in genuine speech wrongly called synthetic — the quantity that decides whether a detector can be pointed at an employee or a witness. On 31 August 2026 the phrase “false positive” appeared nowhere in the eight pages of theirs we read.
We are not asserting the figure is untrue; we have no way to know, and saying otherwise would be the same species of unsupported claim. We are saying a number with no dataset, no sample size, no date and no reachable method gives a reader nothing to work with — and that “clean audio” is the easiest condition there is, least like the compressed forwarded voice note in most people's actual problem.
Where they may be the better choice
- You want a deletion window you can point to today. Their 24-hour default is published, dated and specific. Ours is not yet, and if that decides it, it decides in their favour.
- You want to know which generators a tool was built against. Twenty named systems beats a count, and it is on their site now.
- They are shipping and we are not. A live product, a free tier of 50 checks a month, paid plans from $49 to $599 a month, and years of submissions. Truthring is pre-launch, and a working tool today beats a stated intention today.
- This page may already be stale. If they publish a false positive rate and a methodology URL that resolves, most of the argument above disappears — and the category is better for it. Re-run the checks yourself.
Where we intend to be the better choice
- When the verdict has to survive being questioned. What holds up is a readable method, both error rates by condition, a version stamp and a reference that reopens the analysis — not a percentage.
- When the audio is realistic rather than clean. A verdict on a twice-forwarded voice note is a different claim from one on a studio file, and a single figure across both misleads by construction.
- When you need the tool to admit it cannot tell. We return unclear where the audio will not support a verdict, and unknown generator where we cannot name the system.
Questions
Which of the two is more accurate?
Nobody can say from public information, us included. That comparison needs both detectors run over the same held-out clips at the same thresholds by an independent party, and no such public test existed for this pair on 31 August 2026. Assembling our own set would measure them on data we chose, which flatters whoever chose it. Hence a page about disclosure, which is checkable.
Are you saying aivoicedetector.com has no methodology?
No, and the distinction matters. We are saying that on 31 August 2026 nine specific URLs returned 404 and a tenth returned 403, their sitemap listed none of them, and two on-page “methodology” links resolved elsewhere. What exists on their servers is a separate question; if the document is published somewhere we missed, we will correct this page and date the correction.
Does an unlinked press strip mean the coverage is not real?
It does not — outlets do cite tools without the tool linking back. What we can report is the page: on 31 August 2026 the strip named Forbes, the BBC, Reuters, Wired and TechCrunch as plain text with no headline, date or link, and the homepage's only external links pointed at Google Fonts. A reader wanting to check had nothing to click.
Which should I use for an HR or legal matter?
Whichever can show its working when someone pushes back. In a proceeding the score is never the question; how it was produced, how often the method errs in the direction that harms the accused, and whether an independent party can repeat it are the questions.
Why trust a comparison written by a competitor?
You should not. Every finding is a URL, an HTTP status or a quoted sentence, chosen so you can re-check it without believing us. Where we read documentation rather than a live result, the row says so.
Our side of the table
Related comparisons
If you are mid-problem
All claims about aivoicedetector.com were verified against their live site on 31 August 2026 at the URLs named. Re-checked quarterly; next review due November 2026. Corrections are published with a date rather than made silently.