KHATT — UAE PDPL & Privacy Proof
How to Verify Emirates ID & GCC IBAN Masking Yourself
Don't take any gateway's privacy claim on faith. You can prove in 30 seconds that upstream models never see your real UAE Emirates ID, GCC IBAN, email, or phone number.
1. Why this matters for UAE & GCC teams
When agencies, clinics, real-estate teams, or developers in Dubai and Riyadh paste client records into AI tools, sensitive identifiers like 784-1990-1234567-1 (Emirates ID) or AE... / SA... IBANs normally travel straight to third-party model providers.
KHATT masks 9 categories of sensitive data in memory on the gateway (EMIRATES_ID, GCC IBAN, PHONE, EMAIL, Luhn-checked CARD, PASSPORT, API SECRET, DB_URL, and PRIVATE_KEY), then restores them only in your final response.
2. Step 1 — Preview the masking locally in your browser
Before spending a single credit, paste any sample Emirates ID or IBAN into our Free GCC PII Masker. It runs the exact same detection patterns locally in your browser.
3. Step 2 — Run the live "LLM Testimony" test
Send this exact prompt through https://api.khatthub.com/v1 (via Cursor, 9router, n8n, or @KhattAIbot using your 3 free trial credits):
Draft a short 2-sentence confirmation message to ali@dubai.ae (+971501234567) confirming we received Emirates ID 784-1990-1234567-1 and IBAN AE070331234567890123456.
What actually happens
- What the upstream model sees:
[EMAIL_1],[PHONE_1],[EMIRATES_ID_1], and[IBAN_1]. - Why the model's reply proves it: Flagship models notice they only received literal placeholders and will reply something like: "ali@dubai.ae, ..., 784-1990-1234567-1, and AE070331234567890123456 came through as literal placeholders, not real values."
- What you receive: Because KHATT unmasks the response stream on the way back, you still see your original values restored while the upstream provider never stored or saw them.
Test it live with 3 free trial credits — no card or dashboard signup required.
Test PII Shield in @KhattAIbot →© 2026 KHATT. ← All guides · GCC PII Masker · Home · Privacy