Manatoko DPDP
This site is password-protected.
This site is password-protected.
Every platform currently re-verifies the same workers independently — creating redundant PII, multiplied breach risk, and compounded Section 8(1) liability. Manatoko DPDP is a workflow solution that eliminates this: agents redesign your worker onboarding workflow, Manatoko VC issues portable credentials to workers, and any platform verifies instantly without taking PII custody.
Enforcement begins May 2027. DPDP Rules notified November 2025.
The DPDP Act 2023 applies to any organisation that processes digital personal data of Indian residents — including gig workers on quick-commerce platforms. The Rules were notified 13 November 2025. Core obligations become enforceable May 2027 — with no grace period on penalties from Day 1.
For quick-commerce platforms, the most significant obligations are: Section 6 (consent must be free — structurally difficult for gig workers whose livelihoods depend on acceptance), Section 8(1) (absolute liability for ID verification agency failures, no contractual escape), and data minimisation (platforms hold far more worker PII than necessary across multiple re-verification cycles).
The Labour Code 2025 adds a new dimension: effective November 2025, platforms must register workers on eShram. eShram creates a portable government-verified worker identity that Manatoko VC extends — a credential issued against an eShram-verified identity is portable across any Manatoko-integrated platform.
Conventional worker onboarding at every quick-commerce platform starts from the same assumption: the platform must collect Aadhaar, PAN, driving licence, vehicle registration, and background check results directly — and retain them, share them with an ID verification agency, and manage them across the worker's tenure. Each platform does this independently. Zomato, Swiggy, and Blinkit each hold the same Arjun Mehta's complete identity file.
Manatoko DPDP starts from a different premise. The platform does not need the underlying data. It needs verification of the worker's identity, licence, vehicle, and background. A portable credential in the worker's own wallet delivers exactly that — verification result, not raw PII. Three platforms benefit from one verification event. Zero redundant PII custody.
The worker's Aadhaar AVC, driving licence (Sarathi API), vehicle registration, and background verification are processed transiently by Manatoko's Credential Agent — verified in 4.2 seconds, deleted immediately. No platform holds the raw documents. No ID agency is in the data custody chain.
KYC Verified · Driving Licence Valid · Vehicle Registered · Background Cleared · Food Handler Certified — each as a separate verifiable credential in the worker's self-custodied wallet. The worker owns them. No platform holds a copy. The worker can present them to any Manatoko-integrated platform.
Zomato verifies by requesting a credential presentation from the worker's wallet. Swiggy does the same. Blinkit does the same. Each receives a verification result — not the Aadhaar number, PAN, or vehicle documents. One verification event. Three platforms. Zero redundant PII custody.
Section 6 consent is structurally coerced for gig workers — no technical architecture makes consent truly free when work depends on it. Manatoko DPDP reduces the data subject to that coercion but does not resolve the legal tension. Regulatory guidance on gig worker consent is still evolving. Manatoko DPDP will refer you to DPDP-qualified Indian privacy law firms for guidance on Section 6, the VC data custody architecture, and intersection with Labour Code 2025 obligations.
The Ingestion Agent processes all submitted documents — existing onboarding policies, ID agency contracts, platform DPAs, worker consent notices, current verification SOPs. It classifies, indexes, and prepares them for assessment of your current worker data flows.
Maps every operational workflow touching worker and customer personal data. Specifically identifies: worker onboarding PII flows, ID agency processor relationships and their Section 8(1) exposure, customer data practices (location, payment, order history), and which worker verification workflows qualify for VC-based elimination.
Designs target-state worker onboarding workflows — eliminating unnecessary PII custody, redesigning ID agency DPA relationships, and producing the credential schema for portable worker credentials. Every redesign is presented for your team’s approval before implementation begins.
Executes the remediation work. The Credential Agent deploys Manatoko VC for qualifying worker verification workflows — issuing five portable credentials to each worker's self-custodied wallet, registering validation events on-chain, and enabling any Manatoko-integrated platform to verify instantly without PII custody.
Assembles the worker onboarding workflow redesign documentation, ID agency DPA audits and processor attestation credentials, evidence of credential deployment for qualifying verification workflows, customer consent redesign records, and a residual-risk register. Structured for presentation to DPDP Board inspectors, auditors, or the board.
Complete assessment of every workflow touching worker and customer personal data — onboarding, ID agency relationships, location tracking, payment data — with gap register and Section 8(1) risk mapping.
Visual map of where worker personal data sits across your platform — collection, storage, retention, sharing risk — and which workflows qualify for full data custody elimination via Manatoko VC.
Target-state worker onboarding flows — credential-based verification replacing PII collection, ID agency DPAs executed, processor attestation credentials issued to agency wallets.
Regulator-ready documentation: worker consent records, ID agency DPA audits, credential deployment evidence, worker onboarding redesign documentation, on-chain audit trail — structured for DPDP Board inspectors.
Board-level summary with readiness scorecard, domain assessments, residual risk register, and documented Section 8(1) liability position for leadership sign-off.
Defensible, evidence-backed statement of baseline readiness — with referral to DPDP-qualified Indian privacy law firms for legal review including gig worker consent, VC architecture, and Labour Code 2025 obligations.
Zomato, Swiggy, Blinkit, Zepto, Porter and equivalent platforms. Section 8(1) exposure through outsourced KYC. Redundant PII across independent re-verifications. Manatoko DPDP redesigns the onboarding workflow and deploys portable worker credentials.
Agencies serving multiple platforms — SafeCheck, AuthBridge equivalents. Your DPDP readiness determines your platform clients' Section 8(1) liability. Processor attestation credential is the primary output. Agents identify and address your exposure on behalf of all clients you serve.
Platforms managing large worker fleets with complex multi-channel verification requirements. Agents compress weeks of assessment, redesign, and credential deployment into days. Network effect: every worker credentialed on your platform becomes instantly verifiable by any Manatoko-integrated platform.
Agents do the work. Wallets hold the data. Humans make the decisions.
The section above describes what Manatoko DPDP for Quick-Commerce does. The demo below shows it — including the point in the workflow where Manatoko VC is deployed so three platforms verify the same worker credential, zero PII collected by any of them.
Enter your work email to unlock the interactive walkthrough. No password. No sales call.
Yes. Any platform that processes digital personal data of Indian residents — including gig workers — is a Data Fiduciary. Zomato, Swiggy, Blinkit, Zepto, Porter, and equivalent platforms are all covered.
For quick-commerce platforms, the most significant obligations are: Section 6 (consent must be free — structurally difficult for gig workers), Section 8(1) (absolute liability for ID verification agency failures), and data minimisation (platforms hold far more worker PII than necessary).
Yes. Section 8(1) makes your platform absolutely liable for any processor failure — no contractual escape. If your ID verification agency is breached, your platform faces the DPDP penalty for the workers' data the agency held on your behalf.
Manatoko DPDP's Governance Redesign Agent restructures the onboarding workflow so the platform receives a verification result rather than raw worker data. If the platform never holds the raw data, it is not in the data custody chain for the verification step — and the Section 8(1) exposure for that workflow is eliminated.
Section 6 requires consent to be free, specific, informed, and unambiguous. Consent given as a condition of accessing a livelihood is not free in any meaningful sense. This is a genuine structural tension in the law as it applies to gig platforms. Manatoko DPDP will refer you to DPDP-qualified Indian privacy law firms for guidance.
What the Manatoko workflow achieves is reducing the scope of consent required: if the platform receives a credential confirmation rather than Aadhaar and PAN, less PII is collected — and less needs to be consented to.
The Social Security Code 2025, effective November 2025, requires platforms to register workers on eShram. eShram registration creates a government-verified worker identity that is portable across platforms — exactly the model Manatoko VC extends.
A credential issued against an eShram-verified identity is portable to any Manatoko-integrated platform. The Social Security Fund contribution record can itself be a verifiable credential, giving workers proof of entitlement without the platform holding that record.
A 90-day baseline readiness program executed through autonomous AI agents. The agents assess your current worker onboarding and data practices, redesign the onboarding workflow to eliminate unnecessary PII custody, deploy Manatoko VC to issue portable worker credentials, and assemble an evidence pack.
It is not a consulting engagement. Agents execute. Your team governs the decisions.
A current-state diagnosis of every workflow touching worker and customer personal data. For quick-commerce, the Assessment Agent specifically maps: worker onboarding PII flows, ID agency processor relationships and their Section 8(1) exposure, customer data practices (location, payment, order history), and which worker verification workflows qualify for VC-based elimination.
Worker onboarding workflow redesign documentation, ID agency DPA audits and processor attestation credentials, evidence of credential deployment for qualifying worker verification workflows, customer consent redesign records, and a residual-risk register. Structured for presentation to DPDP Board inspectors, auditors, or the board.
Five verifiable credentials in the worker's wallet: KYC Verified, Driving Licence Valid, Vehicle Registered, Background Cleared, Food Handler Certified. Each contains the verification outcome — not the underlying Aadhaar number, PAN, vehicle registration number, or address. The platform receives a presentation result, not a data dump.
Yes — this is the core design intent for quick-commerce. A worker verified by Manatoko receives credentials in their wallet. Any Manatoko-integrated platform verifies in seconds without re-collecting documents. The worker onboards to a second platform in minutes, not days.
For platforms, this creates a network effect: every worker verified by any Manatoko-integrated platform is already verifiable by yours. Worker acquisition friction drops significantly.
The on-chain validation record supports re-issuance of credentials to a new device following appropriate re-verification. The specific recovery workflow is defined during the governance redesign phase of the engagement.
In the current model, a platform blocks a worker by suspending their account — no explanation required, no audit trail. With Manatoko VC, revocation is logged on-chain with a timestamp and reason code. The worker retains their base credentials; the platform documents why access was withdrawn.
This does not prevent platforms from blocking workers. It makes blocking auditable — defensible to regulators and courts rather than arbitrary.
Five specialised agents execute the program. Ingestion Agent processes submitted documents. Assessment Agent maps worker and customer data workflows and identifies gaps. Governance Redesign Agent designs target-state onboarding workflows. Implementation Orchestration Agent sequences and tracks remediation. Credential Agent deploys Manatoko VC and issues portable worker credentials.
Every output is traceable to a source document. Agents log reasoning chains for auditability. Agents do not make legal conclusions — they flag legal questions for your team.
A decision gate is a structured pause where the agent presents its outputs for your team's review. Primary gates: after assessment (your team approves the gap register before redesign begins) and after redesign (your team approves target-state onboarding designs before credential deployment begins).
At each gate your team can approve, request changes, or reject the output. The agent does not proceed without explicit approval.
Manatoko DPDP can be delivered through a channel partner — a virtual DPO firm or a compliance federation — that provides the human governance layer. The agents execute the program; the partner provides oversight your platform cannot maintain internally.
Currently your platform — or your ID agency — holds Aadhaar numbers, PAN details, vehicle documents, and address information for every worker. This is the breach surface. This is the Section 8(1) exposure.
After Manatoko VC is deployed for the onboarding workflow, your platform receives a verification confirmation — 'KYC verified, licence valid, vehicle registered, background cleared.' Not the Aadhaar number. Not the PAN. Not the address. For that workflow, you have left the data custody chain.
Five amber-light credential cards in their self-custodied wallet. Each card shows the credential type, issuer (Manatoko DPDP), valid-until date, and which platforms have verified it. The worker can see their own verified status. They can share it with a new platform in seconds.
This is the first time in India's gig economy that a worker's verified identity belongs to them — not to the platform that verified them.
A verification result: 'Arjun Mehta — KYC Verified · Licence Valid · Vehicle Registered · Background Cleared · Food Handler Certified — Valid until April 2027.' No Aadhaar number. No PAN. No address. No raw documents.
For that onboarding workflow, the platform is not a data fiduciary for the collection step. Section 8(1) exposure for that workflow is eliminated.
The Governance Redesign Agent designs the credential schema so it is interoperable across Manatoko-integrated platforms. Worker credentials issued by any platform's Manatoko deployment are verifiable by any other. Amberoon coordinates the schema standardisation across platform partners.
Yes. Credential issuance is a stateless, parallelisable operation. Credential presentation verification runs in under one second. The Credential Agent processes worker verifications at platform scale.
The practical migration question is transitioning existing verified workers. Manatoko designs a phased approach: new workers credential-first, existing workers credentialed at next re-verification cycle.
Document quality is handled at the verification step. Manatoko verifies against source authorities — Aadhaar AVC for identity, Sarathi for driving licence, vehicle registration APIs for vehicle documents. If a document cannot be verified, a credential is not issued for that element. The worker receives a partial credential with clear indication of what is verified and what is pending.
This is an improvement over current practice: platforms often accept unverified documents under onboarding pressure and deal with quality issues later. Credential issuance enforces verification upfront.
Yes. The Assessment Agent maps your background verification workflow. The Governance Redesign Agent designs an integration: the background check is conducted by your existing agency, the result is communicated to Manatoko's Credential Agent, and a 'Background Cleared' credential is issued to the worker's wallet. Your agency remains in the verification chain; the raw result is not stored by the platform.
No. Manatoko DPDP produces a defensible, evidence-backed baseline readiness position. Not a government certification.
Section 6 consent for gig workers remains structurally problematic — Manatoko reduces the scope of PII collected but does not resolve the coercion issue.
Three legal questions about the VC architecture require a formal opinion before the first pilot. Manatoko DPDP will refer you to DPDP-qualified Indian privacy law firms.
Platform network effects depend on cross-platform adoption. A credential issued by Manatoko is most valuable when multiple platforms accept it. Amberoon is building the platform partner network — confirm the current state before piloting.
See the worker onboarding workflow — one verification, three platforms, zero redundant PII custody. Enter your work email to unlock.
“DPDP compliance is a workflow problem. Agents solve it.”
“Agents do the work. Wallets hold the data. Humans make the decisions.”
“One verification. Three platforms. Zero redundant PII.”