Show [MASKED] in the UI while checks still run on the in-memory original — and why that matters for demos and shared screens.
Compliance demos and shoulder-surfing on shared desks make raw names and account numbers a liability. A useful pattern: mask the display layer while the engine evaluates the unmasked in-memory payload.
- UI shows [MASKED] for sensitive fields during review.
- Validation still uses the original values so format and presence checks remain truthful.
- No case-data database — payloads are not persisted by the open Form/Bulk surfaces.
Masking is not encryption at rest and not a substitute for your firm’s data-handling policy. It is a practical control for pre-file review sessions.