Emergency Contact Information Resident must complete and provide to University an emergency contact information form provided by University Housing before Resident will be allowed to move into the Residence Facility.
Periodic Update of Contact Information The District shall provide CSEA with a list of all bargaining unit members’ names and contact information on the last working day of, January, May, and September. The information will be provided to CSEA via electronic mail. This contact information shall also include the following information, with each field listed in its own column:
How Do I Get More Information? For more information, including the full Notice, Claim Forms and Settlement Agreement go to xxx.xxxxxxxxxxxxxxxxxxxx.xxx, contact the settlement administrator at 0-000-000-0000, or call Class Counsel at 1-866-354-3015. Exhibit E UNITED STATES DISTRICT COURT FOR THE SOUTHERN DISTRICT OF FLORIDA Xxxxx v. AvMed, Inc., Case No. 10-cv-24513 If You Paid for or Received Insurance from AvMed, Inc. at Any Time Through December of 2009, You May Be Part of a Class Action Settlement. IMPORTANT: PLEASE READ THIS NOTICE CAREFULLY. THIS NOTICE RELATES TO THE PENDENCY OF A CLASS ACTION LAWSUIT AND, IF YOU ARE A MEMBER OF THE SETTLEMENT CLASSES, CONTAINS IMPORTANT INFORMATION ABOUT YOUR RIGHTS TO MAKE A CLAIM UNDER THE SETTLEMENT OR TO OBJECT TO THE SETTLEMENT (A federal court authorized this notice. It is not a solicitation from a lawyer.) Your legal rights are affected whether or not you act. Please read this notice carefully. YOUR LEGAL RIGHTS AND OPTIONS IN THIS SETTLEMENT SUBMIT A CLAIM FORM This is the only way to receive a payment. EXCLUDE YOURSELF You will receive no benefits, but you will retain any rights you currently have to xxx the Defendant about the claims in this case. OBJECT Write to the Court explaining why you don’t like the Settlement. GO TO THE HEARING Ask to speak in Court about your opinion of the Settlement. DO NOTHING You won’t get a share of the Settlement benefits and will give up your rights to xxx the Defendant about the claims in this case. These rights and options – and the deadlines to exercise them – are explained in this Notice. QUESTIONS? CALL 0-000-000-0000 TOLL FREE, OR VISIT XXX.XXXXXXXXXXXXXXXXXXXX.XXX PARA UNA NOTIFICACIÓN EN ESPAÑOL, LLAMAR O VISITAR NUESTRO WEBSITE BASIC INFORMATION
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Business Contact Information Each party consents to the other party using its Business Contact Information for contract management, payment processing, service offering, and business development purposes related to the Agreement and such other purposes as set out in the using party’s global data privacy policy (copies of which shall be made available upon request). For such purposes, and notwithstanding anything else set forth in the Agreement with respect to Client Personal Information in general, each party shall be considered a data controller with respect to the other party’s Business Contact Information and shall be entitled to transfer such information to any country where such party’s global organization operates. EXHIBIT A DEFINITIONS
DNS name server availability Refers to the ability of a public-‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.
DOES THE SPR NEED TO BE UPDATED IF INFORMATION CHANGES Yes. It remains a continuing obligation of the principal or his/her authorized agent to update the SPR whenever any of the information provided on the initial form changes. WHERE DO THE SPR AND ANY UPDATES NEED TO BE FILED? The SPR needs to be filed with the County Department or County Division processing the application or matter. If and when an additional expenditure is incurred subsequent to the initial filing of the SPR, an amended SPR needs to be filed with the County Department or County Division where the original application, including the initial SPR, was filed. WHEN DO THE SPR AND ANY UPDATES NEED TO BE FILED? In most cases, the initial SPR needs to be filed with the other application forms. The SPR and any update must be filed with the appropriate County Department or County Division not less than seven (7) days prior to the BCC hearing date so that they may be incorporated into the BCC agenda packet. (See Section 2-354(b), Orange County Code.) When the matter is a discussion agenda item or is the subject of a public hearing, and any additional expenditure occurs less than 7 days prior to BCC meeting date or updated information is not included in the BCC agenda packet, the principal or his/her authorized agent is obligated to verbally present the updated information to the BCC when the agenda item is heard or the public hearing is held. When the matter is a consent agenda item and an update has not been made at least 7 days prior to the BCC meeting or the update is not included in the BCC agenda packet, the item will be pulled from the consent agenda to be considered at a future meeting.
Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
