Sample Pricing Trust For agencies About
Claims register

Every claim this website makes, and how we checked it.

Proven: a named automated test or a stated document backs it. Partly: part of it is proven, and the line says what is still to come. Not yet tested: true as far as the code shows, but nothing checks it yet.

Every sentence on this site is on this list with its status. If you find a sentence that is not here, tell us and we will fix the sentence or add the test.

  • 61Proven
  • 21Partly
  • 8Not yet tested
  • Register checked against production on 13 November 2026.

Tell us about a sentence

Data residency and no external AI.

4 claims: 3 Proven, 1 Partly

All storage and processing happens in Australia, on computers Trenthos controls. The AI models run there, and nothing from a brief is sent to an outside AI service.

Partly: code review and local models; an automated egress test is due before 1 December 2026.

Account and service emails are sent through Resend (a US company), and payments are taken by Stripe (United States and India). Neither receives your records.

Proven: automated tests (legal).

If you reach the Trenthos IME sign-up page from a link with campaign tags, or from another website, the app records those tags and the name of that website with your account. They are kept in Australia and sent to no other party.

Proven: automated tests (signup-source, signup, legal).

Our emails never name a claimant and never contain any of the records.

Proven: automated tests (emails).

Deletion and retention.

12 claims: 9 Proven, 3 Partly

On a trial, the identified original of the brief is deleted within 7 days of delivering the chronology.

Proven: automated tests (retention).

On a trial, everything else is deleted 30 days after delivery (or 30 days after your last upload if no chronology is delivered), and backup copies within 21 days after that.

Proven: automated tests (backup-retention, deletion-policy, purge, trial-deletion-v21).

If a trial registration is declined, the files sent are deleted at once and nothing is prepared from them.

Partly: the deletion is tested; the test is still to be named in the register.

The record that you accepted the trial undertaking is kept for 7 years after the trial is deleted, as evidence of your acceptance.

Proven: automated tests (trial-deletion-v21).

To allow one trial per examiner, a one-way coded value made from your email address and Ahpra number is kept after your account is deleted. It cannot be turned back into either.

Proven: automated tests (deletion).

A paid matter, or a whole account, is deleted on request after a typed confirmation and an undo window of up to 6 days.

Proven: automated tests (deletion).

Backup copies may persist for a limited time.

Proven: automated tests (deletion-card, legal).

When a paid service ends, its matters are deleted after 90 days, with a warning 14 days before.

Proven: automated tests (deletion).

Nothing is deleted because a payment failed. After a failed payment you keep full use for 14 days.

Proven: automated tests (billing).

Chronologies export one matter at a time, as PDF or Word; there is no export of a whole account at once.

Partly: the per-matter export is tested (export); a whole-account export is not built (checked 9 Nov 2026).

Published deletion times currently cover free trial matters only.

Proven: the paid-matter deletion time promises are switched off in production (checked 9 Nov 2026).

When a matter or account is deleted, the app keeps a deletion record you can copy; no email confirms that the deletion is complete. Each matter’s chronology can be downloaded as PDF or Word before you leave; there is no export of a whole account at once.

Partly: the deletion record and the per-matter export are tested; there is no completion email and no whole-account export (checked 9 Nov 2026).

Redaction.

Trials only; paid matters are processed as received.

9 claims: 7 Proven, 2 Partly

On a trial, identifying details are removed automatically on Trenthos computers before the chronology is prepared. No person reviews the original.

Proven: automated tests (redaction, trial-auto-release, undertaking-v21).

On a trial, redaction removes the claimant’s names and their variants, date of birth, address, personal phone and email, Medicare, claim, policy, licence, staff and record numbers, family and other private people, and other patients.

Partly: tested except for policy and licence numbers and another patient’s records in the brief.

On a trial, the names of clinicians, staff and organisations (employers included), document numbers and practice phone numbers are kept, because an examiner needs them.

