If you’re working in the email space, everything is “CAN-SPAM compliant.” But does it make any sense to say, “I had a CAN-SPAM compliant dinner last night”?
No? I didn’t think so either.
But what makes an email database “CAN-SPAM compliant?” I came across a press release wherein the company purports to offer “more than 50 additional healthcare marketing databases. All email databases are CAN/SPAM compliant.”1
So, what exactly makes a database “CAN-SPAM compliant”?
I suspect that it means that all of the addresses were gained from some other method than scraping websites.
Footnotes
- Susan Duensing, Newly Updated for 2008: Expanded Physician E Mail Contacts from Direct Medical Data Unique and Multiple Location Contacts from AMA and Proprietary Database, PRWeb (2008), https://web.archive.org/web/20080607083209/http://www.prweb.com/releases/2008/06/prweb991314.htm (last visited Jun 4, 2008). ↩︎
About the Author
Mickey Chandler is a Consultant & Attorney with over 28 years of experience in Email Deliverability & Privacy Law. He has a strong background in email authentication infrastructure (SPF, DKIM, DMARC), ISP and mailbox provider relations, anti-spam policy and compliance, CAN-SPAM and state anti-spam law gained through overseeing the Abuse & Compliance team at Salesforce Marketing Cloud, originating the ISP relations role at Informz (now part of Higher Logic), and working in the fight against spam since 1997. He holds a B.A. in Government, a B.S. in Computer Information Systems, and a J.D. from the University of Houston Law Center. He is a certified CIPP/US professional and a certified CIPM professional.
