Same reasoning as the existing CVV/PIN/DATE entries: a bare mention
("Экскурсия в Нижний Новгород", "цены выросли в Казахстане") isn't
personal data on its own, only alongside some other PD that ties it to
a specific person. The mechanism was already generic — this only adds
two more types to the default set.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
28 lines
603 B
JSON
28 lines
603 B
JSON
{
|
|
"default": {
|
|
"enabled": true,
|
|
"demask": true,
|
|
"maskMode": "MASK",
|
|
"types": ["*"],
|
|
"requireCompanion": ["CVV", "PIN", "DATE", "BIRTH_PLACE", "ADDRESS_COUNTRY"]
|
|
},
|
|
"crm": {
|
|
"enabled": true,
|
|
"demask": false,
|
|
"maskMode": "TOKEN",
|
|
"types": ["FIO", "PHONE", "EMAIL", "ADDRESS_CITY", "ADDRESS_STREET", "ADDRESS_HOUSE", "ADDRESS_FLAT"]
|
|
},
|
|
"analytics": {
|
|
"enabled": true,
|
|
"demask": false,
|
|
"maskMode": "SYNTHETIC",
|
|
"types": ["*"]
|
|
},
|
|
"legacy-billing": {
|
|
"enabled": false,
|
|
"demask": false,
|
|
"maskMode": "MASK",
|
|
"types": ["*"]
|
|
}
|
|
}
|