Open MIT models · Seter v1.1

Seter: open models that catch Hebrew and Arabic names

Free, MIT-licensed PII detection for Hebrew, Arabic, English and mixed text. Includes first names on their own, which generic filters miss.

The browser demo runs the fast model on your machine (int8 ONNX, Transformers.js), so text never leaves the page. The accurate v1.1 model is the large checkpoint on Hugging Face.

Built for Hebrew & ArabicFirst names on their own, prefixes (ל/ו/ש), titles, kunyas (أبو …), and mixed HE/AR–EN text.
IDs, cards and accountsIsraeli IDs, passports, IBANs, and payment-card numbers including “ending in 1234” and masked forms.
Runs where you already workDrop-in labels aligned with openai/privacy-filter, plus a LiteLLM / Docker guard.

Measured, not claimed

On the REDACT Hebrew, Arabic and English records (LLM-generated — so synthetic-on-synthetic; evaluation only, never training), Seter v1.1 improves on the previous release and on OpenAI’s open privacy filter.

REDACT, char-level F1OpenAI privacy-filterSeter v1.1 largeSeter-fast (v1.0)
Hebrew (621)0.630.900 (released 0.904)0.84
Arabic (568)0.720.912 (released 0.917)0.88
English (534)0.700.871 (released 0.878)0.83

Large-model figures are the mean of 3 training seeds; the released weights are seed 1 (in parentheses). The fast model is still the 25 Oct 2026 v1.0 release. Source: Vats et al., REDACT, arXiv:2606.19881 (2026). Method and caveats are on the model card.

Hebrew first names on their own, on a fixed-seed REDACT subset (250 HE / 250 AR / 150 EN; ≥50% of the name covered by a person span):

Seter v1.1 largeGLiNER-multi-PIIDictaBERT-NEROpenAI privacy-filter
Hebrew (n=240)0.8830.3330.4920.142

Same subset, Arabic / English first-name recall for Seter v1.1: 0.921 / 0.952. Competitor rows are from the 3 Nov 2026 CPU bench (uniform decoder); Seter v1.1 was scored with the shipped shared decoder.

Payment-card recall on the released v1.1 weights, including last-four and masked forms: 98% / 90% / 95% Hebrew / Arabic / English (v1.0: 50% / 38% / 38%). Names caught (any overlap): Hebrew 99.5% vs 40% for openai/privacy-filter.

The honest part: REDACT is LLM-generated. Seter still masks more aggressively than GLiNER or privacy-filter, which means more false positives. Pick it when missing a name costs more than over-masking a word. Not yet compared against Azure or Private AI. The fast model has not been retrained for v1.1.

What you get (all free)

git clone https://github.com/Shoresh-Labs/seter-guard && cd seter-guard
docker build -t seter-guard . && docker run -p 8080:8080 seter-guard

POST /v1/redact   {"text": "..."}          # or plug into LiteLLM as a guardrail

Working with us

Seter is free and stays free. We work with privacy and DLP vendors that want a Hebrew/Arabic name layer to embed or license, and with teams in Israel working on Privacy Protection Law Amendment 13 (in force since 14 Aug 2025) that want help integrating, on-prem, or tuning it to their documents.

Talk to us about a pilot

Not legal advice and not a compliance certification. Seter is a detection model, not an anonymization guarantee.

Or just start: try the demo · download the models