Security Report
Email Campaign Flow
Summary
Detected
- Services:
- Permissions:
- Data Handling: pii
Undeclared
All items declared
Warnings
No warnings
Findings (15)
Compliance
GDPR undeclared "- Company address (GDPR/CAN-SPAM requirement)"
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
CAN-SPAM undeclared "- Company address (GDPR/CAN-SPAM requirement)"
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
GDPR undeclared "Write email campaign copy for the following audience segment and campaign objective. Include: 3 subj"
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
GDPR undeclared "title: GDPR Marketing Compliance"
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
GDPR undeclared "description: "Reference for GDPR compliance in email marketing""
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
GDPR undeclared "GDPR (General Data Protection Regulation) compliance requirements for email marketing activities."
This content references a regulatory or compliance framework. This is informational — no action needed unless the skrpt processes regulated data.
Data Handling
pii declared "first_name"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "first name"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "{{first_name}}"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "{{company}}"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "customer data"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "Customer data"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "customer data"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "subscriber data"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.
pii declared "subscriber data"
This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.