Your personal details never appear in our logs.
A log is the running diary an app writes as it works. Logs are a common place for sensitive data to leak, so nothing sensitive is written into ours.
Here is the failure this section is about. Something goes wrong, and the error message prints an employee's email or a policy number. That line then sits in a log file, readable, for as long as the logs are kept. Two layers stop it happening here.
First, by design. Document contents and your email address are never passed into a log message at all. When something fails, the code records the review ID and an error code. Nothing from the document goes with it. That is the primary guarantee.
Then, as a safety net. Every line the app writes goes through one piece of code that redacts personal details before the line is stored. It catches emails, US Social Security numbers, street addresses, ZIP codes, and phone numbers. It also catches policy and claim numbers, whether they are all digits or mixed, like POL-4432.
One gap stays open, and we would rather name it than leave you to find it. Names cannot be matched by pattern without redacting ordinary words along with them. So employee names are covered by the first rule, never log document contents, and not by the redactor. The redactor is a backstop. It is not the thing standing between your records and a log file.
log redaction · fixed rules
RedactingWhat a naive log might write
review POL-4432 for jane.doe@acme.com
at 42 Oak Street failed. Call
back on 555-238-9910What Koala actually writes
review [id] for [email]
at [address] failed. Call
back on [number]The redaction follows fixed rules, not a judgement call. The same input is always redacted the same way, so there is no AI model in the loop deciding whether your address counts as private.