Can iDBQuery mask or redact sensitive fields?
Yes. iDBQuery can mask or redact sensitive fields so values like card numbers, emails, or national IDs appear partially hidden or withheld for users who lack permission, while the underlying data stays untouched in your source. Masking is tied to roles, so exposure depends on who is asking.
Masking and redaction reduce how much sensitive detail a user sees without removing the data from your systems.
- Partial or full masking - show only the last four digits of a card, a redacted email, or nothing at all, depending on the field and the viewer's role.
- Role-aware - the same query returns fuller detail for authorised users and masked values for everyone else.
- Source stays intact - masking is applied at query time; because iDBQuery queries in place, your source records are never altered.
For example, a customer-service view might show 'card ending 4242' so an agent can confirm a payment, while the full number is never surfaced. This pairs naturally with column-level permissions and row-level security: use permissions to hide a field entirely, or masking to reveal just enough to be useful. And because every iDBQuery answer is cited back to its exact source row, the citation respects the same masking - it will not leak the raw value in a footnote. Masking supports data-minimisation practices and helps you keep PII exposure proportionate to need, which is useful when you are designing for privacy obligations such as GDPR. It sits inside iDBQuery's broader architecture of query-in-place, RBAC, and encryption in transit and at rest. Talk to us about the masking rules that fit your data.
Updated 2026-06-22