TxID keeps a record of the conditions behind every answer, so a support conversation can be reviewed and reproduced later rather than taken on trust. This is the part institutional buyers are really asking about.
The record behind each answer
Every assistant answer carries the conditions it was produced under, opened from the shield beside it on the Conversations page:
Chain state
The ledger version the answer was true as of, so the exact chain state can be replayed later.
Prices at read time
The prices any figure rested on. A number about someone's position cannot be checked later without them.
What was checked
Which lookups ran, and any that failed, so a thin answer is never mistaken for a complete one.
Request context
Country and region, coarse device, surface and language.
Model and latency
Which model answered, and how long it took.
Answer hash
A SHA-256 of the answer, so any later change to the stored text is detectable.
Records cannot be quietly rewritten
Message content and the evidence behind it are append-only, enforced in the database rather than the application. Deletion is refused unless erasure is explicitly requested, and an erasure leaves a tombstone recording who did it and when, so a gap in the record is never unexplained. Views, exports and erasures are themselves logged.
Change history
Every configuration change is recorded on the Account page as change history: what changed, who changed it, and what it was before. Credential values are never recorded, only that a credential was set or cleared. The entries cannot be edited or deleted through the dashboard.
Exporting a conversation
A conversation can be exported with its full record attached: ledger version, the time the chain state was read, country, model and answer hash. The export logs itself as a disclosure, so there is a record of what left and when.
What is not stored
No IP address is kept in these records. Only country-level location is ever needed, and that is all that is stored. Infrastructure providers process IP addresses to route and rate limit requests, under their own retention policies. Device facts stop at platform and browser family and are never combined into an identifier.
For the buyer-facing summary of data handling and subprocessors, see the security page at txid.support/security.