Organizations and GDPR

Every user has their own “Data & privacy” card where they can export their own data or request deletion; a request never deletes instantly — it creates an admin-reviewable request.

The audit log (its own Settings tile): an org Admin sees their own organization’s audit log — a trail of sensitive admin actions (user removal, role assignments, GDPR exports, employee document upload/deletion) with timestamp, actor, and a short summary. The trail now also covers plain employee edits, CSV imports, and bulk employee updates — but never a salary or compensation value, only which field changed. If the organization’s complete data is ever exported at platform level, that also shows up as a row in the log (GDPR transparency).

Viewing and exporting salary data is logged too. The audit log now gets a row every time someone opens an annual pay-equity snapshot, opens the EU Pay Transparency report, fetches the employer-certificate basis for an employee, fetches the pre-revision export, or saves the joint pay assessment — with who, when, which year/cycle/employee and how many rows it covered, but never a salary amount. CSV and PDF downloads made in the browser from an already-open page are not logged as separate rows. The self-service export under “Data & privacy” now also includes the pay transparency requests (EU directive, article 7) that concern you, including the answer you received.