Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
South Korean platform (Kakao Corp.) offering Maps and Login SDKs, sharing, and the Kakao Pixel for advertising conversion tracking. Data is processed in South Korea.
Kakao Corp. is a South Korean technology company behind KakaoTalk and a family of developer tools, including the Kakao Maps JavaScript SDK, the Kakao Login SDK, Kakao share buttons, and the Kakao Pixel for advertising conversion tracking. Websites add these SDKs and pixels to integrate maps, social login, sharing and ad measurement.
When a Kakao SDK or the Kakao Pixel loads, the browser connects to Kakao domains such as dapi.kakao.com and analytics.kakao.com and may set cookies including _kawlt, _kahai, _karmt, TIARA and _T_ANO. These support login sessions, analytics and the advertising pixel, which reports conversion events back to Kakao for ad measurement and optimisation.
The Kakao Login session cookies can be strictly necessary for a login feature the user requested, but the Kakao Pixel and TIARA analytics are advertising and measurement technologies. Under the ePrivacy Directive these require prior consent, and the GDPR lawful basis is consent under Article 6(1)(a).
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Block the Kakao Pixel and analytics SDKs until the visitor consents, and load only the strictly necessary login or map features without consent where genuinely requested. Use a consent management platform so that the advertising pixel fires only after an affirmative opt in.
Kakao processes data in South Korea, a third country. Importantly, the European Commission adopted an adequacy decision for South Korea in December 2021 covering commercial operators under PIPA, so transfers to in scope Korean recipients rely on Article 45 adequacy and do not need Standard Contractual Clauses. You should still disclose the transfer to Korea in your privacy notice.
List Kakao and its cookies in your cookie policy, gate the Pixel and analytics behind consent, document the Korea transfer and the adequacy decision in your records, and keep login session cookies separate as strictly necessary. Review which SDKs you actually need so you load the minimum.
Websites using Kakao must obtain user consent under GDPR regulations.
DPIA considerations
The Kakao Pixel and TIARA analytics justify a DPIA because they track advertising conversions. Assess the identifiers set, the transfer to South Korea that is covered by Article 45 adequacy, and the separation of strictly necessary login session cookies.
Sample consent text
This site uses Kakao for maps, login, sharing and the Kakao advertising Pixel. The Pixel sets identifiers and sends events to Kakao in South Korea. Do you consent to loading the Kakao Pixel and analytics?
Third-party domains contacted
kakao.comdapi.kakao.comt1.kakaocdn.netdevelopers.kakao.comanalytics.kakao.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| _kawlt | Third-party | Session to 12 hours | Kakao Login authentication token cookie used to maintain a signed in session for the Kakao account. |
| _kahai | Third-party | Persistent | Kakao Login helper cookie that supports the authentication and session handling of the Kakao account. |
| _karmt | Third-party | Persistent | Kakao Login refresh related cookie used to renew the authenticated session. |
| TIARA | Third-party | 2 years | Kakao TIARA analytics identifier used to measure usage and attribute activity across Kakao services. |
| _T_ANO | Third-party | Persistent | Kakao analytics and advertising cookie used together with the Kakao Pixel for conversion measurement and ad optimisation. |
Kakao places tracking cookies for advertising — comply with GDPR using FlowConsent.
Kakao SDKs and the Pixel can set cookies such as _kawlt, _kahai and _karmt for login sessions, and TIARA and _T_ANO for analytics and advertising. The Pixel reports conversion events to Kakao.
Yes. The Kakao Pixel and TIARA analytics are advertising and measurement technologies, so they require prior consent under the ePrivacy Directive before they load.
The Pixel and analytics rely on consent under Article 6(1)(a) GDPR. Strictly necessary login session cookies for a feature the user requested can rely on contract or legitimate interest.
Yes, Kakao processes data in South Korea. This is permitted because the European Commission adopted an adequacy decision for South Korea in December 2021 for commercial operators under PIPA, so transfers rely on Article 45 adequacy and need no Standard Contractual Clauses.
A DPIA is recommended where you use the Kakao Pixel or analytics, because they track advertising conversions and set identifiers. Assess the data collected, the consent flow and the transfer to Korea, even though it is adequacy covered.
Gate the Kakao Pixel and analytics SDKs behind a consent banner, load only the login or map features the user actually requests, list Kakao in your cookie policy, and record the Korea transfer and adequacy decision in your processing records.
If you only need maps or login, you can load those SDKs without the advertising Pixel. For conversion measurement you could use a consent gated, server side or privacy focused analytics approach instead of the client side ad pixel.
Add an entry naming Kakao Corp., the cookies the SDKs and Pixel set, their login, analytics and advertising purposes, and the transfer to South Korea covered by the Article 45 adequacy decision, with a link to Kakao's privacy policy.