Privacy talent for India and Asia
Synthetic educational demonstration—no real candidates or jobs
Explore how a privacy-first talent marketplace could work.
A plain-language concept for privacy professionals and responsible hiring teams. Candidates choose what is visible; recruiters explain a purpose before requesting more. It cannot tell you who is available, verify anyone, or accept an application.
Local by design. This demonstration never reveals identity, contact data or a resume—and never sends an application or request.
- 4
- named synthetic records
- 0
- runtime network submissions
- 1
- device-only demo adapter

In plain English
A conversation, not a directory of people.
These diagrams show the product rules a real pilot would need to honour. They do not create a live marketplace.
Purpose before discovery
- State a fixed demo role purpose.
- Acknowledge field minimisation and safe use.
- See only already-visible broad signals.
Boundary: Demo Organisation remains not_verified; this unlocks no contact, identity, role or application.
A fixture is a small, synthetic signal set.
- Visible when chosen
- Broad region · capability signals
- Not collected
- Name · contact · resume · seniority
- Not inferred
- Fit · rank · demographic · availability
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 dignity path
Choose what becomes visible—and reverse it.
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.
Talent fixture 01
This fixture does not appear in recruiter results. Its bundled synthetic record still exists in the page code.
- Visibility
- private_draft
- Deletion intent
- none
- Local events
- 0
- Network record
- None
Recruiter legitimacy path
State the role purpose before seeing a fixture.
I understand that this preview does not verify me, Demo Organisation, or any role. It unlocks synthetic discovery on this device only.
Visible synthetic results
Complete the gate, then use fixed visible-field criteria.
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_verifiedDemo Candidate B
A bundled anonymised fixture for local discovery.
synthetic · not_verifiedDemo Organisation
A purpose-gate example, never a real employer.
synthetic · not_verifiedDemo Privacy Role
A fixed-purpose example, never a vacancy.
synthetic · not_verifiedTrust decisions before infrastructure
A future adapter may change. These boundaries may not.
Explain the hiring use before collection.
Production needs a reviewed lawful-purpose and necessity decision. This demo makes no legal determination.
Private, anonymised or paused—never silently public.
Deletion intent is separate from visibility and fails closed by removing the fixture from results.
Name the trigger, owner and deletion evidence.
The demo persists only synthetic local state. Production periods remain unapproved and unimplemented.
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.
DPO, counsel, engineering or GRC?
Separate authority, legal interpretation, technical implementation and assurance.
02 · BriefingWrite a serious privacy job description.
Define decisions, interfaces, evidence and escalation—not vague compliance promises.
03 · InterviewingUse a consistent, privacy-aware scorecard.
Evaluate work samples without demanding confidential employer material.
04 · Candidate dignityBuild portfolio evidence safely.
Use invented or anonymised scenarios rather than real people or internal records.
Provision-aware legal status
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.