Proven: automated tests (document-numbers, redacted-vision-guard, redaction-minimal, redaction-precision, redaction-r15-professional).

On a trial, a file is used only if every redaction check is clean. A file that cannot be made clean is left out.

Proven: automated tests (trial-auto-release).

On a trial, nothing is processed until every file has been redacted or left out.

Proven: automated tests (quarantine).

Nothing is prepared from a trial brief until the Ahpra check is approved.

Partly: the holding of files is tested; a test that no reading job runs before approval is still to come.

The trial preview hides the claimant’s identity, but it is not de-identified: a detail may be missed.

Proven: automated tests (billing, legal).

A trial matter’s record holds no identifying fields.

Proven: automated tests (trial-matter).

Paid matters are processed as the brief was received: the documents are not redacted and names are kept.

Proven: automated tests (standard-matter-identified).

Security.

15 claims: 8 Proven, 5 Partly, 2 Not yet tested

Records are encrypted in transit and at rest.

Partly: configured and checked by hand; no automated encryption-in-transit check yet.

On a trial, the identified original is held in a restricted area that is not copied to any backup. Within Trenthos, access is limited to a single operator account.

Partly: the area is tested; access is limited to the operator account.

Two-factor sign-in is required before any record can be opened. A new examiner may upload the trial brief first.

Proven: automated tests (auth, before-mfa-routes, before-mfa).

An idle session locks after 15 minutes and needs your PIN to resume. Five wrong PINs lock it for 15 minutes.

Proven: automated tests (auth-lock, pin, pin.service).

Passwords are stored only as a one-way hash (argon2id).

Partly: in the code; a test that pins the hash type is still to come.

Each practice’s records are separated in the database itself, by row-level security on every table that holds clinical records.

Proven: automated tests (api-login-role, billing, disclosure, rls).

The application can only add to the audit log. It cannot change or delete entries.

Proven: automated tests (audit-immutable, audit-owner).

Every opening of a matter, document, page or chronology through the app is recorded in the audit log.

Proven: automated tests (audit-immutable, download-audit, pipeline).

The app shows a matter, document, page or chronology only after it has saved the audit entry for that opening. If the entry cannot be saved, the app refuses the view and sends none of the content.

Proven: automated tests (matter-detail, phi-read-audit, read-audit-refusal).

A practice cannot yet obtain the audit record for its own matters: the record is kept, but there is no view, export or request route for it.

Not yet tested: the record is kept but not offered to the practice (checked 9 Nov 2026).

A practice has four roles: Admin, Examiner, Support and Reviewer. Admin, Examiner and Support may create and upload to a matter and run it.

Partly: tested for creating matters; a test that a Reviewer is refused on upload is still to come.

If we become aware of a data breach affecting your documents, we will tell you without undue delay.

Proven: stated in the Terms of Service; a written breach procedure is the check.

We do not claim SOC 2 or ISO 27001 certification.

Proven: no page of this website or the app claims either.

Named roles and two-factor sign-in apply to every account, and every opening of a matter is recorded, but the record is not yet offered to the practice: there is no view, export or request route for it.

Partly: roles, two-factor sign-in and the access record are tested; the record is not offered to the practice (checked 9 Nov 2026).

Incidents that affect customers are published in the incident log.

Not yet tested: a commitment by Trenthos; each entry within five business days of the fix.

AI use and disclosure.

5 claims: 4 Proven, 1 Not yet tested

Trenthos IME never writes an opinion or a report. Drafting is not available.

Proven: automated tests (methodology-statement.unit, trial-annexure.unit).

Your documents are never used to train an AI model.

Not yet tested: stated in the Terms of Service and Privacy Policy; no training pipeline exists to test.

Every AI call is logged with the model that answered it.

Proven: automated tests (ai.service).

The disclosure annexure is built from the system’s own records: the models and versions used, the dates, the settings, automatic redaction on trials, and the pages detected as not fully read.

