Localize provides a number of ways to disable phrase ingestion to prevent the risk of Personally Identifiable Information (PII) and Protected Health Information (PHI) exposure.
It is possible to completely disable new content phrase detection by setting the
saveNewPhrases to false when in a production environment, which would fully eliminate the risk of PII/PHI or other unwanted content from reaching Localize servers.
However, this also prevents new phrases from being detected, which requires that you have a separate staging or development environment where the
saveNewPhrases option is turned on - all new phrases would be detected within the staging environment with no new content detected from production.
Then while in your production environment, Localize will deliver the appropriate translations to your end users, but won't be finding new content.
Use one of the following features in your Localize dashboard and/or initialization call to help block unwanted content.
Use Localize’s Disable Phrase Detection by Domain functionality to define what domains phrase detection should be enabled on.
Configure Localize to detect and translate only content that is contained inside a
<div> with a particular CSS class name (ignoring all other content on the page) by providing a list of class names in the translateClasses option in your
Configure Localize to block content that is contained in an HTML element with a particular CSS class or ID name.
Add a notranslate attribute to key HTML elements to prevent Localize from parsing those parts of the page.
Use Localize’s Block New Phrases by Pattern functionality to define regex patterns that, if matched, will prevent Localize from detecting the phrase.
Use Localize’s Disable Phrase Detection by Page functionality to define regex patterns that, if matched, will prevent Localize from detecting any phrases on that page.
Updated 8 months ago