Web analytics, cookies, tag managers, CMPs, ad pixels, and session-replay tools as deployed on websites and apps targeting Colombia. Sectoral rules (financial via SFC, healthcare, telecoms via CRC) are touched only where they intersect with the analytics layer.
National addons
Country-specific statutes layered on the EU baseline.
- Art 4 Processing principles — legality, purpose, freedom, truthfulness, transparency, restricted access, security, confidentiality
- Art 8 Data-subject rights — access, rectification, deletion, revocation of authorization, complaint to SIC
- Art 9 Prior and informed authorization — opt-in consent baseline; tacit/silent consent invalid
- Art 17 Controller duties — including registration of databases with the SIC (RNBD)
- Art 25 Habeas data complaints procedure with the SIC
- Art 26 International transfers — prohibited unless destination country provides adequate protection or one of seven exceptions applies
- Art 5 Form of authorization — written, oral, or unequivocal conduct; controller bears burden of proof
- Art 7 Children and adolescents — processing must respect best interests and fundamental rights; parental consent required for under-18 minors
- Art 10 Privacy notice — minimum content (controller identity, processing purposes, rights, channels)
- Art 13 Internal Policy for Personal Data Handling (PTI) — mandatory written policy
- Art 25 Data-subject request handling — 10-business-day response window for queries; 15 for claims
- Sec II Adequacy list — countries deemed to provide adequate protection
- Sec III Contractual safeguards — required clauses for transfers to non-adequate destinations
- Sec IV Prior declaration to SIC — controllers must declare transfers to non-adequate countries
Regulators
Supervisory authorities that interpret and enforce privacy law here.
Coordination body
- 2018-08-09 · RNBD scope reform — Decree 090 of 2018 limited mandatory RNBD registration to controllers that are legal entities of a private nature with assets above 100,000 UVT, and to all public-sector legal entities.
- 2020-12 · COVID-19 contact-tracing — SIC issued guidance restricting employer use of CoronApp data and reaffirming opt-in baseline for any health-status processing.
- 2024-03 · Cookies and trackers — SIC reiterated that browser-based trackers fall under Law 1581 — Spanish-language banner, prior authorization for non-strictly-necessary cookies, and registration of analytics databases in the RNBD.
Notable enforcement
The SIC has emerged as one of Latin America's most active data-protection regulators. Multi-million-peso fines are imposed multiple times per year, and the regulator has shown willingness to pursue large banks, airlines, breweries, and telecoms. Colombian sanctions are calculated in monthly minimum legal wages (SMLMV) up to a statutory cap of 2,000 SMLMV per infraction (~COP 2.85 billion / ~USD 700K in 2026). The SIC publishes sanctions on its website, creating reputational pressure beyond the headline amount. Notable targets in recent years include Banco Davivienda (COP 1.165B, 2023), Avianca, Bavaria (the AB-InBev subsidiary), and major telecom operators.
-
Banco Davivienda SIC · Law 1581 Art 4, 17 stood
Multiple sanctions totalling approximately COP 1.165 billion for security failures, unauthorized data sharing, and inadequate response to data-subject requests. One of the largest single SIC sanctions to date.
-
Claro Colombia SIC · Law 1581 Art 4, 8 stood
Sanction for security failures resulting in customer-data exposure and inadequate breach-response procedures.
-
Avianca SIC · Law 1581 Art 17 stood
Sanction for inadequate handling of habeas data complaints from passengers — failure to respond within statutory windows and to keep RNBD registration current.
-
Bavaria S.A. SIC · Law 1581 Art 9 stood
Sanction for processing marketing data without prior, informed authorization — pre-checked consent boxes invalid under Law 1581 Art 9.
-
Rappi SIC · Law 1581 Art 9, 17 stood
Sanction for opt-in deficiencies in marketing communications and incomplete RNBD registration of customer databases.
GA4 status
GA4 is usable in Colombia only with prior, express, informed authorization (opt-in) under Law 1581 Art 9. Tacit or silent consent — including pre-ticked boxes or 'continued browsing implies acceptance' banners — is invalid. The privacy notice must be in Spanish, and the analytics database must be registered in the RNBD where the controller meets the registration threshold. Transfers to Google's US servers fall under Law 1581 Art 26 — the US is not on the SIC adequacy list, so contractual safeguards or specific data-subject consent are required.
| DPA | Stance |
|---|---|
| SIC | Cookies and analytics fall under Law 1581 (2024 guidance). Opt-in baseline + Spanish-language banner + RNBD registration where threshold met. US transfers require contractual safeguards under Circular 002. |
Cross-border transfers + Schrems II
Colombia is not in the EU's adequacy list and is not a DPF participant. Under Law 1581 Art 26 + SIC Circular 002 of 2015, international transfers require either (a) destination on the SIC adequacy list — currently includes EU member states, UK, Argentina, Israel, and a small group of others; (b) standard-contractual safeguards with the importer; (c) BCRs; (d) specific data-subject consent for the transfer; or (e) one of the narrow exceptions (medical urgency, banking/stock-exchange transfers, treaty obligations). Transfers to non-listed destinations require prior declaration to the SIC.
Colombia has no published official SCC template — the SIC accepts contractual safeguards drafted around Circular 002's required clauses. EU SCCs (2021/914) are commonly adopted as a baseline by multinational controllers; the SIC has accepted them in practice but does not formally endorse a template.
Employee data
Key thresholds
Vendor signals
Red / yellow / green markers are an editorial reading of public regulator guidance and published enforcement actions, applied to vendor behavior we can observe or that the vendor documents. They are not legal conclusions, not endorsements, and not advice about your specific processing. Configuration changes the picture — a "yellow" vendor in one configuration may be defensible in another.
Analytics tools · 4 · 0 green · 3 yellow · 1 red
| Vendor | Status | Rationale |
|---|---|---|
| YELLOW | Visitor ID cookie + cross-suite stitching with Experience Platform. DPIA strongly recommended; configure ECID + IP obfuscation. | |
| YELLOW | EU residency available on paid plans; default cloud is US. Persistent user IDs require config + DPA + DPF chain. | |
| YELLOW | EU cloud helps but session recording + autocapture default to PII collection. Disable autocapture and recordings or self-host for green. | |
| RED | Auto-capture grabs every click and form value — broad PII risk under GDPR Art 5(1)(c) data minimization. |
Consent management platforms · 5 · 5 green · 0 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | Danish-based, EU-hosted. Auto-blocks third-party scripts pre-consent — verify your manual scripts also gate. | |
| GREEN | Italian-based, EU-hosted. Free tier limits 5k pageviews/mo; granular per-vendor controls require paid plan. | |
| GREEN | Open-source, self-hosted. No managed updates — site owner maintains vendor list. | |
| GREEN | GDPR + CCPA + multi-region templates available. Common config error: GDPR/CCPA mode mismatch — verify per-region defaults. | |
| GREEN | German-based, EU-hosted. v3 SDK required for Consent Mode v2; TCF flow can over-collect for non-AdTech sites. |
Ad pixels · 3 · 0 green · 0 yellow · 3 red
| Vendor | Status | Rationale |
|---|---|---|
| RED | Loads pre-consent if naively placed; cross-device matching broad. Block until consent + IAB TCF string set. | |
| RED | Schrems II concerns persist; advanced matching hashes PII but does not fix EU→US transfer problem. | |
| RED | PRC-parent ownership flagged by Italian Garante and EDPB; transfers to China contested. Consent + risk acknowledgement required. |
Server-side · 3 · 2 green · 1 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | EU-only datacenters strong for FR/DE compliance; per-event pricing scales steeply at high traffic. | |
| GREEN | EU server containers handle the routing — but server-side tagging does NOT auto-fix consent. CMP must still gate browser-side pings. | |
| YELLOW | "EU server" ≠ EU data — clients still transmit to Google ad backends downstream. Use only for Google-ecosystem first-party-routing. |
Compare with neighbors
Side-by-side rule comparison.
Common questions
Is Google Analytics legal in Colombia in 2026?
Is habeas data really a constitutional right in Colombia?
Do I need to register my database with the SIC (RNBD)?
What language must my privacy notice be in?
Is 'legitimate interest' a valid basis for analytics in Colombia?
Do I need a Colombian Encargado / DPO?
Do I need a Colombian representative if I'm based abroad?
What about international transfers — what are the rules?
What's the parental-consent age for processing children's data?
How active is SIC enforcement?
// EDITORIAL · NOT LEGAL ADVICE This page summarises Colombia's privacy framework as of 2026-05-05. Rules vary by sector, establishment, and DPA position. For binding interpretation, consult counsel admitted here.