How to implement a personal data governance program in a large Chilean company
A personal data governance program is the structure that makes compliance happen every day and not only when an audit arrives. It has four minimum components: roles with assigned responsibility, a record of processing activities that is kept up to date, common policies for all areas and periodic reporting to management. In a large organization it is not implemented all at once. It is implemented in stages, starting with the processes that concentrate the most risk.
Why a large company cannot solve it area by area
In an organization with twenty management units, each area contracts its own software, requests its own data and chooses its own vendors. The result is the same personal data processed under different criteria in several places at once.
Law 21.719 does not look at areas. It looks at the organization as the data controller. Without governance, each management unit is a separate exposure and no one has the full picture.
What the law says about compliance programs
Law 21.719 provides for an infringement prevention model that organizations may adopt voluntarily and that the Personal Data Protection Agency can certify. The regulation that sets the requirements to implement, certify, register and supervise those models is Supreme Decree No. 662 of the Ministry of Finance, published in the Official Gazette on September 9, 2026.
In practice, a well-built governance program is the foundation of that model. The difference is that the certified model requires being able to demonstrate it.
The components of the program
1. Mandate and roles. The board or the risk committee sponsors the program. The data protection officer, or whoever fulfills that role, coordinates it. Each management unit has a data owner with a first and last name. Without an owner there is no control.
2. Record of processing activities. What data is processed, for what purpose, on what lawful basis, in which systems and with which vendors. It is the foundation: without it, risks cannot be prioritized nor can a data subject be answered. More in Record of processing activities (RAT): why do it if it is not mandatory?.
3. Policies and standards. A corporate policy and standards that all areas reuse: how consent is requested, how a privacy notice is drafted, how a vendor is assessed, how a rights request is answered.
4. Operational fronts. Consent in the channels, cookies on the website, data subject rights, security breaches and vendors. Each front with its procedure and its evidence.
5. Metrics and reporting. Processing activities mapped, consents with evidence, requests answered within the deadline, incidents and vendors assessed.
6. Training. Operational judgment for those who design products and contract vendors, rather than an annual course.
How it is implemented in the first year
Quarter 1: diagnosis. Map processing activities and systems, and identify the highest-risk processes and the most evident gaps.
Quarter 2: foundation. Approved policy, designated roles, record of processing activities in operation and consent and privacy notice templates.
Quarter 3: highest-exposure fronts. Digital channels with traceable consent, website with cookie management and an open rights channel.
Quarter 4: evidence and reporting. First formal report to the committee or the board, with declared gaps and a plan for the following year.
How to report to the board
A useful report does not list activities. It shows exposure and progress:
Critical processing activities identified and how many have a documented lawful basis.
Percentage of consents with verifiable evidence.
Rights requests received, answered and overdue.
Incidents during the period and the status of controls.
Relevant vendors assessed.
If the report does not fit on one page, it is still an activities report. On the role of the board, see Data privacy: the new strategic challenge for boards and CEOs.
How Soyio solves it
The bottleneck of a governance program is almost always the same: the record of processing activities. Mapping it by hand across twenty management units takes months, and by the time it is finished it is already outdated.
Prisma IA solves that point. It builds the record by conversing with each area in natural language, leaves the lawful basis of each processing activity documented and keeps it alive when processes change. A Chilean financial group documented more than 800 processing activities across 26 management units this way, with a single standard for the whole group and an average of 10 to 15 minutes per processing activity. With the record solved, the rest of the program has something to build on.
On that foundation, Consent provides a single standard for all the group's channels and brands, cookie management orders the website front and the Rights Manager concentrates data subject requests and their deadlines in a single inbox.
Soyio is a Chilean technology company for privacy and personal data governance, with ISO 27001 and ISO 27701 certifications.
A privacy program is measured by what it can demonstrate, not by what it declares.
Frequently asked questions
What is a personal data governance program?
It is the set of roles, policies, processes and metrics that make compliance with the data law happen sustainably across the entire organization, with assigned responsibility and available evidence.
How long does it take to implement it in a large company?
The plan in this article is organized into four quarters, that is, about one year. What should not be postponed is the record of processing activities, because without it no prioritization is possible.
Who should lead the program?
A data protection officer or privacy officer, with a mandate from the risk committee or the board. If the program depends only on the legal area, it does not reach the areas that process the data.
How does it relate to Law 21.719?
The law establishes enforceable obligations, an Agency that supervises and an infringement prevention model that can be certified. The program is the way to comply with those obligations demonstrably.
When does Law 21.719 enter into force?
On October 15, 2027. The original date was December 1, 2026, and in November 2026 Congress approved postponing it (bulletin 18.623-07). With a staged plan like the one in this article, of about one year, the margin left by the postponement is already tight.
Where do I start if I have nothing?
With the record of processing activities and with the two or three highest-risk processes, which in a large organization tend to be digital channels, marketing and vendors.