Skip to main content
Empuls restricts access to company data stored in its system to a small group of designated senior personnel — specifically the CTO and production heads — ensuring your organisation’s information is never exposed to general internal staff.
When organisations connect Empuls to their HR systems — whether Workday, SAP SuccessFactors, or Darwinbox — employee data flows into Empuls to power recognition workflows, rewards programmes, and engagement surveys. Understanding exactly who can view that data is a critical governance question for IT teams, Data Protection Officers, and People leaders evaluating Xoxoday Empuls as a vendor.

​
How Empuls controls internal data access

Empuls enforces a strict access model at the infrastructure level. Only two categories of senior personnel hold authority to access raw company data: the CTO and designated production heads. This is not a configurable setting that individual customers adjust — it is an enforced architectural constraint built into how Empuls operates its production environment. Empuls’s wider engineering, product, customer success, and support teams cannot query or retrieve the data your organisation enters. Day-to-day operational staff interact with anonymised metrics and aggregated system reports, never with raw employee records or transaction histories. This separation of concerns mirrors the principle of least privilege, a foundational control in environments certified to ISO 27001 and audited against SOC 2 Type II criteria.

​
A practical example

Consider an organisation running Empuls alongside Microsoft Teams and Workday. When a manager sends a recognition shoutout through the Empuls bot in Teams, or when employee profiles sync automatically from Workday, that data is written to Empuls’s secure cloud environment. The only individuals within Xoxoday who could access that raw record are the CTO and production heads — not the support agent handling a service ticket, and not the engineer deploying a software update. This boundary holds regardless of the integration in use. Whether employee data enters Empuls via an API connection to SAP SuccessFactors, a CSV upload, or a Darwinbox sync, the same access restrictions apply across the entire data layer.

​
Why this matters for compliance and vendor due diligence

Strict internal access controls directly support compliance with data protection regulations such as GDPR, where data minimisation and access restriction are explicit requirements. People teams operating in regulated industries — financial services, healthcare, or government — can use this access model as documented evidence during vendor due-diligence and security assessments. Empuls’s SOC 2 Type II audit covers logical access controls as a key trust service criterion, meaning this access architecture is independently verified, not simply self-declared. Administrators can review active security controls and integration permissions directly within the Empuls security settings console. Learn more: Empuls Help Centre — Data

How does Empuls encrypt stored data?

Understand the encryption standards Empuls applies to data at rest and in transit across its cloud infrastructure.

What compliance certifications does Empuls hold?

Learn about Empuls’s ISO 27001, SOC 2 Type II, and GDPR compliance posture for enterprise deployments.