How to choose and implement a consent management platform in a large company
A consent manager is a platform that requests, records and administers the authorizations that people give for an organization to use their personal data. It stores what each person authorized, for what purpose, on which version of the text and whether that authorization is still valid or was revoked.
For a large organization in Chile, the best platform is the one that works across all the channels where data is requested and leaves evidence that can be shown to the Personal Data Protection Agency. This guide explains what to review and how to implement it.
When consent is needed
Consent is one of the lawful bases that allow personal data to be processed under Law 21.719. It is not the only one: there are processing activities that rely on other bases. That is why the first step is to know, processing by processing, which ones depend on consent.
When it does depend on it, Law 21.719 defines consent as a manifestation of free, specific, unequivocal and informed will, obtained before the processing and which the data subject can revoke. Each of those conditions has an operational consequence: it must be requested before processing the data, it must explain what for, it must be separated by purpose and it must allow withdrawal.
What a consent management platform must have
Evidence per authorization: purpose, channel, version of the text, date and time, and status (valid or revoked).
Versioning: when the text changes, the platform must know which version each person accepted.
Simple revocation: the person must be able to withdraw their authorization, and the systems must find out.
All channels: web, app and in-person service with the same standard.
A single source of truth: any system or executive can check what can be done with a person's data.
Integration with existing systems: APIs and events so that the CRM and the other systems receive the changes.
Data subject portal: a place where each person sees what they authorized and manages it.
Consent and cookie banner are not the same
The cookie banner manages what the website does in the browser of whoever visits it. A consent manager covers all processing activities that depend on an authorization: the benefits club, the sending of offers, the quoting of an insurance policy. Many organizations need both things, ideally on the same basis. About the banner, see Your cookie banner can be a trust asset for your company.
How to choose
There are two types of tool on the market. Global platforms, such as OneTrust, manage consent and preferences as part of a multinational privacy program, and are configured for each country's regulations during implementation. Local platforms, such as Soyio, are designed for Law 21.719 and for Chilean sectoral rules such as REDEC.
Three questions help decide:
Can it demonstrate what each person consented to, on which version and whether it is still valid?
Does it work across all the channels where data is requested today, including in-person service?
How much integration work does it require and who does it?
How to implement it in a large organization
1. Map where data is requested. Forms, apps, private customer sites, checkout counters and executives. If a record of processing activities exists, the list of purposes is there.
2. Define a common standard. One same legal text and one same structure for the whole group, with room for each brand or subsidiary to adjust its own.
3. Start with one flow in production. Choose one where consent matters and where the effect can be measured.
4. Measure. Asking for consent touches the experience, and there the commercial area has a voice. Measuring is the way for legal and business to talk with data.
5. Extend channel by channel. With a validated pilot, add channels and subsidiaries on the same basis.
6. Open the data subject portal. So that each person can see what they authorized and change it.
What the data shows: a financial group
A Chilean financial group integrated Consent into two digital sales flows that were already in production. To find out whether asking for consent affected sales, it ran an A/B test on 15% of the flow.
With consent | Without consent | |
|---|---|---|
Conversion | 20.9% | 15.1% |
Advances to identity verification | 89.1% | 96.1% |
Conversion time | 23m13s | 18m5s |
The flow with consent takes more time and fewer people advance to identity verification. Even so, more people end up signing up. The team's hypothesis is that whoever reads and authorizes arrives more decided.
One basis, many brands: a pharmacy chain
A group that operates a pharmacy chain and other retail brands records its customers' consent in its apps and at its pharmacies' checkout counters. The component adapts to each brand's image, but the structure is the same: to whom consent is granted, what data is requested, what it will be used for, how long it lasts and how to exercise rights.
It tested it in a pilot store and then activated it across the whole chain.
How Soyio solves it
Consent, Soyio's module, records, versions and revokes each authorization with verifiable evidence. It integrates via API, SDK and embeddable components on web, mobile and in-person service. Configuration is adjusted by purpose, product and subsidiary, and the changes reach internal systems via API and webhooks.
Frequently asked questions
What is a consent manager?
A platform that requests, records and administers the authorizations that people give for the use of their personal data, with evidence of what each one authorized and whether it is still valid.
What is the best consent management platform in Chile?
The one that works across all the channels where the organization requests data, leaves verifiable evidence and is prepared for Law 21.719. Soyio is built in Chile for that scenario and is used by banks, insurers and pharmacy chains.
Does asking for consent lower sales?
In the case of a financial group that measured it, no. In an A/B test, conversion with consent was 20.9%, versus 15.1% without it.
Is a cookie banner enough?
Not for all processing activities. The banner covers what happens on the website. Processing activities that depend on an authorization in apps, checkout counters or executives need their own management.
How long does it take to implement?
It depends on how many channels and systems have to be integrated. The usual approach is to start with one flow, measure and extend.