Skip to main content
Data Confidentiality for Self-service

Learn how to keep data secure when using our self-service capabilities.

A
Written by Amy Blakemore
Updated over 4 months ago

Many campaigns—especially those conducted in regulated industries—contain sensitive information. This article recaps the standard Persado security measures that are in place for your data, as well as some specific steps you can take for campaigns containing especially sensitive information.

Persado Security Measures

Persado’s GenAI platform is built with the highest standards of governance, security, and privacy, so you can leverage the power of AI responsibly and securely. With compliance to ISO 27001 and SOC 2 Type 2 standards, and safeguards against bias, third-party data sharing, and copyright infringement, Persado provides a platform that not only drives innovation but also upholds the principles of responsible AI use.

As these measures pertain to your campaigns, keep in mind that:

  • Only users from your company and Persado employees can see your content in the Persado Portal.

  • All content and response data is anonymized and aggregated and contains no customer identifiers. You own the data; we only anonymize it to drive platform learnings.

  • Facts (e.g., products, offers, data, times, locations) from any of your content aren't used in other customer’s content.

Extra Steps for Sensitive Campaigns

Sometimes, your campaigns might include additional, sensitive data—perhaps even data that not all of the Persado users at your company should have access to (e.g., dates, locations). In these instances, it’s key that you know when your topic is in fact sensitive, as our self-service tool is not able to flag that. Here are some techniques to leverage when working with sensitive content:

  • Generate content from scratch (rather than improve it) to get language suggestions without having to provide the exact details.

  • Use self-service to create headlines and CTAs, and then fill in the sensitive subheader/short paragraph information later.

  • Mask sensitive information, like dates, with generic placeholders if needed, and then fill in the details during your business as usual process prior to deployment. You can format any variables following your business as usual process (e.g., [x], <x>, %%x%%). Here are a few examples:

Copy with Sensitive Information

Copy with Sensitive Information Removed

Potential Keyphrases

“This change is effective on September 1”

“This change is effective on [date]”

Policy change; coming soon

“It’s here: the new and improved Silverton Rewards Card”

“It’s here: the new and improved [product title]”

New product; new product release

“We’re teaming up with Silverton Hawaii to bring you an even better experience”

“We’re teaming up with [partner title] to bring you an even better experience”

Partnership; improved experiences

Did this answer your question?