Q: What security features does the mobile app have? What happens if an employee loses their phone?

Our app has multiple layers of security: Biometric Login: Supports fingerprint or face-scan login Session Timeout: The system automatically logs out after a period of inactivity Remote De-authorize: If an employee loses their phone, HR or IT can go into the backend system and immediately revoke that device's authorization, preventing others from accessing the data.

Question 1

Can we integrate with systems we already have, such as Active Directory for Single Sign-On (SSO)?

Accepted Answer

We have an API (Application Programming Interface) open for connecting with other systems. For specific requirements such as Single Sign-On (SSO) or integration with other ERP systems, please consult our technical team to assess feasibility and the scope of collaboration.

Question 2

Who owns the data on the platform?

Accepted Answer

Your company owns 100% of all data. Human Soft acts only as a Data Processor under contract. You have the right to access, edit, and export your data from the system at any time.

Question 3

If we decide to cancel the service, what happens to our data?

Accepted Answer

Before the contract ends, you can export all of your data from the system in standard file formats (e.g., Excel, CSV). After the contract ends, we have a data destruction policy following security best practices to protect your privacy.

Question 4

Can we set a Password Policy that matches our company standards?

Accepted Answer

Yes. You can set password complexity requirements such as minimum length, requiring uppercase/lowercase letters, numbers, special characters, and password expiration to enforce regular changes.

Question 5

What security features does the mobile app have? What happens if an employee loses their phone?

Accepted Answer

Our app has multiple layers of security:

Biometric Login: Supports fingerprint or face-scan login
Session Timeout: The system automatically logs out after a period of inactivity
Remote De-authorize: If an employee loses their phone, HR or IT can go into the backend system and immediately revoke that device's authorization, preventing others from accessing the data.

Question 6

How well does the system handle heavy concurrent usage at month-end?

Accepted Answer

Our system architecture is designed to support Load Balancing and Auto-scaling, meaning when usage is heavy — such as thousands of employees checking their payslips at once on payday — the system automatically scales resources (e.g., CPU, RAM) to handle the load, keeping the system fast and stable.

Frequently Asked Questions (FAQ)

faq > IT Department

faq > IT Department

faq > IT Department

Can we integrate with systems we already have, such as Active Directory for Single Sign-On (SSO)?+

Who owns the data on the platform?+

If we decide to cancel the service, what happens to our data?+

Can we set a Password Policy that matches our company standards?+

What security features does the mobile app have? What happens if an employee loses their phone?+

How well does the system handle heavy concurrent usage at month-end?+

faq > IT Department

Can we integrate with systems we already have, such as Active Directory for Single Sign-On (SSO)?+

Who owns the data on the platform?+

If we decide to cancel the service, what happens to our data?+

Can we set a Password Policy that matches our company standards?+

What security features does the mobile app have? What happens if an employee loses their phone?+

How well does the system handle heavy concurrent usage at month-end?+