Access IDs and Passcodes Sample Clauses

Access IDs and Passcodes. One of the main security features protecting the Internet Banking Service is the unique combination of your Access ID and Passcode. During the enrollment process, you will be asked to select a unique Access ID and Passcode. For security purposes, do not use your account number or social security number as your Access ID. Encryption and access controls are used to protect your Passcode within our database. If you need to reset your Passcode, you may use our online automated Passcode reset feature or you may contact this Institution for assistance. Because your Passcode is used to access your accounts, you should treat it as you would any other sensitive personal data. • You should carefully select a Passcode that is difficult to guess. • You should NOT use words based on your name, address or other personal information. • Passcodes should not be shared with anyone, even Authorized Users. • Do NOT use dictionary words. • Keep your Passcode safe. • Memorize your Passcode and do NOT write it down. • You will be prompted to change your password every six (6) months When you enroll for the Internet Banking Service you agree to change your Passcode immediately if you suspect that your Passcode has been compromised. This can be done at any time from the User Services menu after you log on to the Internet Banking Service. NEITHER THIS INSTITUTION NOR ITS SERVICE PROVIDERS WILL CONTACT YOU BY TELEPHONE, EMAIL OR TEXT MESSAGING REQUESTING PERSONAL INFORMATION, SUCH AS YOUR ACCESS ID, PASSCODE, CREDIT CARD NUMBER, ATM CARD NUMBER OR ATM PIN. IF YOU ARE CONTACTED BY ANYONE REQUESTING THIS TYPE OF INFORMATION, DO NOT PROVIDE ANY INFORMATION AND CONTACT OUR CUSTOMER SERVICE DEPARTMENT IMMEDIATELY.
AutoNDA by SimpleDocs

Related to Access IDs and Passcodes

  • User IDs and Password Controls All users must be issued a unique user name for accessing DHCS PHI or PI. Username must be promptly disabled, deleted, or the password changed upon the transfer or termination of an employee with knowledge of the password, at maximum within 24 hours. Passwords are not to be shared. Passwords must be at least eight characters and must be a non-dictionary word. Passwords must not be stored in readable format on the computer. Passwords must be changed every 90 days, preferably every 60 days. Passwords must be changed if revealed or compromised. Passwords must be composed of characters from at least three of the following four groups from the standard keyboard: • Upper case letters (A-Z) • Lower case letters (a-z) • Arabic numerals (0-9) • Non-alphanumeric characters (punctuation symbols)

  • Usernames and Passwords 1. Staff will not share usernames and passwords with anyone, including supervisors and technical support staff.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Use of information, data and software In the event that you receive any data, information or software via the Trading Platform other than that which you are entitled to receive pursuant to this Client Agreement, you will immediately notify us and will not use, in any way whatsoever, such data, information or software.

  • Accessibility of Information Technology Contractor represents and warrants that any software/ hardware/ communications system/ equipment (collectively “technology”), if any, provided under this Agreement adheres to the standards and/or specifications as may be set forth in the Section 508 of the Rehabilitation Act of 1973 standards guide and is fully compliant with WCAG 2.0 AA standards for accessibility and compliant with any applicable FCC regulations. Technology that will be used on a mobile device must also be navigable with Voiceover on iOS devices in addition to meeting WCAG 2.0 level AA. If portions of the technology or user experience are alleged to be non-compliant or non- accessible at any point, District will provide Contractor with notice of such allegation and Contractor shall use its best efforts to make the technology compliant and accessible. If a state or federal department, office or regulatory agency, or if any other third party administrative agency or organization (“Claimants”), make a claim, allegation, initiates legal or regulatory process, or if a court finds or otherwise determines that technology is non-compliant or non-accessible, Contractor shall indemnify, defend and hold harmless the District from and against any and all such claims, allegations, liabilities, damages, penalties, fees, costs (including but not limited to reasonable attorneys’ fees), arising out of or related to Xxxxxxxxx’ claims. Contractor shall also fully indemnify District for the full cost of any user accommodation that is found to be necessary due to an identifiable lack of accessibility in the Contractor’s technology. If necessary, an independent 3rd party accessibility firm using POUR standards (Perceivable, Operable, Understandable and Robust) may be used to validate the accessibility of the technology.

  • User ID and Password You will be assigned a personal User ID and a Password that you will use to obtain access to the Online Banking. You authorize us to follow any instructions entered through the Service using your User ID and Password. Because your User ID and Password can be used to access your Accounts and to access information about these Accounts, you should treat your User ID and Password with the same degree of care and secrecy that you use to protect your ATM security code and other sensitive financial data. We may ask you to change your User ID and Password from time to time for security reasons. You agree not to use any language that is abusive, harassing, libelous, defamatory, obscene, or threatening when defining your Password or any other personalization of your Accounts.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Access to Customer Data You agree that we may, for the purposes of providing Maintenance and Customer Support and/or for the purpose of otherwise protecting the integrity of the Software, access and/or download your Customer Data on a limited basis.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!