How to store Encrypted and Sensitive data?

What are Encrypted Fields?

Encrypted fields provide an additional layer of security for your data in ZEPIC. When you mark a field as encrypted, the information stored in that field is securely encrypted in our database, protecting it from unauthorized access.

What are Sensitive Fields?

Sensitive fields offer the highest level of protection for your most confidential information. In addition to encryption, sensitive fields have special handling properties:

• They receive maximum protection in the database
• They cannot be used in email or WhatsApp campaign personalization
• They can be masked when displayed to users with limited permissions

How to Create Encrypted and Sensitive Fields

Creating an Encrypted Field

1. Go to Settings -> Objects. Create a new object or edit an existing object.
2. Click "Add New Field"
3. Configure your field properties as needed
4. Enable the "Encryption" option
5. Save your changes

Important: The encryption property can only be enabled during field creation. You cannot add encryption to an existing field later.

Creating a Sensitive Field

1. Follow steps 1-3 above for creating a field
2. Enable the "Encryption" option
3. Check the "Sensitive Data" option
4. Configure masking characters if needed
5. Save your changes

Configuring Masking for Sensitive Fields

Masking allows you to control how sensitive data appears to users with different permission levels:

1. When creating a sensitive field, scroll to the "Masking characters" section
2. Select your preferred masking pattern (asterisks, custom characters, partial display)
3. Preview how the masked data will appear to users

Best Practices for Using Encrypted and Sensitive Fields

• Use encryption for data that requires protection but still needs to be used in campaigns and automations
• Use sensitive fields for highly confidential information that should never appear in outgoing communications
• Plan your field structure carefully since encryption settings cannot be modified after field creation
• Establish clear governance policies about which team members can access unmasked sensitive data
• Regularly audit who has access to view sensitive information

Limitations and Considerations

• Sensitive fields cannot be used in personalization tokens for campaigns
• Search functionality may be limited for encrypted and sensitive fields
• Reporting that includes sensitive fields will display masked values based on user permissions
• Exported data will maintain security restrictions based on user access levels

Need Help?

If you have questions about implementing encrypted or sensitive fields in your ZEPIC instance, contact our support team at support@zepic.com