Proven: automated tests (annexure-claims.unit, disclosure, methodology-versions, trial-annexure.unit).

Trenthos IME makes no decisions about people. The only automatic decision it makes is which details to hide on a trial.

Proven: the same tests as trial redaction (above).

Citations and accuracy.

14 claims: 7 Proven, 6 Partly, 1 Not yet tested

These counts come from synthetic test briefs built with deliberate traps. Most cases were written at points where the product had already been found wrong. They track fixes on hard cases. They are not an error rate on ordinary pages. Real records are harder to read than our synthetic test briefs, so a real brief can have more entries marked for checking than our test results show.

Every entry the product extracts carries a reference to a page of its own document.

Proven: automated tests (extraction).

Known gap: in tests, some entries cite the page next to the right one. The quote check does not catch all of these: where the cited page prints near-identical wording, the entry passes the check. In tests on 11 November 2026, 5 of 25 cases had an entry citing the page next to the right one; the quote check flagged 1 of the 5.

Each entry is linked to a page of its source document. Entries without a date are labelled undated.

Partly: the page link and the undated label are tested.

Known gap: in tests, some entries take a wrong date, and some are left undated when the page prints a date. In tests on 11 November 2026, 122 of 376 date cases took a wrong date (77) or were left undated (45).

Software checks that the quoted words of every entry are found on the cited page. A quote that is not found there is kept and flagged “Quote not found on page”.

Proven: automated tests (fact-quote-check, fact-quote-wiring, page-check, quote-locator).

This check does not confirm that the cited page is the correct one: where two pages print the same words, an entry can cite the wrong one and not be flagged.

Proven: automated tests (methodology-versions).

Clicking a reference opens the source page, with the quoted words highlighted.

Proven: automated tests (pdf-highlight, source-drawer).

Pages the product detects as not read in full are listed with the chronology. The list is not complete.

Partly: the list is tested in the exports.

Known gap: in tests, some pages with content that no entry reads are not listed. In tests on 11 November 2026, 19 of 37 cases had such a page that was not listed.

When the same fact appears twice, the entries are merged and every cited page is kept.

Partly: tests prove that every page the merged entries cited stays on the entry that remains. Only that entry’s own quote and wording are shown; the quotes of the merged entries are stored but not shown. If its quote is not on every page it now cites, it is marked for checking. The stored merge step has no test of its own yet.

Everyone in a practice account sees every matter in that account.

Partly: the app says so in its Team settings, and the matter list is filtered by account only; no automated test yet.

Every file in a brief is numbered D1, D2 and so on.

Partly: visible in every export; no named test.

Where two documents give different readings of the same measurement on the same day, or different dates for the injury, both readings are shown side by side with their pages, and the product does not say which is right.

Proven: automated tests (sources-differ, topic-view).

The 100-page synthetic sample brief took 16 minutes from upload to a ready chronology.

Proven: handoff MANIFEST, 5 Nov 2026.

A trial brief usually takes less than half an hour, longer when the server is busy.

Not yet tested: measured on the sample and the first trials; a queue-age alert is still to come.

The “Read by AI, not confirmed” mark appears only in the sample, from a test run with AI reading of scanned pages switched on. It is off in the service today.

Proven: switch off in production, 0 such pages (checked 9 Nov 2026).

Nothing is deleted or summarised to make the chronology, and no AI model ranks entries. The default view sorts entries into key events, course and routine using stored fields, and folds routine entries and repeated retellings behind one click; search covers every entry. Topics use term matching and show the terms that matched. The practice can merge two entries that record the same event, keeping every cited page. Exports leave out entries a reviewer rejected, and pages that could not be read are listed.

Partly: each part is tested except merging, whose test is not yet named (checked 9 Nov 2026).

Trial terms.

5 claims: 3 Proven, 1 Partly, 1 Not yet tested

The free trial covers one brief of up to 50 pages, with no card needed.

