Monday, March 15, 2010
Yesterday we started a promotional mailing to a subset of FeedBlitz publishers to offer a special upgrade incentive. To make it more real we wrote a custom script that would show how much a publisher might save if they accepted that offer - which necessitated running the email outside of FeedBlitz's standard mechanisms and processes.
That script blew up and unfortunately shared some publisher emails with other FeedBlitz publishers. I unreservedly apologize for that and take full responsibility for this privacy breach. The mailing was stopped as soon as we discovered the problem. There was and is no issue with FeedBlitz's standard mailings used by publishers to reach their subscribers.
No subscriber list information was revealed, "only" some publisher email addresses to other publishers on the system. There was no payment or password data in the email. It was as if those affected - a subset of publishers - had been CC'd instead of BCC'd on a mail from a desktop system.
Again, I apologize for our error.
Phil
That script blew up and unfortunately shared some publisher emails with other FeedBlitz publishers. I unreservedly apologize for that and take full responsibility for this privacy breach. The mailing was stopped as soon as we discovered the problem. There was and is no issue with FeedBlitz's standard mailings used by publishers to reach their subscribers.
No subscriber list information was revealed, "only" some publisher email addresses to other publishers on the system. There was no payment or password data in the email. It was as if those affected - a subset of publishers - had been CC'd instead of BCC'd on a mail from a desktop system.
Again, I apologize for our error.
Phil
|
1 Comments:
Happens to the best of us... no harm done, I am sure.
Imran
IMRAN.TV
Post a Comment
Note: Only a member of this blog may post a comment.
<< Home