A customer's phone number or other personal detail sits in a spreadsheet or CRM field in plain text, and that's the exact thing an auditor asks about when GDPR, CCPA or HIPAA compliance comes up. AnonyFlow's answer is to protect that value with its own encryption, hand back a scrambled version to store, and unprotect it again only at the moment it's actually needed, for instance right before a text needs to go out to that customer.

On its own, protecting or unprotecting a value doesn't create anything a customer would notice, so pairing AnonyFlow with Mobile Message works best in the middle of a longer Zap. A trigger from another app starts things off, AnonyFlow unprotects the stored phone number so it's usable again, and Mobile Message sends the text using that decrypted detail. Used the other way, AnonyFlow can protect a customer's details for secure storage right after Mobile Message has sent them a confirmation text.