Restriction of Data Access Sample Clauses

Restriction of Data Access. Any user’s data is stored in the data storage shared with other users, and access to the storage is restricted by the access control function of UNIX.
Restriction of Data Access. 6.5.1 While you subscribe to the Service, you may not restrict ▇▇▇▇’s access to and use of your data, except as permitted by applicable Law and as provided below.

Related to Restriction of Data Access

  • Restriction of Use The Bank may reduce the cardholder's daily spending limit or suspend use of the debit card without prior notice if the cardholder exhibits any one of the following: I. Violation against Article 5, Paragraphs 2, 3 or 4. II. The cardholder maintains insufficient balance in the direct debit account to pay for purchases for two consecutive months from the payment date. III. The cardholder declares bankruptcy or is declared bankrupt in accordance with the Bankruptcy Act, or has been blacklisted by Taiwan Clearing House. IV. The corporate entity or non-profit organization in which the cardholder serves as a legal representative, representative or manager has been blacklisted by Taiwan Clearing House, declares bankruptcy or is declared bankrupt under the Bankruptcy Act, undergoes or is forced to undergo restructuring, ceases business operations or is liquidated. V. The cardholder is sentenced for a criminal offense or has main properties seized by the court. VI. The cardholder uses the debit card for inappropriate purposes or the Bank suspects the cardholder's account to be used for inappropriate purposes. In which case the Bank may suspend or terminate use of the debit card at any time, and recover the card to have it voided. VII. The cardholder's account has been placed on alert. VIII. The cardholder is ordered by a court to be subjected to guardianship or assistance. The Bank may reduce the cardholder's daily spending limit or suspend use of the debit card without prior notice if the cardholder exhibits any one of the following: I. The cardholder violates Article 2, Paragraph 2, and the Bank is unable to establish contact using the mailing address and telephone number provided at the time of application. II. The cardholder maintains insufficient balance in the direct debit account to pay for purchases continuously for one month from the payment date. III. The cardholder violates Article 4, Paragraph 1, and attempts to use the debit card for purchases exceeding the available balance of the direct debit account. IV. The cardholder has checks returned due to insufficient deposit balance; or that the corporate entity or non-profit organization in which the cardholder is the person-in-charge, representative or manager has checks returned due to insufficient deposit balance. V. The cardholder has had credit/debit cards suspended or credit/debit card agreements terminated by other card issuers. VI. The cardholder is subjected to enforcement, provisional seizure, provisional disposition or other debt-securing measures. VII. The cardholder is sued for other debt-related disputes, or is investigated or prosecuted for criminal offense. VIII. The cardholder fails repay debts owed to the Bank (including the Bank's head office and branches), or exhibits delays in repaying principals or interests on debts owed to other creditors. IX. The cardholder fails to fulfill guarantee obligations in accordance with agreements. The Bank may reinstate cardholder's daily spending limit or use of the debit card when the situations described in Paragraphs 1 and 2 no longer apply, or if the Bank accepts the explanations provided by the cardholder, or if the cardholder settles part of the debts owed or provides suitable collaterals.

  • 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.

  • Retention of Data With regard to business transactions covered by this Agreement, Licensee must retain any records for a period of ten years starting on 1th of January of the year following the year during which the data were transmitted or otherwise transferred, or for the minimum period prescribed by applicable law, whichever is longer. In addition, Licensee must maintain current, complete and accurate reports on all of SAP’s Confidential Information in its possession or in the possession of its representatives.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.