Data Protection Rights of the Player Sample Clauses

Data Protection Rights of the Player. The Player will have a right to access (Art. 15 GDPR), a right to rectification (Art. 16 GDPR), a right of removal (Art. 17 GDPR), a right to restriction of processing (Art. 18 GDPR), a right to data portability (Art. 20 GDPR), as well as a right to object to processing (Art. 21 GDPR) by sending a postal communication to the address indicated above or by writing an e-mail to (include Club DPO mail address). In any case, the Player can file a complaint before the competent data protection authority.
AutoNDA by SimpleDocs

Related to Data Protection Rights of the Player

  • RIGHTS OF THE UNION Section 4.1 The Union has the right and responsibility to represent the interests of all employees in the unit; to present its views to the District on matters of concern, and to enter collective negotiations with the object of reaching an agreement applicable to all employees within the unit, except that by such obligation neither party shall be compelled to agree to a proposal or be required to make a concession. Section 4.2 The Union shall promptly be notified by the District of any formal grievance of any employee in the unit in accordance with the provisions of the Discharge and Grievance articles contained herein. The Union is entitled to have an observer at hearings conducted by any District official or body arising out of a grievance and to make known the Union's views concerning the case. Section 4.3 The Employer, as part of the general orientation of each new employee within the unit subject to this Agreement, shall make available to each employee, a copy of this Agreement. Section 4.4 The President of the Union and/or the President's representatives will be provided time off without loss of pay to a maximum of twenty-five days (25) days total per year, to be used at the discretion of the executive board. The leave will be granted for the President and the Union representatives to attend regional or state meetings when the purpose of these meetings. Additional release days may be granted. The Union will reimburse the District for the cost of any required substitute. Such use shall not interfere with District operations. 4.4.1 Upon return from such leave, the employee will be returned to the position previously held. 4.4.2 All seniority rights for such employee shall be retained and accrued. Section 4.5 The names of employees in the respective unit will be made available to the President of the Union upon request. On or before the first day of October of each year during the term of this Agreement, the District shall provide the Union with information regarding each employee in the bargaining unit on a form to be provided by the Union. Upon request the information shall be supplemented and revised quarterly. Employee information given to the Union shall be used solely for the purpose of union business. Section 4.6 The Union reserves and retains the right to delegate any Union right or duty contained herein to appropriate officials of the American Federation of Teachers Union of Washington. Section 4.7 Visitation rights shall be granted to the designated representative of the Union to visit employees in the unit for the purpose of grievance procedures and/or general information data. This excludes recruitment during working hours. The union representative shall notify his/her immediate supervisor and the building office (for employees assigned to a school site regularly or for the day) before leaving the assigned worksite and shall notify the building office upon arrival. For any union representative working in Maintenance, the representative shall notify his/her lead and the Maintenance Supervisor. Union meetings may be held during working hours with prior approval of the Superintendent or designee.

  • Cybersecurity; Data Protection To the Company’s knowledge, the Company and its subsidiaries’ information technology assets and equipment, computers, systems, networks, hardware, software, websites, applications, and databases (collectively, “IT Systems”) are adequate for, and operate and perform in all material respects as required in connection with the operation of the business of the Company and its subsidiaries as currently conducted, free and clear of all material bugs, errors, defects, Trojan horses, time bombs, malware and other corruptants. The Company and its subsidiaries have implemented and maintained commercially reasonable controls, policies, procedures, and safeguards to maintain and protect their material confidential information and the integrity, continuous operation, redundancy and security of all IT Systems and data (including all personal, personally identifiable, sensitive, confidential or regulated data (collectively, the “Personal Data”)) used in connection with their businesses, and there have been no breaches, violations, outages or unauthorized uses of or accesses to same, except for those that have been remedied without cost or liability or the duty to notify any other person, nor any incidents under internal review or investigations relating to the same, except in each case as would not reasonably be expected to have a Material Adverse Effect. The Company and its subsidiaries are presently in material compliance with all applicable laws or statutes and all judgments, orders, rules and regulations of any court or arbitrator or governmental or regulatory authority, internal policies and contractual obligations relating to the privacy and security of IT Systems and Personal Data and to the protection of such IT Systems and Personal Data from unauthorized use, access, misappropriation or modification.

  • Third-Party Information; Privacy or Data Protection Laws Each Party acknowledges that it and its respective Subsidiaries may presently have and, after the Effective Time, may gain access to or possession of confidential or proprietary Information of, or personal Information relating to, Third Parties: (i) that was received under confidentiality or non-disclosure agreements entered into between such Third Parties, on the one hand, and the other Party or the other Party’s Subsidiaries, on the other hand, prior to the Effective Time or (ii) that, as between the two parties, was originally collected by the other Party or the other Party’s Subsidiaries and that may be subject to and protected by privacy, data protection or other applicable Laws. Each Party agrees that it shall hold, protect and use, and shall cause its Subsidiaries and its and their respective Representatives to hold, protect and use, in strict confidence the confidential and proprietary Information of, or personal Information relating to, Third Parties in accordance with privacy, data protection or other applicable Laws and the terms of any agreements that were either entered into before the Effective Time or affirmative commitments or representations that were made before the Effective Time by, between or among the other Party or the other Party’s Subsidiaries, on the one hand, and such Third Parties, on the other hand.

  • Rights of Use of the results and of pre-existing rights by the NA and the Union (a) for its own purposes and in particular to make available to persons working for the NA, Union institutions, agencies and bodies and to Member States’ institutions, as well as to copy and reproduce in whole or in part and in an unlimited number of copies." For the rest of this article, the references to the "Union" must be read as reference to "the NA and/or the Union".

  • Rights Protection Mechanisms and Abuse Mitigation ­‐ Registry Operator commits to implementing and performing the following protections for the TLD: i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits). ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary. iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions. iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period. v. Bind registrants to terms of use that define and prohibit illegal or abusive activity. vi. Limit the use of proxy and privacy registration services in cases of malfeasance. vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-­‐compliance with the terms of the Registrar Accreditation Agreement. viii. Registry Operator will be properly resourced to perform these protections.

  • Rights of the Parties Nothing expressed or implied in this Agreement is intended or will be construed to confer upon or give any Person other than the parties hereto any rights or remedies under or by reason of this Agreement or any transaction contemplated hereby.

  • Certain Rights of the Depositary; Limitations Subject to the further terms and provisions of this Article (23), the Depositary, its Affiliates and their agents, on their own behalf, may own and deal in any class of securities of the Company and its Affiliates and in ADSs. The Depositary may issue ADSs against evidence of rights to receive Shares from the Company, any agent of the Company or any custodian, registrar, transfer agent, clearing agency or other entity involved in ownership or transaction records in respect of the Shares. Such evidence of rights shall consist of written blanket or specific guarantees of ownership of Shares furnished on behalf of the holder thereof. In its capacity as Depositary, the Depositary shall not lend Shares or ADSs; provided, however, that the Depositary may (i) issue ADSs prior to the receipt of Shares pursuant to Section 2.3 of the Deposit Agreement and (ii) deliver Shares prior to the receipt and cancellation of ADSs which were issued under (i) above but for which Shares may not yet have been received (each such transaction a “Pre-Release Transaction”). The Depositary may receive ADSs in lieu of Shares under (i) above and receive shares in lieu of ADSs under (ii) above. Each such Pre-Release Transaction will be (a) accompanied by or subject to a written agreement whereby the person or entity (the “Applicant”) to whom ADSs or Shares are to be delivered (1) represents that at the time of the Pre-Release Transaction the Applicant or its customer owns the Shares or ADSs that are to be delivered by the Applicant under such Pre-Release Transaction, (2) agrees to indicate the Depositary as owner of such Shares or ADSs in its records and to hold such Shares or ADSs in trust for the Depositary until such Shares or ADSs are delivered to the Depositary or the Custodian, (3) unconditionally guarantees to deliver to the Depositary or the Custodian, as applicable, such Shares or ADSs and (4) agrees to any additional restrictions or requirements that the Depositary deems appropriate, (b) at all times fully collateralized with cash, United States government securities or such other collateral as the Depositary deems appropriate, (c) terminable by the Depositary on not more than five business days’ notice (save for a prescribed termination event in which case any such Pre-Release Transaction may be immediately terminable by the Depositary) and (d) subject to such further indemnities and credit regulations as the Depositary deems appropriate. The Depositary will normally limit the number of ADSs and Shares involved in such Pre-Release Transactions at any one time to 30% of the ADSs outstanding (without giving effect to ADSs outstanding pursuant to any Pre-Release Transaction under (i) above), provided, however, that the Depositary reserves the right to change or disregard such limit from time to time as it deems appropriate. The Depositary may also set limits with respect to the number of ADSs and Shares involved in Pre-Release Transactions with any one person on a case by case basis as it deems appropriate. The Depositary may retain for its own account any compensation received by it in conjunction with the foregoing. Collateral provided pursuant to (b) above, but not the earnings thereon, shall be held for the benefit of the Holders (other than the Applicant).

  • PERSONAL DATA PROTECTION ACT 7.1. PAH is committed to protecting the privacy, confidentiality and security of all personal data to which it is entrusted. It has been our policy to ensure your personal information are protected. With the introduction of the Malaysian Personal Data Protection Act 2010 ("PDPA"), we are even committed to ensure the privacy and confidentiality and security of all personal data are protected in line with the PDPA. We process personal data which you have provided to us voluntarily through our website upon your registration and this includes personal data such as your name, address, NRIC and contact details. In this regards, you have expressly consent to our processing of your personal data. If you give us personal data or information about another person, you must first confirm that he/she has appointed you to act for him/her, to consent to the processing of his/her personal data and to receive on his/her behalf any data protection notices. We may request your assistance to procure the consent of such persons whose personal data is provided by you to us and you agree to do so. You shall indemnify us in the event we suffer loss and damage as a result of your failure to comply with the same. We will only retain your personal data for as long as necessary for the fulfilment of the specified purposes or as legislated 7.2. E-Bidders shall be responsible for the confidentiality and use of password and not to reveal the password to anyone at any time and under any circumstances whether intentionally or unintentionally. 7.3. E-Bidders agree to comply with all the security measures related to safety of the password or generally in respect of the use of the service. In the event that the password is compromised, the E-Bidders shall immediately notify PAH.

  • Rights Protection Mechanisms Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the registry-­‐registrar agreement entered into by ICANN-­‐accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-­‐requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-­‐

  • Protection of Legal Rights of Third Parties Registry Operator must specify, and comply with, the processes and procedures for launch of the TLD and initial registration-­‐related and ongoing protection of the legal rights of third parties as set forth Specification 7 attached hereto (“Specification 7”). Registry Operator may, at its election, implement additional protections of the legal rights of third parties. Any changes or modifications to the process and procedures required by Specification 7 following the Effective Date must be approved in advance by ICANN in writing. Registry Operator must comply with all remedies imposed by ICANN pursuant to Section 2 of Specification 7, subject to Registry Operator’s right to challenge such remedies as set forth in the applicable procedure described therein. Registry Operator shall take reasonable steps to investigate and respond to any reports from law enforcement and governmental and quasi-­‐governmental agencies of illegal conduct in connection with the use of the TLD. In responding to such reports, Registry Operator will not be required to take any action in contravention of applicable law.

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