
Law 21.719 Implementation Guide
Important: This guide is for informational purposes and provides an overview of the main tasks that typically need to be performed to adapt a website to Law No. 21.719 on Personal Data Protection. The specific implementation will depend on the type of business, the website, the data processed, and the systems used.1. Run an initial website audit
Before modifying any aspect of the site, it is essential to identify what personal data the company collects. The audit should answer, among others, the following questions: What forms exist? What personal data is requested? Where is it stored? Who has access? Is it sent via email? Are there integrations with CRM? Are marketing tools used? Is Google Analytics employed? Is Meta Pixel used? Are AI tools utilized? Are cookies stored? Is data transferred outside of Chile? Are there plugins that collect information? Without an audit, it is very difficult to determine the actual level of compliance.2. Prepare the Record of Processing Activities (RoPA)
Based on the audit, it is necessary to create a formal inventory of all personal data processing activities carried out by the company. This inventory is what the law recognizes as the Record of Processing Activities (RAT), and it is the document that the Personal Data Protection Agency reviews first during any inspection. For example, each of the following constitutes a distinct data processing activity and must be recorded: Contact forms. Quotation forms. Ecommerce. Customer registration. Newsletter. WhatsApp Business. CRM. Chatbots. Reservations. Scheduling. Technical support. Payment systems. Comments. Surveys. For each processing activity, the RAT must record: what data is collected, for what purpose, where it is stored, who has access, if it is transferred to third parties, and for how long it is retained. It does not need to be a public document; it must exist, be kept up to date, and be available if requested by the authority.3. Review the server infrastructure
It must be verified that the server has the minimum necessary security measures to protect personal information and reduce the risk of unauthorized access. Valid SSL certificate. Updated PHP versions. Updated operating system. Firewall. Malware protection. Automatic backups. Server monitoring. Access and permission control. Protection against brute force attacks. Security header configuration (HTTP Security Headers). Update and maintenance policies. At Estudio Ideas, all managed hosting services and the servers we manage for our clients consider these security measures as part of our operation and maintenance policy. Our team performs continuous monitoring, periodic updates, automatic backups, and applies best practices in cybersecurity.4. Set up Cloudflare
In some cases, it may be essential to incorporate Cloudflare as an additional layer of security and perimeter protection for the website, especially when the system is integrated with critical platforms such as CRM, ecommerce, or tools that process sensitive personal data, and there is direct exposure to public traffic or automated attack attempts. An appropriate configuration may include: Protected DNS. Firewall (WAF). DDoS attack protection. Bot protection. Security rules. Limiting access attempts. Protection of administrative pages. HTTPS optimization. Security headers. Cloudflare does not replace server security measures but complements them.5. Implement Cloudflare Turnstile
All public forms should be protected against spam and automated attacks. Cloudflare Turnstile allows: Reducing automated submissions. Decreasing bot attacks. Protecting forms. Improving site security. Replacing traditional CAPTCHAs. It is generally installed on: Contact forms. Quotation forms. Login. Registration. Password recovery. Comments.6. Implement two-step authentication (2FA)
All administrative access should use two-factor authentication. Especially: WordPress. Hosting. Cloudflare. Corporate emails. CRM. Google Workspace. Microsoft 365. A password alone is no longer a sufficient security measure.7. Review users and permissions
It must be verified: Active users. Old users. Administrator permissions. Shared accesses. Weak passwords. Unused accounts. The principle of least privilege should always be applied.8. Update WordPress, plugins and themes
All components must be kept updated periodically to reduce vulnerabilities and ensure the proper functioning of the website. It should be reviewed: WordPress. Plugins. Themes. PHP. Database. Known vulnerabilities are one of the main causes of incidents, especially in environments with outdated plugins or inherited configurations. In the case of websites designed and developed by Estudio Ideas, and that also have managed hosting with us, this point is considered managed within the service, as core updates, plugins, themes, PHP environment, and database maintenance are part of the ongoing technical management of the system, aimed at keeping the site updated and ensuring its stability and operational continuity. This service is included in the annual hosting plan, which includes technical maintenance and necessary updates for the stability and operational continuity of the website.9. Review all forms
Each form should clearly indicate: What data is collected. For what purpose it will be used. Who is responsible. Link to the Privacy Policy. Consent when applicable. Additionally, it should be verified: Validation. Security. Spam protection. Storage.10. Write a Privacy Policy
The policy should explain, among other aspects: Collected data. Purpose. Legal basis. Retention periods. Rights of the data subject. Data transfers. Security measures. Contact information. It is not enough to copy a policy from another website.11. Write a Cookie Policy
It must inform: What cookies the site uses. Purpose. Duration. First-party cookies. Third-party cookies. How to reject them. How to delete them.12. Implement a Cookie Banner
The banner must allow the user to decide. It generally includes categories such as: Necessary. Statistics. Marketing. Preferences. Optional cookies should not be installed before obtaining the corresponding consent.13. Set up consent
Consent must be stored appropriately. It must be demonstrable: Date. Time. Accepted preferences. Rejected preferences. 14. Review Google Analytics The configuration of Google Analytics should be analyzed when this system is implemented on the website. If in use: What information is collected. Privacy settings. Data retention. Anonymization when applicable. Integration with Consent Mode or consent mechanisms.15. Review the Meta Pixel
The configuration of the Meta Pixel should be verified when this system is implemented on the website. If in use: Configured events. Data sent. Relation to cookie consent. Privacy and targeting settings.16. Review artificial intelligence tools
The use of Artificial Intelligence tools should be reviewed when these are integrated into the website or in its data collection or processing processes. If in use: Chatbots. Smart forms. Virtual assistants. Automations. AI agents. It must be identified what type of data they receive, process, or store, and under what conditions they operate within the system.17. Review CRM, ERP and SaaS applications
The use of CRM, ERP, and SaaS applications should be reviewed when these are implemented in the operation of the website or in the management of clients, suppliers, or internal processes. If in use: Stored data. Users and access permissions. Integrations with other platforms. Applied security measures. Data deletion or export processes. Backups and operational continuity.18. Review external services and formalize Data Processing Agreements
The use of external services should be reviewed when these are integrated into the website or participate in the processing of personal data. If in use: Email marketing platforms. Automation tools. Cloud storage services. Payment gateways. Messaging or communication services (including WhatsApp Business). Analytics or advertising tools. In all cases, it must be identified what personal data is shared, for what purpose, and under what conditions these providers operate. Each of these providers is, for legal purposes, a Data Processor, so the company should maintain a list of all of them and formalize with each a Data Processing Agreement (DPA) that establishes their security obligations and their responsibility in case of an incident.19. Define internal procedures
The company should establish written procedures for: Responding to requests from data subjects (ARCO rights: access, rectification, cancellation, and opposition, as well as the right to data portability). The law establishes a maximum period of 30 days to respond to these requests; this period should be explicitly stated in the Privacy Policy or in the corresponding attention channel, not just fulfilled in practice. Data deletion. Rectification. Accesses. Security incidents and data breaches: the law requires notifying the Personal Data Protection Agency within a maximum period of 72 hours from the time the incident is known, and to the affected data subjects when the risk to them is high. It is advisable to define in writing who decides if an event qualifies as a reportable breach, how it is documented, and who performs the notification. Backups. Restoration.20. Evaluate the designation of a Data Protection Officer (DPO)
The obligation to have a Data Protection Officer depends on the volume and sensitivity of the data the organization processes, being mainly required for public bodies and for large-scale processing of sensitive data. In smaller companies, this role can be assumed by the owner or an internal manager, as long as they have the appropriate training. Although it is not mandatory in all cases, having a designated and published DPO as a formal contact point is a sign of proactive responsibility in the face of potential inspections.21. Keep an ongoing review
Compliance with Law No. 21.719 is not a one-time task. It should be reviewed each time: A new plugin is installed. Hosting is changed. A CRM is incorporated. Artificial Intelligence is added. New forms are created. Ecommerce is modified. A new platform is integrated. Technology providers are changed. Legal or regulatory changes occur. Conclusion Complying with Law No. 21.719 involves reviewing and managing each of the points described in this guide. It is not an optional process nor is it resolved by installing a plugin. Each company must address these steps according to its reality, the data it processes, and the tools it uses. If your organization has not yet started this process, now is the time to do so. For further reference and consultation of the practical implementation framework, you can review the official guide published by the Digital Government Secretariat of the Government of Chile, under the Ministry Secretary General of the Presidency: 👉 Practical implementation guide for Law 21.719 on Personal Data Protectionhttps://wikiguias.digital.gob.cl/datos-personales/guia-practica-implementacion-nueva-ley-datos-personales





General topics
New services
Support
Support











