Partly: the 50-page limit is in the code and the trial has no checkout; a test that pins the 50 is still to come.

One trial per Ahpra registration, and one per email address.

Proven: automated tests (trial-abuse, trials).

A person checks your Ahpra registration on the public register before a trial brief is processed.

Not yet tested: a manual check, alerted to the operator.

A trial cannot be turned into a paid matter. For the full chronology, start a paid matter and upload the brief again.

Proven: automated tests (trial-v21, undertaking-v22, legal).

The trial preview is not for use in a report or as evidence.

Proven: stated in the trial undertaking and the Terms of Service.

Pricing and billing.

10 claims: 6 Proven, 3 Partly, 1 Not yet tested

Solo is A$119 a month at the launch price and A$149 after 12 months, with 2,000 pages a month. Solo Plus is A$249 a month at the launch price and A$299 after 12 months, with 5,000 pages a month. The launch price is for subscriptions started by 30 June 2027 and is held for 12 months.

Proven: automated tests (billing, payg).

Pay as you go is A$99 a brief for up to 500 pages, and A$79 for each further 500 pages or part.

Proven: automated tests (billing, payg).

Prices are in Australian dollars and include GST. The tax invoice shows our ABN.

Proven: automated tests (env, payg, tax-invoice).

A page is counted once. Reprocessing is free, the same file uploaded again within 12 months is not recounted, and trial pages never count.

Proven: automated tests (usage-calculator).

If you go over your allowance, a brief under way finishes and one more brief is allowed; you are never charged for extra pages without being asked.

Partly: tested; the extra-brief test is still to be named in the register.

Subscriptions can be cancelled online at any time, with no fee; access runs to the end of the month.

Not yet tested: set in the payment provider’s customer portal; a recorded check is still to come.

Charges made in error, and double charges, are refunded.

Partly: refunds are recorded and confirmed by email; the policy is stated in the Terms.

You are not charged twice for the same thing.

Proven: automated tests (billing).

Payment is handled by Stripe. Trenthos never sees or stores your full card number.

Partly: by design (Stripe hosted checkout, card details never reach Trenthos); no automated test.

The cost calculator uses only the published prices and allowances.

Proven: a build check compares the calculator’s prices and allowances with the app’s plans data and the plan cards on the page, and works through set examples.

Support and service levels.

3 claims: 1 Proven, 2 Not yet tested

The Ahpra check is usually made within one business day.

Not yet tested: an alert for a check waiting longer is still to come.

We do not guarantee availability or a response time. We aim to reply within one business day.

Proven: stated in the Terms of Service.

Each examiner can book a 20-minute walkthrough; support at support@trenthos.com is answered by a doctor.

Not yet tested: given by Trenthos; booked through the contact form.

Research.

2 claims: 2 Proven

Trenthos Research is at the planning stage: no partner, pilot, dataset or paper exists.

Proven: stated on the research page; no research has started.

The vendor questions article links each question to our own answer and to its status on this register.

Proven: a build check confirms each link reaches a published page and a row of this register, and that the status shown is the row’s own.

Product and service.

5 claims: 5 Proven

Trenthos IME does not connect to or replace a practice management system.

Proven: no connector exists in the product; files arrive only by upload (checked 9 Nov 2026).

The two reusable statements on the agencies page contain only sentences listed elsewhere in this register, each with its status.

Proven: a build check maps every sentence of each statement to a register row, Proven or Partly, and fails on any sentence without one.

The responsibility table on the service description restates Terms of Service clauses and register rows only.

Proven: a build check maps each cell to a register row or a Terms of Service clause.

The vendor assessment pack contains only sentences published elsewhere on this website.

Proven: a build check finds every sentence of the pack on the site, and a release check fails if a source page changed after the pack was built.

The brochure contains only sentences published elsewhere on this website.

Proven: a build check finds every sentence of the brochure on the site, and a release check fails if a source page changed after the brochure was built.