Colombia data protection
Set up authorization, data-subject requests and the applicable RNBD and security incident duties.
Law 21.719 and Chile’s reformed personal data protection regime
Prepare for the new Chilean data protection rules and document which duties are already in effect.
Persons or organizations processing personal data under the reformed Chilean law, including covered activities affecting people in Chile from abroad.
A change plan for controller obligations, rights, sensitive data safeguards and international transfers.
Map the cutover by activity. Keep current-law duties in operation while tracking the new law and implementing instruments separately.
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.
Chile Law 21.719 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 Create a cutover register · Privacy counsel + local operations [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.
A ticketing company inventories data from existing accounts before December 2026. Its owners review the legal grounds for ongoing use, test request intake in Spanish and update supplier clauses before the reformed obligations take effect.
Compare the legal-basis and breach workflows for a second Latin American market.
Confirm the law’s transitional provisions and any applicable implementing rules before setting a project release date.
Official reference (opens in a new tab)Checklist, instructions and 10 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Create a cutover register | Privacy counsel + local operations | Before the general entry into force | Set a start date | Phased legal register; Processing inventory | Open |
| Update processing grounds and rights | Product + privacy operations | Before the applicable legal change | Set a start date | Lawful-basis register; Privacy notices; Rights workflow | Open |
| Review risks and disclosures | Risk lead + procurement | Before new processing or transfers | Set a start date | Impact assessments; Transfer register; Supplier terms | Open |
| Rehearse the security response | Incident response + privacy lead | Before launch and whenever rules change | Set a start date | Incident playbook; 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.
Cross-reference business processes against current and incoming obligations. Identify the new rights, agency-facing duties and gaps that need product work.
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.
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.
Document grounds, prepare notices and test applicable access, rectification, deletion, opposition, portability and other rights.
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 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.
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.
Check the law’s impact-assessment triggers, treatment for sensitive data, requirements for recipients and the conditions for international transfers.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
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.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Record security safeguards, choose how to escalate incidents and verify what the relevant authority and affected people must receive.
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.