How anonymity works

Not a setting you switch on. It is how the system is built.

Most sites promise privacy through policy — a rule that staff are told to follow. We enforce it through structure instead, so that the parts of the system a recruiter can reach have no route to your identity at all.

Your data is split in two

Your profile is stored as two separate records, in two separate places, with two separate sets of keys.

• The searchable half holds your skills, experience, location, authorisation, and expectations. This is what recruiters search. It contains nothing that identifies you.
• The sealed half holds your name, email address, phone number, your LinkedIn profile, your employment history and your original resume file. It is encrypted with its own dedicated key, and the services that serve recruiter search hold no permission to read it.

Your resume is redacted before it is processed

Contact details, addresses, and links are stripped from your resume text before it is analysed or summarised. The original file stays sealed; only the redacted version is ever used to make you findable. The order matters — analysing the original first and filtering afterwards would leave traces of your identity inside the searchable data.

What a recruiter sees, and when

• A card first — how well you match their role, your skills, experience, industry, location, pay range, availability and right to work. No name, and no employer names.
• Then the depth, if they choose to read it — your skills in detail, certifications, domain expertise, technical stack, leadership, and a career timeline with the durations and the seniority but not the companies.
• Then an approach — they tell you about the role and who they are. You can ask questions, accept, decline, or block them, all while still anonymous.
• Then, only if you choose it, your identity — the specific fields you tick, and nothing else.

Releasing details is a decision, not a default

When a recruiter requests a connection, nothing moves automatically. You see who is asking and what for, and you tick the specific fields you are willing to share. Accepting without ticking anything is a complete answer. Only the fields you tick are copied across, and every release is recorded so you can see what you shared, with whom, and when.

You can withdraw a release later. What you cannot undo is that they may already have read it — and saying otherwise would be a promise nobody can keep. Messages between you and a recruiter are relayed through the platform, so neither side sees the other's raw contact details unless they have been released.

Posting in the community feed

The feed is a separate identity. Posts and comments carry a posting alias that is never joined to your resume handle or to your profile — nobody but you can see that the two belong to the same account.

You may also choose to post under your real name. That is a deliberate, per-post choice, the composer says so before you publish, and it cannot be changed afterwards: an identity on a published post is the identity it was published with.

What we cannot promise

Anonymity has limits that no system can remove. A resume detailed enough to be useful may describe a career only one person has had. If you are the only person who held a particular role at a particular company, a determined reader may work out who you are. You control what goes in your profile — keep it specific enough to be found and general enough to stay comfortable.