| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-25 | 5.4 kB | |
| v0.8.0 -- A safety net against storing Aadhaar numbers in custom fields source code.tar.gz | 2026-09-25 | 1.8 MB | |
| v0.8.0 -- A safety net against storing Aadhaar numbers in custom fields source code.zip | 2026-09-25 | 2.3 MB | |
| Totals: 3 Items | 4.0 MB | 0 | |
v0.8.0 — A safety net against storing Aadhaar numbers in custom fields
This is deterrence, not prevention. It catches the most common accidents: a custom field named after Aadhaar, or a clean Aadhaar-shaped number typed into a custom field. It does not stop someone who is determined to store one, and it does not check most free text. Don't describe it to your users or auditors as blocking Aadhaar storage.
Why
OpenEstate doesn't collect Aadhaar numbers, but custom fields are free-form, so an admin can create a field like "Aadhaar number" and staff will fill it in. This release makes that harder to do by accident, and shows you whether it has already happened.
What's new
A field can't be named after Aadhaar. Creating or renaming a custom field whose name or label refers to Aadhaar (Aadhaar, Aadhar, Adhaar, Adhar, or आधार) is refused, on the admin screen, through the API, and when installing a plugin that would add one. "UID" is deliberately allowed.
A value that looks like an Aadhaar number is refused. When staff save a custom-field value that is 12 digits, starts with 2 to 9, and has a valid Aadhaar check digit, it's refused with a message naming the field. The number can be written plain, or in groups of four separated by spaces or hyphens. A value that's already stored isn't re-checked, so older records can still be edited.
A field that really holds 12-digit numbers can be exempted. For example, a bank account number. An admin ticks "Allow 12-digit values" on that one field. The change is recorded in the audit log, the field is marked in the list, and a field named after Aadhaar can't be exempted.
Machine-written notes are cleaned rather than refused. The inbound lead
API, a plugin's lead creation and the Excel importer have no one to show an
error to, so an Aadhaar-like number in the note they save is replaced with
[Aadhaar-like number removed].
Numbers already stored are masked when shown. On detail screens and in
the inquiries CSV export, an Aadhaar-like number shows only its last four
digits (XXXX XXXX 1234). This is masking on display and export only: the
full value is still stored, and the API still returns it.
A report of what's already there. deploy/native/find-aadhaar-like-values.sh
lists which custom fields hold Aadhaar-like values, with counts. It never
prints the values, changes nothing, and isn't run by install or upgrade.
Limits, stated plainly
- About 1 in 10 random 12-digit numbers look valid and will be refused. A genuine 12-digit number, such as a bank account, may need its field exempted.
- A mistyped Aadhaar number isn't caught. One wrong digit breaks the check digit, so the number looks ordinary and is saved. Nor is one written with other separators, such as dots or slashes.
- Only custom-field values are checked. Applicant names, addresses and
alternate phone numbers, follow-up notes, disposition remarks, ticket
messages and the inbound lead's name and email are not. This is tracked
in
docs/todo.md. - The name check can be wrong in Hindi. आधार also means "base", so "आधार मूल्य" (base price) is refused. The message suggests "मूल" instead.
- Masking hides the number on screen and in the CSV export, not in the database or the API.
Is any action needed beyond upgrading?
- Run the report once after upgrading:
bash
cd /opt/openestate-src/deploy/native
sudo ./find-aadhaar-like-values.sh
If it lists anything, decide what to do with those records. The upgrade doesn't change or delete stored values.
- If a field legitimately holds 12-digit numbers, exempt it in Admin → Custom Fields before staff next save that field.
- One database migration (a new column with a default); no new environment variable and no permission to re-grant.
How it was checked
- Automated tests cover the name check, the value check (with test numbers generated to have a valid check digit, never real ones), the exemption and its audit row, the cleaning of machine-written notes, masking in the CSV export, and the report. Browser tests drive the admin screen and the inquiry form.
- On a real install, a refused value was confirmed not to reach the API log, the web server's logs, the database log or the audit log.
- Checked by the project owner with real numbers, by hand, on 25 September 2026: pass, written plain, spaced and hyphenated. Only the result was recorded.
Not in this release
Booking custom fields, once planned for v0.8.0, have moved out and remain a planned item.
Upgrading
:::bash
cd /opt/openestate-src/deploy/native
sudo ./upgrade-native.sh --ref v0.8.0
Full procedure (backup, rollback behaviour, troubleshooting): Installation Guide.
Known issues
The known issues in the
v0.7.1 release notes and
v0.7.0 release notes still apply.
See CHANGELOG.md (github.com),
the [0.8.0] section, for the full detail, and
PR [#55] for the change
itself.