Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BD-3330: Add FAQ for field-level encryption #7845

Merged
merged 3 commits into from
Aug 8, 2024
+4 −0
Merged

BD-3330: Add FAQ for field-level encryption #7845

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2413659
BD-3330: Add FAQ for field-level encryption
lydia-xie Aug 8, 2024
21c128a
Apply suggestions from code review
lydia-xie Aug 8, 2024
159bd46
Update _docs/_hidden/private_betas/field_level_encryption.md
lydia-xie Aug 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions _docs/_hidden/private_betas/field_level_encryption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,3 +113,7 @@ The hashed email address is included in email delivery and engagement events.
### What email address should I expect to see in message archiving?

The plaintext email address is included in messaging archiving. These are sent directly to the customer’s cloud storage provider and there may be other personal data included in the email bodies.

### Can I use mail-to list-unsubscribe for subscription management with field-level encryption?

No. Using mail-to list-unsubscribe would send the plaintext decrypted email address to Braze. With field-level encryption enabled, we support the URL-based HTTP: method, including one-click. We also recommend including a one-click unsubscribe link in your email body.
lydia-xie marked this conversation as resolved.
Show resolved Hide resolved