Skip to content

Payroll and records

Compliance and audit trail

Roles, protected reporting and logs support responsible handling of people and applicant data.

  • revDSG and GDPR
  • Rights held in the database
  • Reporting channel and audit log
RewalzExample

Audit log

09:41

Permission changed

Noah Beispiel

09:32

Protected report received

Confidential reporting channel

09:15

Document added

Noah Beispiel

Illustrative product view · Fictional data

Limit access and document important actions.

  • Consent first

    No video exists before consent was given. Time and wording are kept.

  • Retention with a deadline

    You set the period and the records carry it with them.

  • Rights in the database

    Permissions live in the data layer and not in the interface.

  • Change log

    Who changed a score or watched a video stays traceable.

  • Protected reporting

    Concerns can be submitted confidentially and handled separately from personnel files.

  • Export for the audit

    The log can be exported, for your internal audit and for a supervisory authority.

How it works

Who may see what, and who did what. Neither lives in a policy document. Both live in the system.

  1. Assign roles

    Everyone gets a role in the company. What that role may open is defined in one place and applies to the application and to the database alike.

  2. The database enforces them

    Every query is bound to the caller's own tenant and to their role. A forgotten condition in the application therefore returns an empty list, never someone else's data.

  3. Keep evidence separate

    Audit records and protected reports remain traceable without distributing confidential content unnecessarily.

Frequently asked questions

Get to know Rewalz.

Rewalz is not open to everyone yet. Sign up and we will get in touch as soon as your access is ready.