IT asks: What data does Empatyzer collect and which is mandatory?

TL;DR:

  • Basic fields: age, gender, join date, reporting lines — used to contextualize diagnostics, micro-lessons and assistant responses.
  • Only a minimal set is mandatory for system operation; most information is optional.
  • Empatyzer follows data minimization: raw individual results are not shared with the company and conversations with Em stay private.

Empatyzer collects a small set of basic data: age, gender, join date and reporting structure (who reports to whom). These fields help tailor diagnostics, micro-lessons and Em's responses. Typically only some fields are required at sign-up; others can be added later. Mandatory data is limited to what's strictly necessary for organizational features and security. Optional details may include communication preferences, project roles, consent for comparisons and extra privacy settings. The product is built around minimization: the company only receives aggregated team- or department-level data, not raw individual profiles. Conversations with Em remain private and are not passed to HR or managers, and vendor administrative access is monitored and audited. Users control their profile visibility, can hide their profile or delete their account, triggering data removal according to retention policy. Integrations with HRIS and SSO are optional and generally discouraged to preserve independence and comfort; deployment needs minimal IT support. Employee communications should stress voluntariness, that the tool isn't used for performance reviews, and outline encryption and processing practices to reassure about privacy.

Summary: only minimal fields are mandatory (age, gender, join date, reporting lines); everything else is optional. Privacy, minimization and aggregation are core principles.

Author: Empatyzer

Published:

Updated: