Access and evidence
Built to be checked.
Every action is logged, and each record carries the hash of the one before it. SSNs, EINs and bank numbers come out before a model reads a page. A person approves what leaves.
A hash-chained record.
Each record carries the hash of the one before it, so an altered record no longer matches. The chain is re-checked every day, and every firm's whole chain every week.
Export it when an agency asks.
Filter the trail by employer or date and export it as CSV.
Response packets you can check.
Each response is assembled with its evidence into one packet that can be checked later.
Redacted first.
SSNs, EINs and bank numbers are redacted from a notice's text before a model reads it. A scanned page is read by a vision step, and its output is redacted the same way. A name-recognition layer is not deployed yet.
Logins and signatures.
Portal logins in a vault.
State-portal logins kept in a vault, with every reveal logged.
Signing links.
Letters and Form 8821-family authorizations signed by link.
What is live today.
Every line works in the product now.
- Credentials vaultLiveState-portal logins kept in a vault, with every reveal logged.
- Hash-chained audit trailLiveEvery action recorded, each record carrying the hash of the one before it.
- PII redactionLiveSSNs, EINs and bank numbers redacted before any model sees the text.It does not yet remove people's names.
- E-signature and POALiveSigning links for letters and Form 8821-family authorizations.
Questions about the record.
Can Kreto staff edit the audit trail?
The database refuses edits and deletes of audit records from every application role, Kreto staff included, and an altered record no longer matches its hash.
Are SSNs removed before a model reads a notice?
Yes. SSNs, EINs and bank numbers are redacted from a notice's text before a model reads it. People's names are not removed yet.
Bring one employer and its states.
A walkthrough of the part that worries you most, on your own records.