Privacy talent for India and Asia

Synthetic concept preview—no real candidates or jobs

A privacy career should come with privacy of your own.

Explore a hiring concept where professionals decide what to reveal and recruiters explain what they need. Try the candidate and recruiter controls using fictional profiles.

Try the hiring demo

Demo only. No real jobs, candidates or applications. The examples stay in your browser.

Candidate choiceClear role descriptionsLimited disclosure

Illustrative privacy practitioners and a recruiter in a calm professional conversation. — Illustrative image; people depicted are fictional/generated.

YOUR NEXT STEP

Try the candidate or recruiter view.

Both use fictional examples. You can explore the controls without sharing your own details.

I work in privacy

Choose which example skills are visible, then try pausing the profile.

Try candidate controls 02

I hire privacy professionals

Describe a role and explore the skills in the sample profiles.

Try the recruiter view 03

What stays private?

See which information the demo shows and which it does not collect.

Read the privacy details

Candidate dignity path

Choose what becomes visible—and reverse it.

Purpose-specific collection notice walkthrough

Prepare an anonymised recruitment signal

Data in this demo: Synthetic alias plus fields you select below.
Purpose: Show how role discovery could work without exposing identity.
Recipient: Only this browser’s synthetic recruiter view.
Retention: Local browser state until you clear it or browser storage is removed.

Real system: would need a reviewed notice, purpose/legal-basis decision, retention owner and enforceable rights workflow. This preview: creates no account and sends nothing.

Choose the smallest useful visible field set

Both choices are synthetic and optional. No seniority, role target, identity or contact field exists in these candidate fixtures.

Broad regionIndia only; no city or precise location.Visible capability signalsOnly the three signals already visible in the fixture.

Visibility control

Device-only controls

Recruiter-side preview

Talent fixture 01

Private draft

This fixture does not appear in recruiter results. Its bundled synthetic record still exists in the page code.

Identity hiddenContact absentResume absent

Start private. Review the purpose, then choose the smallest useful field set.

Visibility: private_draft
Deletion intent: none
Local events: 0
Network record: None

Recruiter legitimacy path

State the role purpose before seeing a fixture.

Organisation fixtureDemo OrganisationNot verified · synthetic only

Role fixtureDemo Privacy RoleNot posted · no vacancy claimed

Design reviewLawful purpose + necessityFuture production gate · not a legal determination

Build a fixed-option role purposeOperating purposeBroad region criterionRequired visible signal

Necessary-field and acceptable-use checklistDefined role purposeDiscovery is tied to Demo Privacy Role, not general browsing.Necessary visible fields onlyUse only broad region and visible signals selected by the fixture.No discriminatory useDo not infer protected or sensitive traits.No re-identificationDo not combine fields to guess a person.No scraping or bulk exportResults remain local and cannot be downloaded.No direct contact or resumeNeither exists in the result contract.Not-verified gate understoodThis unlocks synthetic discovery only; no organisation or role is verified.

Explicit not-verified gate

I understand that this preview does not verify me, Demo Organisation, or any role. It unlocks synthetic discovery on this device only.

Deterministic discovery

Visible synthetic results

Locked · not verified

Synthetic discovery is locked. Complete every safeguard acknowledgement first.

Discovery has not run

Complete the gate, then use fixed visible-field criteria.

In plain English

What would you share before a first conversation?

The demo above lets you try both sides. Here is how the proposed sharing rules work.

01 · profile visibility

Choose what a recruiter can see

Broad region + selected signalsPurpose-gated requestIdentity, contact & resume: never shown

02 · recruiter introduction

Purpose before discovery

Choose the type of role in the example.
Read and accept the demo’s limits on using profile information.
Explore the skills the fictional candidate has chosen to show.

Fictional organisation: not verified. This step opens example skills only, never contact details or an application.

03 · example profile

A profile starts with skills, not contact details.

Visible when chosen: Broad region · capability signals
Not collected: Name · contact · resume · seniority
Not inferred: Fit · rank · demographic · availability

ROLE PURPOSEVISIBLE SIGNALS

Deterministic connection

Lines form from selected role purpose to already-visible fixture fields. No score or recommendation is calculated.

Why the canopy matters

Only a stated purpose can meet the smallest visible signal set.

Connections are deterministic and limited to broad region and visible capability signals already included in the synthetic fixtures. They are not a recommendation, ranking or fit score.

Two-sided trust

Complete both journeys without pretending the service exists.

Candidate choice comes first. Recruiter access stays gated, purpose-bound and explicitly unverified.

Candidate path

Review purpose → minimise fields → preview → opt in → pause → export or record deletion intent.

Recruiter path

Define purpose → acknowledge safeguards → remain not verified → discover anonymised fixtures.

Four synthetic examples

Fixtures describe the demo—not people looking for work.

They exist only to make the privacy behaviour inspectable. No profile includes a photo, contact detail, employer, qualification, availability or application path.

Demo Candidate A

Controlled through the candidate walkthrough.

synthetic · not_verified

Demo Candidate B

A bundled anonymised fixture for local discovery.

synthetic · not_verified

Demo Organisation

A purpose-gate example, never a real employer.

synthetic · not_verified

Demo Privacy Role

A fixed-purpose example, never a vacancy.

synthetic · not_verified

Trust decisions before infrastructure

A future adapter may change. These boundaries may not.

Purpose

Explain the hiring use before collection.

Production needs a reviewed lawful-purpose and necessity decision. This demo makes no legal determination.

Visibility

Private, anonymised or paused—never silently public.

Deletion intent is separate from visibility and fails closed by removing the fixture from results.

Retention

Name the trigger, owner and deletion evidence.

The demo persists only synthetic local state. Production periods remain unapproved and unimplemented.

Access

No identity, contact or document in discovery.

A future relay and controlled resume access require verification, audit, rate limits and candidate permission.

Career and hiring guides

Judge privacy work by operating evidence.

Read all six guides →

01 · Role design

Notified does not always mean operative today.

The official ledger separates in-force and future commencement cohorts as rechecked on 30 August 2026. Product safeguards are design choices here, not compliance certification.

Review official sources

A privacy career should come with privacy of your own.

Try the candidate or recruiter view.

I work in privacy

I hire privacy professionals

What stays private?

Choose what becomes visible—and reverse it.

Prepare an anonymised recruitment signal

Talent fixture 01

State the role purpose before seeing a fixture.

Visible synthetic results

What would you share before a first conversation?

Choose what a recruiter can see

Purpose before discovery

A profile starts with skills, not contact details.

Only a stated purpose can meet the smallest visible signal set.

Complete both journeys without pretending the service exists.

Fixtures describe the demo—not people looking for work.

Demo Candidate A

Demo Candidate B

Demo Organisation

Demo Privacy Role

A future adapter may change. These boundaries may not.

Explain the hiring use before collection.

Private, anonymised or paused—never silently public.

Name the trigger, owner and deletion evidence.

No identity, contact or document in discovery.

Judge privacy work by operating evidence.

DPO, counsel, engineering or GRC?

Write a serious privacy job description.

Use a consistent, privacy-aware scorecard.

Build portfolio evidence safely.

Notified does not always mean operative today.