Choose the language mix
Identify the languages, scripts and document types your team handles, including bilingual records.
Review personal data in regional documents, bilingual forms and mixed-script records within your own environment.
For Government, privacy and document operations teams
Discuss this workflow ↗Records may combine English headings, regional-language fields and identifiers written in local numerals. Discovery needs to account for the script, the data category and the quality of the source.
Identify the languages, scripts and document types your team handles, including bilingual records.
Use configured OCR routes and local detection models, with numeral normalization before identifier checks.
Check candidate personal data against the original page and validate coverage using representative records.
Coverage is assessed by task. The current repository includes separate evaluations for reading documents and detecting numbers, with model-specific coverage for names and speech.
| Task | Languages | Assessment |
|---|---|---|
| Document OCR | Assamese, Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Nepali, Punjabi, Sindhi, Tamil, Telugu and Urdu | Evaluated on synthetic bilingual ID cards. Validate with your document layouts and scan quality. |
| Document OCR with partial coverage | Odia and Sanskrit | Evaluated on synthetic cards. Recognition needs further improvement and source review. |
| Identifier and number detection | All 22 scheduled Indian languages, plus English | Digit normalization and number-word lexicons evaluated on synthetic text. Coverage depends on the identifier and extraction quality. |
| Additional script reading | Ho, Santali and Sora | Character recognition evaluated on synthetic text. Personal data detection in these languages needs separate validation. |
| Names and speech | Coverage depends on the configured language models | Assess names and audio separately for your language mix. Indian-language speech requires evaluation on representative recordings. |
Inspect records containing English and regional-script fields, then review findings against the original page.
Normalize digits from different scripts before applying identifier patterns and checksum checks.
Package the required language models and dependencies locally for the agreed deployment.
Bring representative scans and recordings to your pilot so we can assess language, layout and data-category coverage together.
A reviewer checks the original field and the normalized digits before confirming the finding.
PIIE is in development. File coverage, detection categories and deployment requirements are agreed during pilot assessment.
Review candidate personal data with file locations, categories and confidence.
Use reviewed findings to inform catalogues and privacy workflows through an agreed integration.
Explore PERM ↗Pass reviewed locations into a scoped redaction workflow for supported content.
Explore DART ↗Discuss your file formats, data categories and deployment requirements.
Bring scattered documents and media into a reviewable picture of personal data exposure.
Give privacy and business teams source-level findings to support their personal data inventory and evidence gathering.
Screen datasets for personal data before annotation, external review or vendor sharing.
Locate identity and financial data in scanned forms and supporting documents for human review.
Plan personal data discovery around your infrastructure, access rules and operational responsibilities.