Singapore PDPA
Set up accountability, individual rights and a workable breach-notification process.
Digital Personal Data Protection Act 2023 and Rules 2025
Prepare for phased Indian digital personal data obligations with a dated implementation plan.
Data Fiduciaries and other parties processing covered digital personal data in India, or in connection with offering goods or services to people in India.
Phased operational readiness for notices, individual rights, safeguards and breach response.
Check MeitY’s notifications and corrigendum. Significant Data Fiduciaries and processing involving children can have additional requirements.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
India DPDP kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Map digital data and commencement dates · Privacy counsel [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Confirm the exact operative date and applicability against the Gazette and corrigendum.
Official reference (opens in a new tab)Includes Rules 3, 5–16, 22 and 23. Check the Act’s separate commencement notice.
Official reference (opens in a new tab)Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map digital data and commencement dates | Privacy counsel | Before assigning implementation dates | Set a start date | Scope memo; Phased legal register | Open |
| Design notices and consent flows | Product + legal | Before applicable commencement | Set a start date | Notices; Consent records; Youth safeguards | Open |
| Implement rights and processor oversight | Privacy operations + vendor lead | Before applicable commencement | Set a start date | Rights runbook; Processor register; Retention schedule | Open |
| Build safeguards and reporting | Security + privacy lead | Before applicable commencement and at incident | Set a start date | Security evidence; Incident runbook; Exercise record | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify covered digital data and territorial triggers. Map the separate Rules and Act schedules to the obligations tracker.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Map processing to consent or specified legitimate uses. Design clear notices, withdrawal, and age or parental checks where required.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
You can demonstrate what the person saw, how they acted and how the decision was honored.
Provide the consent log and tested withdrawal flow to privacy operations and downstream system owners.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Establish grievance and rights intake, nomination workflows, retention rules and contractual safeguards for processors.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A system operator can apply the rule and show evidence of deletion, exception or hold.
Send authorized rules to system and vendor owners and file the verified disposition evidence.
Test detection, access safeguards and escalation. Prepare notifications for the Board and affected individuals under the applicable rules.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.