Privacy posture

What data OpenHR holds

OpenHR is an HR system, so by design it holds employee personal data uploaded by customer admins: names, contact information, employment history, leave balances, time records, payroll components, and performance review content. Biometric device events, when those modules are enabled.

What OpenHR does with that data

The application code uses customer data to provide configured HR functions. Before using a hosted deployment with real employee data, the operator must document its controller and processor roles, purposes, lawful bases, and any optional analytics.

Data residency and control

OpenHR can be self-hosted. Actual data locations depend on the configured database, object storage, email, messaging, analytics, and payment providers. OpenHR does not currently offer a region selector at signup; residency requirements must be confirmed before onboarding.

Retention and export

Some reports support direct export. A universal workspace export and an automated post-cancellation deletion schedule are not currently available in the product. Operators must define, document, and test retention, backup, export, and deletion procedures before production use.

Subprocessors

Provider choices are deployment-specific and may include hosting, database, object storage, payments, transactional email, WhatsApp, and optional analytics. The deployment operator must publish the exact current list and change-notification process.

Data-subject rights

The product supports correction and deletion for selected records, subject to permissions and business rules. The deployment operator remains responsible for a verified request channel and for completing access, deletion, restriction, objection, and portability requests across the application, backups, and subprocessors.

Do not import production personal data until the deployment operator has published binding privacy information and, where required, executed a data-processing agreement.