ProHire databases are automatically backed up in real time and stored in a secure and remote data center not directly linked with our production servers to ensure redundancy of your data. Our server architecture is redundant, meaning even if one server fails, the system stays active and accessible.
We maintain more than 99% uptime, which guarantees you service continuity and quality assurance.
Our support team is trained to resolve any incident and is available during business hours 7 days a week by email and phone.
Server-to-client communications are encrypted with TLS (HTTPS). The system is designed to prevent any plain communication through the Internet.
ProHire only stores and processes data in Tier 3 data centers, with biometric access control, onsite energy production systems and all IT equipment being dual-powered and provided with two redundancies.
We use compliance best practices to manage vulnerabilities and track our dependencies for known CVEs. We closely monitor security mailing lists to be aware of the latest threats. To further limit potential risks, we configure our services with tight firewall rules.
Our code is scanned for known CVEs in the dependencies we're using.
ProHire encrypts at rest using AES 256. All connections from your browser to ProHire enforce TLS encryption. We only store passwords as salted hashes, not plain passwords.
All data and the database are backed up in real-time, and documents are backed up periodically throughout the day, 7 days a week. Our backups are in a different availability zone than live data.
Any connection to our systems is logged.
We monitor external services and open source libraries for security issues. We use automated tools to continuously scan for service interruptions, performance degradation, and security vulnerabilities and alert our engineers as incidents are detected.
To ensure system availability and provide the best experience, we review and test all updates to ProHire. For each change, we perform unit and end-to-end tests. Our quality assurance team evaluates and manually tests functions expected to be impacted by a change to ensure they're not negatively impacted by a regression.
After we release a change, we continue to monitor and log exceptions and schedule them for resolution. We use several monitoring services to monitor any impact to performance from changes.