The audit chain
Every approval, correction and deletion is written to your audit log. Each entry carries a fingerprint of the one before it, so removing or editing an old entry breaks the chain, and the nightly check shows exactly where.
- Entry 1041Harvest approved, B2prev 7c1e…a90bhash 3f9a…12cd
- Entry 1042Daily record correctedprev 3f9a…12cdhash b04e…77f1
- Entry 1043Member role changedprev b04e…77f1hash 9d22…c3a8
Chain verified every night. Admins see the result on the Audit log page.
Who sees what
Each member has a role and, if you choose, a list of sites. The server checks both on every request, every export and every AI answer, so a hidden button is never the only lock.
- Owner
- Admin
- Manager
- Field staff
- Viewer
- + your own roles
When Anowa support needs to look inside a workspace to help, the session is time-limited and recorded in that organisation's own audit log.
Signing in
Passwords are never stored in readable form. Two-step sign-in works with any authenticator app, with one-time recovery codes for a lost phone. Repeated failed attempts slow down, and a bot check stops automated guessing.
Data on the move
Everything between your phone and Anowa travels over HTTPS. Provider keys for AI, WhatsApp and SMS are encrypted and used only on our servers. File downloads use short-lived links, and data exports expire after 7 days.
Reporting a weakness
If you find a security problem, email us before sharing it anywhere else, with enough detail to reproduce it. We confirm we got it, keep you posted while we fix it, and credit you if you like. Please don't access other people's data or disrupt the service while testing.