SMS consent does not authorize a KakaoTalk ad
The Korea Internet & Security Agency (KISA) has begun administrative action against advertisers who sent KakaoTalk brand messages to users who had only consented to receive SMS. KISA is treating those sends as illegal spam, requesting written justification from the advertisers and issuing corrective orders.
The principle behind the action matters more than the individual cases: marketing consent in Korea is granted per channel, not per customer. The same person, reachable at the same phone number, still has to opt in separately for each medium.
Every medium needs its own explicit opt-in
Under Korea's Network Act, commercial messages require explicit consent for each medium used to deliver them. SMS, voice calls, email, and KakaoTalk each count as a separate medium with a separate consent requirement.
Privacy consent is not marketing consent
This is where most international teams get caught. The consent a user gives for collection and use of personal data at signup does not include consent to receive commercial messages. The two rest on different legal grounds and must be collected separately, with separate wording.
A single "I agree to receive marketing communications" checkbox that silently covers every channel is exposed under this standard. Listing the channels and letting users opt into each one is the defensible design.
Non-compliance carries a fine of up to KRW 30 million
Advertisers who keep sending KakaoTalk ads after receiving a corrective order face a fine of up to KRW 30 million (roughly USD 22,000) under the Network Act. Critically, the fine lands on the advertiser, not the messaging vendor. Outsourcing the send does not outsource the obligation to prove valid consent.
What to audit before your next send
KakaoTalk has become the highest-open-rate CRM channel in Korea, and that pull created a common shortcut: migrating an SMS-consented list straight into KakaoTalk campaigns. This enforcement wave targets exactly that shortcut.
Store consent records per channel
When, in what wording, and for which medium consent was captured is the entire substance of a KISA response. Splitting consent into channel-level fields turns a compliance record into a usable audience field as well — the same first-party data hygiene covered in Google Expands Data Manager to Put First-Party Data to Work Across Analytics and DV360.
A four-question pre-send check
- Which medium does this list's consent actually cover?
- Did the consent notice name that medium explicitly?
- Is there a per-channel opt-out path?
- Can the brand — not the vendor — explain the legal basis for every record?
If any answer stalls, re-permissioning the list costs less than the fine.