Master Opt Out File Sample Clauses

Master Opt Out File which shall list a) all consumers who opted out after receiving an Opt Out notice, but prior to enrollment and b) all consumers that have left the program for any reason after they were enrolled;
AutoNDA by SimpleDocs
Master Opt Out File. This File shall be updated monthly by the Competitive Supplier and shall include Information, as described in Table 1 below, regarding any consumer that opted out of the aggregation after receiving an opt out notice but prior to enrollment, as well as any consumer that enrolled in the aggregation and then left the aggregation for any reason, and shall be provided no later than 10 Business Days following the close of any LDC Read Month.
Master Opt Out File. A list of consumers that opted out of the aggregation program after receiving an opt out notice but prior to enrollment and a list of consumers that enrolled in the aggregation program and then left the program for any reason. The Competitive Supplier shall provide this list 10-business day after the close of any LDC Read Month.
Master Opt Out File. A list of a) all consumers in the Municipality that opted out prior to enrollment and after receiving an Opt-Out Notice and b) all Participating Consumers that left the program for any reason after they were enrolled in the Program. This Master Opt-Out File will also include any records of customers that have opted-out during previous ESAs, which will be provided to Competitive Supplier by the Municipality. The report shall include all customer identifying information provided by the Local Distributor and (i) Opt-Out Notice mailing date (if applicable) and (ii) opt-out date.
Master Opt Out File. A quarterly report of consumers that opted out of the aggregation program after receiving an opt out notice but prior to enrollment and a list of consumers that enrolled in the aggregation program and then left the program for any reason. Competitive Supplier shall provide this list within thirty (30) days after the close of each quarter (March 31, June 30, September 30, and December 31) or within ten (10) business days of a written request by the Municipality.
Master Opt Out File. A list of (a) all consumers in the Municipality that opted out of the aggregation program after receiving an opt out notice but prior to enrollment and a list of consumers that enrolled in the aggregation program and thenafter receiving an Opt-Out Notice and (b) all Participating Customers that left the program for any reason. Competitive Supplier shall provide this list 10-business day after the close ofthey were enrolled in the Program. This Master Opt-Out File will also include any records of customers that have opted-out during previous ESAs, which will be provided to Competitive Supplier by the Municipality. The report shall include all customer identifying information provided by the Local Distributor Read Month.and (i) Opt-Out Notice mailing date (if applicable) and (ii) opt-out date.

Related to Master Opt Out File

  • Collateral Records Such Grantor will maintain complete and accurate books and records with respect to the Collateral owned by it, and furnish to the Collateral Agent, with sufficient copies for each of the Secured Parties, such reports relating to such Collateral as the Collateral Agent shall from time to time request.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

Time is Money Join Law Insider Premium to draft better contracts faster.