Common use of User Passwords Clause in Contracts

User Passwords. If your Application runs as a "client" on a computer or mobile device owned by an Direct Transfer user, you: (i) may not store the user's password on that device without consent from the user; (ii) may not transmit or store that password to any system other than the Direct Transfer service; (iii) must protect the password using the standard protection mechanism for the platform (the password MUST NOT be stored in cleartext); and (iv) must provide a mechanism for the user to log out, which must completely remove the username and password from your application and its persistent storage. If your Application runs as an Internet service on a multi-user server, you must not ask for, view, store or cache the sign-in name or password of Direct Transfer user accounts. Authorization to access the user's account is only permitted via the "web service" authentication scheme in the API.

User Passwords. If your Application runs as a "“client" ” on a computer or mobile device owned by an a Direct Transfer user, you: (i) may not store the user's ’s password on that device without consent from the user; (ii) may not transmit or store that password to any system other than the Direct Transfer service; (iii) must protect the password using the standard protection mechanism for the platform (the password MUST NOT be stored in cleartext); and (iv) must provide a mechanism for the user to log out, which must completely remove the username and password from your application and its persistent storage. If your Application runs as an Internet service on a multi-user server, you must not ask for, view, store or cache the sign-in name or password of Direct Transfer user accounts. Authorization to access the user's ’s account is only permitted via the "“web service" ” authentication scheme in the API.

User Passwords. If your Application runs as a "client" on a computer or mobile device owned by an a Direct Transfer user, you: (i) may not store the user's password on that device without consent from the user; (ii) may not transmit or store that password to any system other than the Direct Transfer servicePlatform; (iii) must protect the password using the standard protection mechanism for the platform (the password MUST NOT be stored in cleartext); and (iv) must provide a mechanism for the user to log out, which must completely remove the username and password from your application and its persistent storage. If your Application runs as an Internet service on a multi-user server, you must not ask for, view, store or cache the sign-in name or password of Direct Transfer user accounts. Authorization to access the user's account is only permitted via the "web service" authentication scheme in the API.

User Passwords. If your Application runs as a "client" on a computer or mobile device owned by an a Direct Transfer user, you: (i) may not store the user's password on that device without consent from the user; (ii) may not transmit or store that password to any system other than the Direct Transfer service; (iii) must protect the password using the standard protection mechanism for the platform (the password MUST NOT be stored in cleartext); and (iv) must provide a mechanism for the user to log out, which must completely remove the username and password from your application and its persistent storage. If your Application runs as an Internet service on a multi-user server, you must not ask for, view, store or cache the sign-in name or password of Direct Transfer user accounts. Authorization to access the user's account is only permitted via the "web service" authentication scheme in the API.