India DPDP
Prepare for phased Indian digital personal data obligations with a dated implementation plan.
Personal Information Protection Act · Republic of Korea
Translate Korean privacy requirements into a data inventory, rights process and incident plan.
Controllers processing personal information within PIPA scope, including some overseas organizations serving Korean users.
Documented collection and transfer decisions, rights handling and breach readiness.
Use the current Korean Act and Enforcement Decree for thresholds, exemptions and overseas transfer 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.
South Korea PIPA 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 Determine role and collect a processing inventory · Privacy lead + local 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.
The Enforcement Decree applies the authority reporting window to specified leakage cases. Confirm the trigger and notice duties under the current rules.
Official reference (opens in a new tab)Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Determine role and collect a processing inventory | Privacy lead + local counsel | At initiation | Set a start date | Scope memo; Processing inventory; Accountability map | Open |
| Implement lawful processing and rights | Legal + product | Before collection and on request | Set a start date | Privacy policy; Consent records; Rights workflow | Open |
| Control outsourcing, transfers and destruction | Vendor lead + security | Before outsourcing or transferring | Set a start date | Outsourcing register; Transfer decision; Destruction records | Open |
| Escalate and assess breaches | Incident response + privacy lead | On awareness of a qualifying breach | Set a start date | Incident log; Regulator report; Notice 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.
Map purposes, categories, sources, systems and recipients. Determine controller roles and any domestic representative or privacy officer duties.
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.
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.
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.
Identify grounds, set notices and consent where required, and implement access, correction, deletion and suspension procedures where applicable.
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 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.
Document processor terms and oversight, evaluate overseas transfer conditions and test data deletion schedules and safeguards.
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.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
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.
Classify affected persons and data, apply the statutory reporting and notice thresholds and preserve decisions and communications.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.