AI Data Loss Prevention
Avoid Leaking Sensitive Information!
Our AI Data Loss Prevention feature ensures sensitive data and Personally Identifying Information (PII) is never stored or processed by a language model.

Additional Highlights
See what makes Rezolve.ai's SideKick 3.0 a no-brainer for your everyday business operations.
Define and add additional PII entities unique to your organization, such as Employee ID numbers, Personal Account Numbers, etc.
Define exceptions to the PII redactions via a Whitelist. For example, you could redact all email addresses except the IT support email address. Conversely, the Blacklist can prevent users from sharing very specific email address, while allowing other emails more broadly.
Freely adjust the sensitivity of the PII detection algorithm to control how aggressively the system identifies and redacts potential PII.
Enhance the accuracy of PII detection by adding context words for the algorithm to consider. For example, if the word “Account” is found near a string of numbers, it would be more likely to identify the numbers as an Account number.
%203.png)
%201.avif)
%203.png)
%203.png)
See Why Our Customers Love Us
Security and Compliance
Rezolve.ai ensures the highest levels of data security and information privacy. We comply with all major global data security standards to give you peace of mind.




FAQs
Frequently Asked Questions are Rezolve.ai and its capabilities
No, our Data Loss Prevention algorithm is processed on-device, ensuring that sensitive or PII is never stored or sent to an external language model or processing system. Additionally, we never train or fine-tune our models using customer data.
Yes! Using our Custom Entities feature you can add PII entities unique to your organization, such as Employee ID numbers, Account Numbers, and more.
When PII-Education mode is enabled, the bot will interrupt a conversation anytime it detects the usage of Personally Identifying Information to educate the user. It’ll explain why sharing such information is risky and provide guidance on how to rephrase the query without including it.