Skip to content
RolePark
EN
About the product ↗

Security at RolePark

This page describes, in plain language, the protections that are already built into RolePark. The contractual commitments are in the Data Processing Agreement, and the vendors that process data are listed on the subprocessors page.

Updated:

In short

  • Each company’s data is separated from other companies on every request; another company’s record looks the same as one that does not exist.
  • All traffic goes over HTTPS with HSTS; employees’ salary, personal documents and military registration documents are encrypted in the database with AES-256-GCM.
  • Two-factor sign-in, SAML single sign-on and SCIM provisioning are available on every plan, Free included.
  • Daily database backups are kept for 30 days, and an administrator can export the whole company as one ZIP at any time.

Company data isolation

RolePark is one service for many companies. Every record — a candidate, a vacancy, a file, an audit-log entry — belongs to one company, and the server limits every request to the company of the signed-in user.

A request for another company’s record gets the same “not found” answer as a request for a record that does not exist, so it does not even reveal that the record exists.

Inside a company, roles decide what each person sees. A file opens only for someone who can open the record it belongs to, for example the candidate profile a CV is attached to.

Encryption

  • In transit: rolepark.com and its API are served over HTTPS. Browsers receive the HSTS header for 180 days, including subdomains, so after the first visit they connect only over HTTPS.
  • At rest: employees’ salary, personal documents and military registration documents are encrypted in the database with AES-256-GCM. Tokens of connected integrations are encrypted the same way with a separate key.
  • Passwords are stored only as bcrypt hashes, and two-factor backup codes only as hashes.
  • The web application sends a Content Security Policy and other security headers and cannot be embedded in a frame on another site.

Sign-in and user accounts

  • Two-factor authentication: any user can turn on one-time codes from an authenticator app (TOTP, RFC 6238). It works without SMS; ten one-time backup codes are shown once when it is turned on.
  • Passwords must be at least 10 characters and are checked against common passwords and the person’s own name and email. After repeated failed attempts, sign-in is temporarily locked.
  • Single sign-on: a company administrator connects an identity provider over SAML 2.0 and can then turn off password sign-in for the company.
  • Provisioning: SCIM 2.0 creates and deactivates user accounts from the company directory. Deactivation removes access and keeps the person’s history, signatures and scorecards.
  • Two-factor authentication, SAML and SCIM are available on every plan, Free included.

Audit logs

  • Audit log: successful changes made by signed-in people in the company workspace are recorded — who made them, when, which action and from which network. Anonymous channels, such as anonymous surveys and anonymous reports, are deliberately not logged, so that they stay anonymous.
  • Access log for sensitive HR data: every view of salary, personal documents or military registration data is recorded before the value is shown, and refused attempts are recorded too. An auditor reads the log without seeing the values.

Anonymised candidates at pipeline stages

A company can mark a pipeline stage as anonymised. While an application is at that stage, interviewers and hiring managers see “Candidate #NNNN” instead of the name, without the photo, contacts or social links, and the CV file does not open for them.

Recruiters, HR and administrators see the real data, and each of their views at an anonymised stage goes to the access log for sensitive data.

Backups

  • The database is backed up every day to a separate private storage bucket outside the application server (Google Cloud Storage). Each copy is checked after upload.
  • Daily copies are kept for 30 days and then deleted automatically, so deleted data also disappears from backups after 30 days.

Export the whole company as one ZIP

  • A company administrator can download the company’s data at any time as one ZIP archive: each table as JSON and CSV, plus the uploaded files.
  • Export is available on every plan, Free included.
  • Sensitive HR fields go into the archive only if the administrator may read them. Chats, import source records, document-signing links and technical logs are not included.
  • An archive can be up to 100 MB including files; for a larger company, contact support.

Company deletion with a backup copy

  • A company can ask to delete its account at help@rolepark.com.
  • Before anything is deleted, RolePark saves an archive of the company’s data and files in closed storage, reads it back and compares its size and SHA-256 checksum. If the check fails, nothing is deleted.
  • Then the company’s data and files are deleted and its users are pseudonymised: email, phone, photo and sign-in details are removed, first and last names remain in the history. PDF files of electronically signed documents currently remain.
  • The pre-deletion archive is kept in case of a mistaken deletion until the company asks to delete it; copies in database backups expire within 30 days.

Where the data is stored

  • The RolePark application and its PostgreSQL database run on a virtual server of a hosting provider. The data-centre country is available on request at help@rolepark.com.
  • Uploaded files (CVs, photos, documents) and daily database backups are stored in Google Cloud Storage.
  • Traffic to rolepark.com passes through Cloudflare: TLS, protection from attacks and caching.
  • CVs are parsed on RolePark’s own server, without AI or language-model providers.
  • RolePark is operated from Ukraine. Where the GDPR applies to a transfer, the Data Processing Agreement incorporates the EU Standard Contractual Clauses.

Subprocessors and legal documents

The subprocessors page lists every vendor that processes personal data, what it receives and where. The Data Processing Agreement sets out the security measures as a commitment (section 5), and the data retention page shows how long each kind of data is kept.

Report a vulnerability

If you find a security vulnerability in RolePark, write to help@rolepark.com with a description and the steps to reproduce it. Please do not access data that is not yours.

Legal documents