Re: Conflict of legal requirements ?
"The thing some companies fail to grasp is that just because they have the data for reason a, doesn't mean they can use it for reason b."
One way would be to have separate databases for a & b. It would avoids that category of error. Unfortunately it introduces a new one, that of keeping one of those databases up to date. The database that's used for trading needs to have its names and addresses up to date, the marketing database may well rot in isolation. However there's an effective solution: throw away the marketing database and add value to the business by stopping pissing off customers with unwanted mailshots and spam.
Biting the hand that feeds IT
