Designing for confidentiality from day one

Confidentiality is easy to promise and hard to keep. If it is added late, it leaks. We built Korum so that masking is enforced at the core, not painted on at the edges.

Masking at the source

When a confidential professional is returned by search, their identity is stripped before the data leaves the server - not hidden by the interface. The name, employer, exact location and contact details never reach the recruiter's browser in the first place.

Aliases, not blanks

A masked professional is not a faceless gap. They are given a stable alias so a recruiter can hold a real conversation and track interest - while the true identity stays sealed until consent.

What is always hidden in Confidential mode

• Real name and contact details
• Current employer and any hidden companies
• Exact location - only the country is shown
• Precise years of experience - only a band is shown

Consent gates

Every step that could expose a professional is gated by an explicit action they take. There is no path where a default, a bug in the interface, or a clever query can reveal someone who has not consented. The search layer itself is written to only ever match on the same fields a recruiter is allowed to see.

Defense in depth

Masking is applied on every surface a professional can appear - search, saved lists, applications, messaging - and each is tested against the same invariant: no identity, contact, employer or salary leak. Confidentiality is not a feature here. It is the foundation.