Use of Customer Statements The Contractor shall not use any statement attributable to the Customer or its employees for the Contractor’s promotions, press releases, publicity releases, marketing, corporate communications, or other similar communications, without first notifying the Customer’s Contract Manager and securing the Customer’s prior written consent.
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Talk America’s data from BellSouth’s data, the following shall apply:
(1) Talk America will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Talk America’s End User accounts which are resident in LIDB pursuant to this Agreement. Talk America authorizes BellSouth to place such charges on Talk America’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls.
(2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge.
(3) Talk America shall have the responsibility to render a billing statement to its End Users for these charges, but Talk America shall pay BellSouth for the charges billed regardless of whether Talk America collects from Talk America’s End Users.
(4) BellSouth shall have no obligation to become involved in any disputes between Talk America and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Talk America. It shall be the responsibility of Talk America and the B&C Customers to negotiate and arrange for any appropriate adjustments.
LIST OF SUB-PROCESSORS The controller has authorised the use of the following sub-processors:
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.
Submission of Grievance Information a. Upon appointment of the arbitrator, the appealing party shall, within five (5) days after notice of appointment, forward to the arbitrator, with a copy to the School Board, the submission of the grievance which shall include the following:
1. The issues involved.
2. Statement of the facts.
3. Position of the grievant.
4. The written documents relating to Section 5 of the grievance procedure.
