Who you are contracting with
The company
There is no legal entity to publish yet. No company name, no company number and no registered office appear on this page, because there is not one to print and a placeholder in a contracting party is worse than an empty line.
Until the entity is registered you are dealing with one person in the United Kingdom, on the terms at /terms. The data processing agreement at /dpa is readable and is marked a draft for the same reason: it cannot be executed by a party it cannot name. If that is not enough for your practice, it should not be, and waiting is the right call.
Write to hello@halebook.com and ask where it has got to.
The person
Halebook is built and run by one person, on their own, from the United Kingdom. That person is not named on this page yet, and until they are, treat the claim as unchecked. An unnamed person reading a client's bank statement is a fair reason to wait.
What is already true: a person opens a statement only when it does not tie out or a row is flagged, and every one of those reads writes a row you can read on your own data page. Who opened it, which client, which statement, and why.
Write to hello@halebook.com. It goes to one inbox, and that inbox is a person.
The accuracy number
We publish our measured tie-out rate once it is measured on real statements. Until then we show none. Not a rounded one, not an internal one, not one from a synthetic test set.
The harness exists and is in the repository. It runs a fixed corpus, checks every statement against the closing balance the statement itself prints with a tolerance of zero, and reports whether the run was meaningful. It currently reports that it was not, because the corpus is synthetic. When real statements go through it we publish the rate, the sample size, the date and the method together, and we publish it again when it moves.
Every competitor in this category publishes a figure. The category does not believe them. Refusing to publish one until it is true is the only version of this we can defend.
If something goes wrong
Report a security problem to hello@halebook.com. One person is responsible for answering it, and that person is the one described above.
- We assess within 4 hours: what happened, which workspaces, which data.
- We contain it: rotate the secret, revoke sessions, disable the path.
- We tell every affected practice within 24 hours, in writing, because you are the controller and your own 72-hour clock depends on ours.
- We notify the regulator within 72 hours where the threshold is met.
- We write a public note afterwards and link it from the security page.
There is no status page and no published uptime commitment yet. Both are on the list of things we do not have, on the security page, with the point at which we revisit them.
What we will not put on this page
- A customer count, because nobody has bought this yet and saying so is the honest version.
- Testimonials, because we have no customers to quote. The research quotes elsewhere on the site are labeled as research, from dated public threads, and they are not endorsements.
- Logos of firms that use us, for the same reason.
- A compliance badge for a certification we do not hold.
- A comparison scoreboard against other vendors. On a page with no customers it reads as a grudge.