# Image Rights Risk Filter Operations

## Modes

- Internal-only mode: external web detection is disabled. The batch still runs fingerprint, knowledge-base, face/person-presence, and scoring logic.
- External-enriched mode: Google Cloud Vision web detection can run only after contract, DPA, content-retention, request-metadata logging, region, credential, and quota controls are approved.
- Search-enriched mode: official text-query search APIs can supplement operator evidence. Naver search is used for Korean query-based evidence, not image-upload reverse search.
- LLM-assisted mode: an internal LLM can generate search queries, structure search results, and summarize evidence for operators. It must not decide the score or final status.

## Hard Boundaries

- Do not automate Google Image Search or Google Lens web UI.
- Do not automate Naver web search UI or scrape Naver result pages.
- Do not send internal originals to external APIs.
- Do not send original images or analysis derivatives to Naver search; use text queries only.
- Do not store face embeddings, celebrity identity matches from faces, or biometric templates.
- Do not use an LLM output as standalone evidence unless it is tied back to source evidence.
- Do not expose automated scores, evidence, or provider details to applicants.
- Do not let the filter change review status automatically.

## Disable External Calls

Set the external API policy to disabled. Batches should continue internal-only and record external-skipped evidence reasons for affected submissions.

Set the search API policy to disabled to stop Naver enrichment. The review enrichment job should continue with existing internal and Google evidence, then record search-skipped reasons for operators.

Disable the internal LLM assistant if prompt logging, model hosting, or source-citation behavior cannot be audited. LLM-disabled operation should still show raw internal, Naver, and Google evidence.

## Provider Credentials And Quotas

- Keep Naver credentials separate from Google credentials.
- Configure provider-specific daily limits before enabling search-enriched mode.
- Treat quota exhaustion as an operator-visible skipped-provider state, not as low-risk evidence.
- Do not log raw original images, derivatives, or applicant personal data in provider request metadata.

## Operator Guidance

Scores are triage signals, not legal conclusions. Operators should review the reasons and evidence, then choose approved, held, or rejected manually.

Evidence status is a judgment aid. Mark evidence as used for judgment, irrelevant, false positive, or pending to keep the case record clear. Evidence status alone must not create a knowledge-base entry.

Held and rejected case decisions create watchlist candidates. Watchlist matches are strong future risk signals, but they are visually separated from confirmed DB matches and never change a future case decision automatically.

Promote a watchlist candidate only after the team accepts it as a reusable confirmed reference. Exclude it when it is a false positive so future internal similarity analysis ignores it.

Naver results are search evidence candidates. Operators should prefer results that connect the submitted image to a named person, work, character, broadcast, webtoon, game, official source, or repeated matching image source.

LLM summaries are reading aids. If a summary mentions a celebrity, character, or copyrighted work without a linked source result, treat that claim as unverified.

## Correction Flow

If a rejection or hold was wrong, correct the operator decision and exclude any watchlist candidates derived from that decision so future submissions are not penalized by stale evidence.
