Understand the planned controls for access, files, devices and sensitive data, and the evidence to request before deployment.
MeridCore™ is a complete operations platform. This page describes its security principles and controls without claiming an unearned certification. Scope, test evidence and responsibilities are validated before real data is processed.
Permissions must follow organization, role, site and sensitivity. Restrictions must apply to screens, search, APIs, files and exports, not just hide a button.
MeridCore™ applies encryption, private storage, temporary access links and separation of sensitive HR records. Secrets must not appear in client code or ordinary logs.
Original events remain linked to corrections, authors, reasons and approvals. Sensitive access and exports require appropriate audit records.
Devices should be revocable and backups tested through restoration. Availability and recovery targets become commitments only after validation and contractual agreement.
The target excludes continuous location tracking, MeridCore™-managed biometrics in V1.0 and autonomous HR decisions. Approved AI uses require minimization, access controls and validation.
Before implementation, verify the tested scope, processing regions, providers, retention rules, exit arrangements and incident contacts.
This page makes no claim of SOC 2 certification, ISO 27001 certification or blanket regulatory compliance. Controls, hosting locations and service commitments is configured for the proposed scope.
Describe your current process, the people involved and the expected result. An initial discussion helps confirm the relevant scope.
Discuss this need