Account Application and Approval Process Sample Clauses

Account Application and Approval Process. Affiliate must complete the application accessible from the cleverbridge Affiliate Center and accept the terms and conditions of this Agreement. Affiliate must indicate the Client who’s Client Products that the Affiliate wishes to promote through the cleverbridge Affiliate Program. Affiliate must submit an application for each respective Client. Client may, in its sole discretion, approve or reject any application. cleverbridge may, in its sole discretion, approve or reject any application for no reason or any reason, including if cleverbridge considers, in its sole discretion, the Affiliate website incompatible with the cleverbridge Affiliate Program, because it promotes (a) material with explicit sexual content, violence; (b) race, sex, gender, religion, nationality, physical disability, sexual orientation and/or age discrimination; (c) illegal activities; or contains (d) materials infringing or supporting third parties to infringe intellectual property or any other applicable laws; (e) the term “cleverbridge” or the Client’s or Client Product’s name or derivations thereof; (f) typing errors in the domain name used by Affiliate; or (g) is in any way illegal, damaging, libelous, obscene, and/or aggressive. If Affiliate has been rejected, cancelled or terminated from the cleverbridge Affiliate Program subsequent to application for admission and/or admission to the cleverbridge Affiliate Program, Affiliate may not submit another such application for admission.
Sample 1
AutoNDA by SimpleDocs

Related to Account Application and Approval Process

  • E1 Authority Data E1.1 The Contractor shall not delete or remove any proprietary notices contained within or relating to the Authority Data.

  • Outage Authority and Coordination Developer and Connecting Transmission Owner may each, in accordance with NYISO procedures and Good Utility Practice and in coordination with the other Party, remove from service any of its respective Attachment Facilities or System Upgrade Facilities and System Deliverability Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency State, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to schedule such removal on a date and time mutually acceptable to both the Developer and the Connecting Transmission Owner. In all circumstances either Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Party of such removal.

  • General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.

  • Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation

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

  • Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE)when reporting on beds utilized at the Hospital. 2. Grantee shall budget and report expenditure data on the CARE Report III, incorporated by reference and posted at: xxxxx://xxx.xxx.xxxxx.xxx/doing-business-hhs/provider- portals/behavioral-health-services-providers/behavioral-health-provider- resources/community-mental-health-contracts, within the Community Hospital strategy C.2.1.1 using line 764 - Project Private Beds. 3. Grantee shall ensure that patient registration, diagnostics, admission and discharge data is reported by using the CARE screens and action codes listed below: a. Screen: Campus-Based Assignments (Add/Change/Delete), Action Code: 305; b. Screen: Campus-Based Discharge/Community Placement (Add/Change/Delete), Action Code: 310; c. Screen: Joint Community Support Plan (Add/Change/Delete), Action Code: 312; d. Screen: Register Client, Action Code: 325; e. Screen: Diagnostics (Add/Change/Delete), Action Code: 330; f. Screen: Voluntary Admission and Commitment (Add/Change/Delete), Action Code 332; g. Screen: Campus-Based Residential Xxxx/Dorm (Add/Change/Delete), Action Code 615; and h. Screen: MH Bed Allocation Exception (Add/Change/Delete), Action Code 345. For details related to the use of these screens and action codes, Grantee can refer to the CARE Reference Manual which can be found under the CARE (WebCARE) section on the portal at: xxxxx://xxxxxxxxx.xxx.xxxxx.xx.xx/helpGuide/Content/16_CARE/CAREWebCARE%20Refere nce%20Manual.htm

  • Scope and Application This Appendix will apply to all work undertaken within the Employer’s Workshop(s) by employees mainly engaged at the Workshop.

  • Authorization and Application of Overtime An employee who is required to work overtime shall be entitled to overtime compensation when the overtime worked is authorized in advance.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Purpose and Application This document (“DPA”) is incorporated into the Agreement and forms part of a written (including in electronic form) contract between SAP and Customer. This DPA applies to Personal Data processed by SAP and its Subprocessors in connection with its provision of the Cloud Service. This DPA does not apply to non-production environments of the Cloud Service if such environments are made available by SAP, and Customer shall not store Personal Data in such environments.

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