Korea AI Basic Act prior notice: tell users the product uses AI
MSIT's guidelines name two duties: prior notice that a service uses generative AI, and labeling outputs. What prior notice looks like in an API product.

MSIT's guidelines on AI transparency set two duties for AI business operators: give users prior notice that a product or service uses high-impact or generative AI, and mark AI-generated outputs. The notice can be given through terms, contracts or visible notifications (MSIT guidelines, read 2026-10-02). Most coverage focuses on labels; the notice is the half that lives in your sign-up flow.
The two duties side by side
The guidelines separate telling people a service uses generative AI from labeling what it produces. Different methods apply depending on whether output stays inside the service or leaves it.
| Duty | What the page says |
|---|---|
| Prior notice | Inform users the product or service uses high-impact or generative AI, via terms, contracts or visible notifications |
| Labeling inside the service | Flexible methods, such as visual indicators, logos or a notice at login |
| Labeling exported output | More explicit marking: watermarks, visible or audible identifiers, or embedded metadata |
| Deepfakes | Labeling must be clearly recognizable to users |
| Who is covered | Direct providers of AI products and services, including international companies serving Korean users |
| Users of AI tools | Not subject to the obligations, for example a filmmaker using AI video generation |
What prior notice looks like in an API product
If you build an app on top of Sume's public API and offer it to people in Korea, you may be the business that provides the generative AI service to them. The practical question is where the notice sits: sign-up terms, a visible line on the generation screen, or both.
The page lists terms and contracts as acceptable carriers, so an accurate clause in your terms of service is not enough if the product screen shows an output that looks like a recorded human. Many teams do both: a sentence in the terms and a short visible notice next to the generate button.
A short plan
- Write one plain sentence saying the product uses generative AI to make video, images or audio.
- Place it in the terms and in the interface where people start a generation.
- Mark exported files with a visible or machine-readable label, using the stricter method for anything that leaves your service.
- Record who in your company owns the notice and when it last changed.
What Sume does and does not decide
Sume's docs do not state whether a given customer is a provider or a user under this law, and Sume does not insert your notice for you. The guidelines are a summary on a government page, and enforcement timing is covered separately; read the Korean text with counsel for anything binding.
Sources
Related posts
More in Use cases
- Korean captions on product clips: use korean-ad, not slam
slam, punch and tiktok-green have no Hangul glyphs and return 400 on Korean copy. Use korean-ad with language ko for Korean product clips; $0.20 a job.
- Find product moments in a live-commerce replay and trim them out
Run one transcript on a live-selling replay, find the sentences where each product is pitched, then cut each range with video-trim at $0.02 a clip.
- Live replay highlight reel in one render: detach once, no trims
Detach a live replay's audio once ($0.01), then build a 30-second highlight reel in one Timeline render using audio parts and source_in. No per-clip trim jobs.
- Log the exact video model id per shot after Runway model removals
When a vendor retires a video model, a logged model id turns the audit into a query. Record it on every shot, and know what Sume echoes.
Written by Sume