Every change carries an author and a date
Every data change is recorded with who made it and when. And when someone asks for their data, or asks to be forgotten, there is a path for that.
Why use it
The problems Avos solves in everyday HR.
No trail, no defence
When a salary looks different and nobody knows who changed it, the discussion becomes word against word.
Every data change is recorded with author, timestamp and what changed.
Data subject requests with no process
An export or deletion request arriving by email becomes a manual, risky task.
Exporting a person's data and anonymising it are operations of the platform itself.
Sensitive data stored in plain text
Identity documents and bank details in plain text are a leak waiting to happen.
Sensitive fields are encrypted at rest, and access depends on role permissions.
How it works
Work as usual
The trail is written automatically on every data mutation.
Look it up when needed
Filter by person, resource and period to reconstruct what happened.
Serve the data subject
Export a person's data, or anonymise it when that is the right answer.
Frequently asked questions
What goes into the audit trail?
Every data change passes through the audit trail, with author, timestamp, the resource affected and, where it makes sense, what changed.
Does Avos support GDPR and LGPD requests?
The platform provides export of a person's data and anonymisation, plus a retention routine — the process itself remains the company's.
Is sensitive data encrypted?
Yes, sensitive fields are encrypted at rest and access is controlled by permissions.