Use contact and automation tools with permission
Only send lawful, relevant communication from an identity you are authorized to use. Product quotas are safety ceilings, not permission to contact someone.
Protect recipients and their choices
Do not use scraped or purchased prospects as an assumed permission source, conceal sender identity, evade opt-outs or rotate mailboxes to evade a limit. Record your source and permission assessment. Imports, merges and archiving must not erase suppression. Honor replies, complaints, hard bounces and provider restrictions before another send.
Keep messages and files safe
Do not send malware, phishing, fraudulent invoices, harassment, unlawful material or another person’s private information without authority. Do not bypass file quarantine or place active scripts in templates. Avoid sending passwords, card details or API secrets through support or chat.
Use integrations within their granted scope
Do not share private mailboxes without their owner’s consent, probe another tenant’s records or use webhooks to access private networks. Keep API keys scoped and revoke unused access. Automated acknowledgements must be visibly attributed and must not impersonate human approval.
Respond to safety holds
A hold or paused connection is a reason to review the stated issue, not move traffic to a different sender. Unknown send outcomes need reconciliation. Necessary transaction notices are not a route for relabeling promotional material to bypass marketing suppression.
Primary-source references
External providers maintain their own requirements; consult the linked documentation for their current details.