To and CC mailings disclose recipients' email addresses to one another
Source references: 3The Skill's core behavior places multiple addresses in To and CC, and its example puts two attendee groups into those visible fields. The documentation itself acknowledges that this would typically breach privacy. BCC addresses are normally hidden, so this risk concerns addresses placed in To or CC.
Customers, attendees, or other users who should not know one another's identities may see each other's email addresses and group membership, potentially causing privacy complaints or compliance issues.
The documentation explicitly says recipients can see the other recipients and calls this a typical privacy breach. The example passes confirmed and tentative attendee arrays into the visible To and CC fields, while BCC is empty. If those arrays contain different users, sending would disclose their email addresses to one another. Users should limit this to groups that consent to address sharing or ask for per-recipient/BCC delivery.
This skill adds support for sending emails with multiple `to`, `cc`, and `bcc` recipients. Not suitable for bulk service emails (recipients see each other).Show 2 other places
- This should NOT be used for sending service emails to multiple users because each recipient will see all the other recipients listed which would typically be a breach of user privacy. ) : async () { let result = await EmailClient.sendRawEmail( "no-reply", confirmedAttendeeEmails, tentativeAttendeeEmails, [], meetingSubject,