| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1000 |
| Technical Name |
de_sensitive_field_masking_pii_vault |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
DE PII-Vault & Masking
Mask/encrypt chosen personal-data fields, role-based reveal and a full DSGVO access log (Art. 32 TOM)
DE Sensitive-Field Masking & PII-Vault (DSGVO Art. 32 TOM)
Key Features
PII-Vault Entry
PII-Vault Entry. Tracks Reference, Field Configuration, Model, Record ID, Record. One-click anonymise.
PII-Vault Field Configuration
PII-Vault Field Configuration. Tracks Label, Model, Model Name, Field, Field Name. One-click view access log.
PII-Vault Bulk Scan / Migration
PII-Vault Bulk Scan / Migration. Tracks Reference, Field Configuration, Blank Source After Vaulting, Extra Domain, Records Scanned. One-click run, view entries.
Reveal Vaulted Value
Reveal Vaulted Value. Tracks Vault Entry, Field, Masked, Reason for Access, Clear Value. One-click reveal.
Store Value in Vault
Store Value in Vault. Tracks Field Configuration, Record ID, Record Label, Clear Value, Mask Preview. One-click store.
DE Sensitive-Field Masking & PII-Vault
DE Sensitive-Field Masking & PII-Vault (DSGVO Art.
32 DSGVO requires the controller
32 DSGVO requires the controller to implement appropriate technical and organisational measures (TOMs) — explicitly pseudonymisation and encryption — to protect personal data, and to apply data minimisation so that staff only see the personal data they actually need.
In practice, sensitive fields (IBAN
In practice, sensitive fields (IBAN, tax ID, health notes, ID numbers) sit in clear text on records that far too many users can open.
Use Cases
Screenshots
Reveal Value
Piivault Settings
Why Choose This Module
This module is a PII-vault: it lets a data-protection officer declare which model fields are sensitive, stores their value encrypted in a separate vault, and shows a masked placeholder (e.g. DE12••••3456) to everyone except the roles explicitly authorised to reveal it. Every reveal is written to an immutable access log (who / which field / which record / when / why), giving the controller the Art. 5 Abs. 2 accountability evidence and a ready answer when a data subject or the authority asks "who looked at my data?".
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: base, mail
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1000 |
| Technical Name |
de_sensitive_field_masking_pii_vault |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module