Qoamo-PII-Decision

A routing model that catches personal data in Korean and English requests before they leave the device. Built on skt/A.X-Encoder-base (ModernBERT, 149M parameters), it was fine-tuned as a decision model that answers questions about a text with a probability for every option.

It can be asked four things about a text (whether it contains personal data, whether it contains a strong identifier, its tier, and which of 33 types it holds), and the answers decide whether the text is sent as is, masked and then sent, or blocked. The decision is made from the first three questions; the types are asked only when needed. Locating the values is not its job. For a text it marks as containing personal data, atonlee/koelectra-ko-pii-ner, built on the same tier1 and tier2 criteria, finds and masks the values. This keeps the fast filtering decision separate from precise masking by NER.

On the official KDPII test split, it scored an F1 of 0.951 at telling whether a sentence contains personal data, the highest among the compared models. The weights are a single safetensors file (bf16). If you need ONNX, use one of the four in onnx/ (float32 · FP16 · INT8 · UINT8).

News

🔥 2026.10 Update

• English: it now judges English text as well as Korean.
• Types 23 → 33: passwords, API keys or tokens, and verification codes or OTPs are asked about separately. Phone numbers are split into regular, business or toll-free, and short public numbers, and personal numbers into employee, member or customer, student or exam, and patient numbers, among others.
• Decision and tier together: decide returns the tier (tier1 · tier2 · none) along with the decision (보냄 · 확인 · 막음). With with_types=True it returns the types as well.
• Asking with different criteria: ask about several types as one (has), leave some types out (has_pii_except), or regroup the tiers into up to 4 levels (tier).
• Long texts: with document=True, a text of up to 2,000 characters is judged in one go. A longer one is split on line breaks and the strictest decision is returned.
• Ready-to-use code: load it with AutoModel.from_pretrained(..., trust_remote_code=True) and use it in one line with model.decide(text).
• Accuracy: KDPII F1 0.896 → 0.951 (10 types 0.918 → 0.955). Every sentence holding a tier1 value was caught.

Questions

The model can be asked four things about a text and gives a probability for every option.

• pii_any — contains personal data? (예 yes · 아니오 no)
• pii_t1 — contains a strong identifier? (예 · 아니오)
• pii_tier — tier (tier1 · tier2 · none): picks the single highest tier in the text.
• type_* — 33 types (예 · 아니오 for each type)

decide asks only the first three; with with_types=True it also asks the 33 types. The questions never see each other, so the answers are the same however many are asked together, and asking fewer is faster.

Tiers and types

In code, use the Korean names in parentheses (CVC and URL as written); they are the names in model.types.

Four answers per text

Asking with different criteria

The tiers above are the default, and the 보냄 · 확인 · 막음 decision was tuned with them. The best results come from using the default tiers as they are. If your policy differs, there are three ways to change the criteria.

• Grouping (has): ask in one go whether any of several types, such as phone number, email and address, is present. On groups it had not seen in training, it was right 99% of the time. To treat some types more strictly, ask with this and raise the tier in your code.
• Excluding (has_pii_except, or leaving types out in tier): leave some types out, so that, for example, a text with only a name does not count as personal data. On texts holding the left-out types it was right 97% of the time or more.
• Changing the tiers (tier): move types between tiers. Use up to 4 levels, named tier1, tier2, tier3, tier4 and none. It is less accurate on texts that hold the moved types. In particular, a type moved up to tier1 tends to stay in its original tier when another tier2 value is present, so use grouping to raise a type.

The fourth and fifth examples under Usage show how. The question wording (the instructions in pii_config.json) can be changed too, but this is not recommended.

Usage

Load it with trust_remote_code=True. Only the files it needs are downloaded, not onnx/. decide gives the decision and the tier from three questions.

pip install "transformers>=5.1" torch

from transformers import AutoModel

model = AutoModel.from_pretrained("atonlee/Qoamo-PII-Decision", trust_remote_code=True)

for text in ["내일 오후 세 시에 팀 회의 잡아 줘",
             "박지훈 대리한테 010-4821-3307 로 문자 보내 줘",
             "내 주민번호 901023-1234567 로 등록",
             "Send the signed contract to david.kim@acme.io"]:
    r = model.decide(text)
    print(f"{r.route} | {r.tier} | {text}")

Output:

보냄 | none | 내일 오후 세 시에 팀 회의 잡아 줘
확인 | tier2 | 박지훈 대리한테 010-4821-3307 로 문자 보내 줘
막음 | tier1 | 내 주민번호 901023-1234567 로 등록
확인 | tier2 | Send the signed contract to david.kim@acme.io

To see the types as well, pass with_types=True. It asks 36 questions and is several times slower.

r = model.decide("박지훈 대리한테 010-4821-3307 로 문자 보내 줘", with_types=True)
print(r.route, r.tier, r.types)

Output:

