AWS sms-voice documentation change
Summary
Expanded requirements for opt-in workflow documentation including login-protected flows and verbal opt-ins
Security assessment
Strengthens documentation around consent verification processes, which supports security/privacy compliance but doesn't address a specific vulnerability
Diff
diff --git a/sms-voice/latest/userguide/registrations-10dlc-register-campaign.md b/sms-voice/latest/userguide/registrations-10dlc-register-campaign.md index 9bba69ff0..a3416fc72 100644 --- a//sms-voice/latest/userguide/registrations-10dlc-register-campaign.md +++ b//sms-voice/latest/userguide/registrations-10dlc-register-campaign.md @@ -83 +83 @@ If you don't have publicly accessible links to your Company Terms & Conditions o - 6. For **Campaign opt-in screenshot -_optional_** , upload a file showing how users consent to receiving messages, as described in the **Campaign opt-in workflow** field. The supported file type are PNG, JPEG, and PDF and the maximum file size is 500KB. Additional information and examples of a compliant opt-in workflow can be found at [Obtain permission](./best-practices.html#best-practices-sms-obtain-permission). + 6. For **Campaign opt-in screenshot -_optional_** , upload a file showing how users consent to receiving messages, as described in the **Campaign opt-in workflow** field. The supported file type are PNG, JPEG, and PDF and the maximum file size is 500KB. A screenshot or mockup is required unless you provide a publicly accessible URL to your opt-in location or call-to-action in the **Campaign opt-in workflow** field. If your opt-in process requires a login, is not yet public, is a verbal opt-in, or occurs on printed forms or fliers, you must provide a screenshot or mockup showing the complete opt-in process. Additional information and examples of a compliant opt-in workflow can be found at [Obtain permission](./best-practices.html#best-practices-sms-obtain-permission).