Everything on this page is written as something that has not happened. Nothing here is available, because a capability that has shipped belongs in the build log with the date it reached users.
There are no delivery dates. We have no delivery history to forecast from, so a date here would be a number invented to look confident. What each row carries instead is the state it is genuinely in and the date that state was last reviewed, which is the first Friday of the month.
A recorded session with a consenting participant, published whole, with the redaction log beside it. It is the missing artefact behind most of what this site cannot yet show: the demonstration on the home page, the session library, and every claim about whether a room changes anybody's mind. Until it exists the honest cell on the evidence page reads zero.
In development 24 August 2026
Three metrics have definitions and targets and no measured values: how often a persona simply agrees, how often two personas take opposed positions on the same claim, and how often the room surfaces an assumption the brief did not name. The rows sit visibly empty on the evidence page and will stay empty until enough real sessions exist to fill them.
In development 24 August 2026
None of this is built and the scaffolding it belongs to has not been started. It is in review rather than in development because the shape of the first enterprise customer decides the order, and we have no enterprise customers. If it is a hard requirement for you, say so on the demo form and we will tell you honestly where it sits.
In review 24 August 2026
Session audio and transcripts are processed in the United States today and there is no way to ask for anything else. A local region is a change to where the model runs as well as where the media server sits, so it is not a configuration flag. It is in review because the demand is real and the work is not scoped.
In review 24 August 2026
The browser client comes first because it needs nothing installed and no store review. The store applications follow it. Each channel page carries its own state and the date that state was last confirmed, so a store badge never appears before a listing a reader can open.
In development 24 August 2026
There is no operating history to base one on. A percentage invented before the service has run is a guess with a symbol after it, and publishing one would be the first dishonest thing on this site. A status page with a real incident log exists instead, and every incident stays on it. The agreement arrives when there is history to write it from.
Not planned 24 August 2026
We hold neither and we will not claim a stage of either one that we have not reached. Nobody in the set we crawled publishes one either. What exists instead is published now: the controls, a pre-signed data processing agreement, and every sub-processor named including the model vendor. An audit follows customers rather than leading them.
Not planned 24 August 2026
No, Tingvar does not have single sign-on today, and the enterprise scaffolding it belongs to has not been built. Single sign-on, tenancy controls and audit export are on the roadmap in the future tense, each with the state it is in, the date it was last reviewed, and no delivery date. We would rather you learned that here than on a call three weeks into a procurement. If it is a hard requirement, tell us on the demo form and we will say honestly where it sits.