확인 tier2 ['이름', '일반 전화번호']

Judge a long text with document=True. A single corporate card number in the middle of the email is enough to block the whole email.

mail = """팀장님, 지난주 부산 출장 정산 건으로 메일 드립니다.

일정은 10월 6일부터 8일까지 2박 3일이었고, 협력사 두 곳과 미팅을 진행했습니다.
교통비는 KTX 왕복 119,600원, 숙박비는 2박 236,000원, 식대는 84,000원입니다.
영수증 원본은 내일 오전 중에 경영지원팀 정산함에 넣어 두겠습니다.

숙박비는 법인카드 4518-3207-6614-2093 으로 결제했고, 나머지는 개인 카드로 냈습니다.
개인 결제분은 이번 달 급여와 함께 넣어 주시면 됩니다.

미팅 결과는 따로 정리해서 금요일 회의 때 공유드리겠습니다.
감사합니다."""

r = model.decide(mail, document=True, with_types=True)
print(r.route, r.tier, r.types)

Output:

막음 tier1 ['카드번호']

To treat contact details more strictly, ask whether there are any and raise the tier if so. Only the second, third and fourth texts, which hold contact details, move up to tier1; the text with only a name and the text with an account number stay as they were.

texts = ["김민수 팀장님께 오늘 회의록 보내 드려",
         "박지훈 대리한테 010-4821-3307 로 문자 보내 줘",
         "견적서 jiyoung.park@gmail.com 으로 보내 줘",
         "서울 강남구 테헤란로 152 12층으로 서류 보냈어",
         "신한 110-482-339201 로 월세 55만 원 보내 줘",
         "내일 오후 세 시에 팀 회의 잡아 줘"]
contact_types = ["일반 전화번호", "이메일", "주소"]

for text in texts:
    before = model.decide(text).tier
    after = "tier1" if model.has(text, contact_types, name="연락처") else before
    print(f"{before} → {after} | {text}")

Output:

tier2 → tier2 | 김민수 팀장님께 오늘 회의록 보내 드려
tier2 → tier1 | 박지훈 대리한테 010-4821-3307 로 문자 보내 줘
tier2 → tier1 | 견적서 jiyoung.park@gmail.com 으로 보내 줘
tier2 → tier1 | 서울 강남구 테헤란로 152 12층으로 서류 보냈어
tier1 → tier1 | 신한 110-482-339201 로 월세 55만 원 보내 줘
none → none | 내일 오후 세 시에 팀 회의 잡아 줘

To stop counting names as personal data, ask with the default tiers minus names. The first text, which holds only a name, becomes none, and the second, with a name and a phone number, stays tier2 because of the phone number.

custom_tiers = {"tier1": model.tiers["tier1"],
                "tier2": [t for t in model.tiers["tier2"] if t != "이름"]}

for text in texts:
    print(f"{model.decide(text).tier} → {model.tier(text, custom_tiers)} | {text}")

Output:

tier2 → none | 김민수 팀장님께 오늘 회의록 보내 드려
tier2 → tier2 | 박지훈 대리한테 010-4821-3307 로 문자 보내 줘
tier2 → tier2 | 견적서 jiyoung.park@gmail.com 으로 보내 줘
tier2 → tier2 | 서울 강남구 테헤란로 152 12층으로 서류 보냈어
tier1 → tier1 | 신한 110-482-339201 로 월세 55만 원 보내 줘
none → none | 내일 오후 세 시에 팀 회의 잡아 줘

• r.scores holds the probability of every option for the questions asked.
• When the decision is 확인, find and mask the personal data with NER, then send.
• With document=True, a text over 2,000 characters is split on line breaks, each piece is judged, and the strictest decision and tier are returned (the pieces are in r.pieces).
• You can ask only the questions you need, like model.ask(text, ["pii_any", "pii_t1"]). The decide rule then does not apply.
• To leave ONNX out when downloading the whole repository, use snapshot_download(..., ignore_patterns=["onnx/*"]).

Evaluation

We measured whether a sentence contains personal data on the official test split of KDPII (CC BY 4.0). Sentences were selected based on our types and the 10 common types (3,998 sentences for our types, 3,737 for the 10 types). KDPII was not used to train this model. Widely used PII detection, decision and guard models on Hugging Face were run on the same sentences and scored the same way.

• F1 (our types): name · phone · mobile · email · vehicle number · IP · user ID · date of birth · age · gender · resident registration number · alien registration number · passport number · driver's licence number · card number · account number
• F1 (10 types): name · phone · mobile · email · resident registration number · alien registration number · passport number · driver's licence number · card number · account number

Data

Training data includes the following.

• BCCard/privacy-filter-openpii-masking (CC BY 4.0)
• nvidia/Nemotron-PII (CC BY 4.0)
• clinc/clinc_oos (CC BY 3.0)

License

Apache-2.0