SLIMEBALL Rocky Mountain Bank CLOSES EMAIL ACCOUNT OF INNOCENT EMAIL ACCOUNT HOLDER. | |
_Storm_
User ID: 362931 United States 09/28/2009 02:36 PM Report Abusive Post Report Copyright Violation | |
Anonymous Coward (OP) User ID: 781607 United States 09/28/2009 02:37 PM Report Abusive Post Report Copyright Violation | |
Anonymous Coward (OP) User ID: 781607 United States 09/28/2009 02:37 PM Report Abusive Post Report Copyright Violation | |
Anonymous Coward User ID: 781606 United States 09/28/2009 02:39 PM Report Abusive Post Report Copyright Violation | The Wyoming-based bank's controversial legal action follows a slip-up by one of its own staff, who sent an email containing the details of 1,300 of its customers to the GMail address in August. Anxious to minimise the fall-out from the privacy breach - the attached spreadsheet contained names, addresses, social security information and account details - the bank emailed the account again asking the recipient to delete the original message. When it received no reply, executives decided to launch legal action to have the information destroyed and to uncover whether the user had ignored their request or just failed to check their account. Google's privacy policies state that the company will not hand over account information without a court order, which Rocky Mountain Bank obtained from a judge in California last week." geez. |
_Storm_
User ID: 362931 United States 09/28/2009 02:40 PM Report Abusive Post Report Copyright Violation | Quoting: Anonymous Coward 781607 The bank should be responsible for the people whos information was sent outs credit/identity being monitored forever. |
Anonymous Coward (OP) User ID: 781607 United States 09/28/2009 02:49 PM Report Abusive Post Report Copyright Violation | The bank should be responsible for the people whos information was sent outs credit/identity being monitored forever. Quoting: _Storm_right, and 1. Though supposedly by mistake of its employee; what type of security measures has this bank undertaken for this type of mindless mistake to happen? I mean come on if this info is supposed to be send to another employee why not use a secure intranet system of the bank? Unless of course the employee was stealing customer info and the bank is covering up calling it a "mistake" instead of customer data theft! 2. Once transferred outside of the banks system only god knows where the info ends up, there are "sniffers" out on the net just looking for this type of info. 3. Why are we still using SS #s for customer account info instead of just an account #? |
_Storm_
User ID: 362931 United States 09/28/2009 04:15 PM Report Abusive Post Report Copyright Violation | |