Empuls makes its full client data schema available in CSV format to every customer with no separate NDA required, in direct alignment with public record disclosure obligations including NC General Statute 132.
What public record law requires from SaaS vendors
Public record laws such as NC General Statute 132 establish that government entities—and the vendors serving them—bear a responsibility not just to retain records, but to make the structure of that data accessible. This extends beyond the records themselves to what legislators and compliance teams refer to as a “data schema”—the metadata describing how information is organized, labeled, and stored. HR and IT professionals working with municipalities, public universities, or state agencies need to understand exactly how Empuls handles this obligation before signing or renewing a contract.What a data schema means in the context of Empuls
A data schema defines the fields, data types, relationships, and structure behind every record a system produces. For Xoxoday Empuls, this covers reward transactions, user profiles, redemption histories, peer recognition events, and engagement milestones. Knowing the schema allows an organization to interpret exported data correctly, build downstream integrations, and fulfill audit or public disclosure requests with full fidelity. Without it, raw exports become difficult to map to internal systems or legal reporting requirements.How Empuls handles schema disclosure
Empuls provides a complete CSV data schema to all customers as a standard deliverable. The schema documents every field available in the platform’s data exports, giving HR administrators and IT teams a precise map of the underlying data structure. No additional NDA or legal agreement is required to access, use, share, or publish this schema. Customers are at full liberty to distribute it internally or externally as their compliance obligations demand.A practical example with common HRIS integrations
Consider a public agency that connects Empuls with Workday or SAP SuccessFactors to manage employee lifecycle data. When a records request arrives, the agency’s IT team uses the Empuls CSV schema to map recognition and rewards data to the correct fields in their HRIS export—without waiting on vendor approval or signing supplemental paperwork. Teams running Darwinbox alongside Empuls follow the same process: the published schema lets them validate cross-system data pipelines and produce audit-ready exports on demand. Organizations that route Empuls notifications through Slack or MS Teams can also use the schema to correlate engagement event logs with communication records when required by auditors.Alignment with Empuls’s broader security posture
Empuls operates under a security framework aligned with SOC 2 Type II and ISO 27001 standards, both of which require transparent and auditable data handling practices. Publishing the data schema is consistent with these certifications—it treats structural metadata as a customer asset rather than proprietary information. Compliance officers and legal teams can review, retain, and share the schema with their own auditors without initiating a separate procurement or legal review cycle. For organizations subject to NC General Statute 132 or equivalent statutes in other jurisdictions, Empuls removes the friction between platform adoption and public disclosure obligations. The schema is available, it is yours, and no additional agreement stands between you and it. Learn more: Empuls Help Centre — Public Record LawData Export and Portability in Empuls
Understand how Empuls structures CSV and API-based data exports, including field definitions and supported formats for HRIS integrations.
SOC 2 Type II and ISO 27001 Compliance
Learn how Empuls maintains SOC 2 Type II and ISO 27001 certifications and what these mean for your organization’s data governance obligations.