Start hereMap databases and register where needed
~77 days leftOpen step
Guide library
Regulation Latin America

Colombia data protection

Ley 1581 de 2012, implementing rules and SIC instructions

Set up authorization, data-subject requests and the applicable RNBD and security incident duties.

Who it applies to

Controllers and processors falling within the Colombian general personal data regime, subject to exclusions and special regimes.

What you’ll produce

Documented authorization and handling, registration decisions and records for complaints, requests and incidents.

Check the current RNBD registration criteria and the correct incident-reporting route. Registration scope and duties to report are separate questions.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the 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.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Colombia data protection 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 databases and register where needed · 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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which databases fall within the general regime and meet current RNBD criteria?
  • Who can show the authorization, grounds or exception for each purpose involving customer data?

Worked scenario

A retailer lets a delivery partner see addresses but also wants to share them with an advertising partner. The privacy owner evaluates each disclosure separately, records its justification and updates authorization wording and downstream instructions as needed.

What to read next

  • Mexico LFPDPPP

    Review different private-sector rules for similar Spanish-language operations.

The whole journeyabout 77 days across 4 steps
  1. 01Map databases and register where neededPrivacy lead + local counsel · ~14 days
  2. 02Document authorization and noticesLegal + product · ~21 days
  3. 03Review transfer and transmission arrangementsVendor management + legal · ~28 days
  4. 04Keep a case timeline and report what appliesSecurity + privacy operations · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 10 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map databases and register where neededPrivacy lead + local counselBefore covered processing and periodic updatesSet a start dateProcessing inventory; Coverage memoOpen
Document authorization and noticesLegal + productBefore collectionSet a start dateConsent evidence; Privacy notices; Rights workflowOpen
Review transfer and transmission arrangementsVendor management + legalBefore handing data to a providerSet a start dateTransfer assessments; Processor agreementsOpen
Keep a case timeline and report what appliesSecurity + privacy operationsAt an inquiry, complaint or security incidentSet a start dateIncident assessment; Request log; Notification recordOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map databases and register where needed

    Who Privacy lead + local counsel When Before covered processing and periodic updates

    Identify controllers, processors, databases and purposes. Record the SIC registration decision and retain the applicable filings and receipts.

    What to produce

    Processing inventorySpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    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.

    Coverage memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    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.

  2. 02

    Document authorization and notices

    Who Legal + product When Before collection

    Check authorization requirements and exceptions. Keep verifiable proof and publish the procedures for people to find their rights and exercise them.

    What to produce

    Consent evidenceSpreadsheet

    Gather first

    • Approved consent language and purpose IDs
    • User interface or paper form
    • Audit event and withdrawal behavior

    How to prepare it

    1. Record the exact consent version, the purpose, the decision and its timestamp. Link to the interface or form shown to the person.
    2. Use an internal reference to the person or parent. Limit access and avoid placing underlying identity documents in the log.
    3. Exercise refusal and withdrawal. Verify that each downstream system stops relying on consent when required, and record the result.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Subject reference
    Account reference C-018
    Purpose and notice version
    Optional product updates, notice v4
    Decision and timestamp
    Opted in, 2026-11-02 14:12 UTC
    Capture channel
    Account preferences, unchecked by default
    Withdrawal and effect
    2026-11-12, active list updated, ticket P-123

    Check before handing it over

    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.

    Privacy noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    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.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    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.

  3. 03

    Review transfer and transmission arrangements

    Who Vendor management + legal When Before handing data to a provider

    Analyze whether each arrangement is a transfer or transmission and whether it is international. Record the controlling agreement, safeguards and responsibility.

    What to produce

    Transfer assessmentsSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    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.

    Processor agreementsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    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.

  4. 04

    Keep a case timeline and report what applies

    Who Security + privacy operations When At an inquiry, complaint or security incident

    Record case dates, role, classification and delivery. Check the SIC reporting requirement and the current submission channel for the incident.

    What to produce

    Incident assessmentSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    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.

    Request logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    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.

    Notification recordSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes