INTRODUCTION TO YOUR SUBSCRIBER AGREEMENT Thank you for choosing Blue Cross & Blue Shield of Rhode Island (BCBSRI) for your healthcare coverage. We appreciate the trust you’ve placed in us and want to help you make the most of your health plan. In this Subscriber Agreement (agreement), you’ll find valuable information about your • how your health coverage works; • how BCBSRI processes claims for the health services you receive; • your rights and responsibilities as a BCBSRI member; • BCBSRI’s rights and responsibilities; and • tools and programs to help you stay healthy and save money. We encourage you to read this agreement to learn about all the advantages of being a BCBSRI member. Below are some helpful tips on how to find what you need in this agreement. • As a member, you are responsible for understanding the benefits to which you are entitled under this agreement and the rules you must follow to receive those benefits. • The Table of Contents will help you find the order of the sections as they appear in the agreement. • The Summary of Benefits, included in this agreement, shows the amount you pay out of your own pocket. • Important contact information, such as, telephone numbers, addresses, and websites are located at the end of this document. • Some words and phrases used in this agreement are in italics. This means that the words or phrases have a special meaning as they relate to your healthcare coverage. Please see Section 8 for definitions of these words. • When we use the words “we,” “us,” and “our,” we are referring to BCBSRI. When we use the words “you” and “your” we are referring to the enrolled subscriber and/or member. These words are also defined in the Glossary. • Many sections of this document are related to other sections. You may need to reference more than one section to find the information you need.
Purchase Order Number NETAPP's purchase order number must appear on all invoices, packing lists and bills of lading and shall appear on each package, container or envelope on each shipment made pursuant to such purchase order.
Indemnification for Marketing Materials In addition to the foregoing indemnification, the Fund and the Investment Adviser also, jointly and severally, agree to indemnify and hold harmless each Underwriter, affiliates, directors, officers, employees and agents of each Underwriter, and each person, if any, who controls any Underwriter within the meaning of Section 15 of the 1933 Act or Section 20 of the 1934 Act, against any and all loss, liability, claim, damage and expense described in the indemnity contained in Section 6(a), as limited by the proviso set forth therein, with respect to any sales material.
SUBLICENSING AND ASSIGNMENT Controlled Affiliate shall not, directly or indirectly, sublicense, transfer, hypothecate, sell, encumber or mortgage, by operation of law or otherwise, the rights granted hereunder and any such act shall be voidable at the sole option of Plan or BCBSA. This Agreement and all rights and duties hereunder are personal to Controlled Affiliate.
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.
Detailed Sales Data Contractor shall also report detailed sales data by: (1) state; (2) entity/customer type, e.g. local government, higher education, K12, non-profit; (3) Purchasing Entity name; (4) Purchasing Entity bill-to and ship-to locations; (4) Purchasing Entity and Contractor Purchase Order identifier/number(s); (5) Purchase Order Type (e.g. sales order, credit, return, upgrade, determined by industry practices);
Court Ordered Requests for Call Detail Records and Other Subscriber Information 7.1 To the extent technically feasible, BellSouth maintains call detail records for Mpower end users for limited time periods and can respond to subpoenas and court ordered requests for this information. BellSouth shall maintain such information for Mpower end users for the same length of time it maintains such information for its own end users. 7.2 Mpower agrees that BellSouth will respond to subpoenas and court ordered requests delivered directly to BellSouth for the purpose of providing call detail records when the targeted telephone numbers belong to Mpower end users. Billing for such requests will be generated by BellSouth and directed to the law enforcement agency initiating the request. 7.3 Where BellSouth is providing to Mpower telecommunications services for resale or providing to Mpower the local switching function, then Mpower agrees that in those cases where Mpower receives subpoenas or court ordered requests regarding targeted telephone numbers belonging to Mpower end users, if Mpower does not have the requested information, Mpower will advise the law enforcement agency initiating the request to redirect the subpoena or court ordered request to BellSouth. Where the request has been forwarded to BellSouth, billing for call detail information will be generated by BellSouth and directed to the law enforcement agency initiating the request. 7.4 In all other instances, Mpower will provide Mpower end user and/or other customer information that is available to Mpower in response to subpoenas and court orders for their own customer records. When BellSouth receives subpoenas or court ordered requests regarding targeted telephone numbers belonging to Mpower end users, BellSouth will advise the law enforcement agency initiating the request to redirect the subpoena or court ordered request to Mpower.
Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Indemnification and Assumption of Risk – Vendor Data VENDOR AGREES THAT IT IS VOLUNTARILY PROVIDING DATA (INCLUDING BUT NOT LIMITED TO: VENDOR INFORMATION, VENDOR DOCUMENTATION, VENDOR’S PROPOSALS, VENDOR PRICING SUBMITTED OR PROVIDED TO TIPS, TIPS CONTRACT DOCUMENTS, TIPS CORRESPONDENCE, VENDOR LOGOS AND IMAGES, VENDOR’S CONTACT INFORMATION, VENDOR’S BROCHURES AND COMMERCIAL INFORMATION, VENDOR’S FINANCIAL INFORMATION, VENDOR’S CERTIFICATIONS, AND ANY OTHER VENDOR INFORMATION OR DOCUMENTATION, INCLUDING WITHOUT LIMITATION SOFTWARE AND SOURCE CODE UTILIZED BY VENDOR, SUBMITTED TO TIPS BY VENDOR AND ITS AGENTS) (“VENDOR DATA”) TO TIPS. FOR THE SAKE OF CLARITY, AND WITHOUT LIMITING THE BREADTH OF THE INDEMNITY OBLIGATIONS IN SECTION 14 ABOVE, VENDOR AGREES TO PROTECT, INDEMNIFY, AND HOLD THE TIPS INDEMNITEES HARMLESS FROM AND AGAINST ANY AND ALL LOSSES, CLAIMS, ACTIONS, DEMANDS, ALLEGATIONS, SUITS, JUDGMENTS, COSTS, EXPENSES, FEES, INCLUDING COURT COSTS, ATTORNEY’S FEES, AND EXPERT FEES AND ALL OTHER LIABILITY OF ANY NATURE WHATSOEVER ARISING OUT OF OR RELATING TO: (I) ANY UNAUTHORIZED, NEGLIGENT OR WRONGFUL USE OF, OR CYBER DATA BREACH INCIDENT AND VIRUSES OR OTHER CORRUPTING AGENTS INVOLVING, VENDOR’S DATA, PRICING, AND INFORMATION, COMPUTERS, OR OTHER HARDWARE OR SOFTWARE SYSTEMS, AND; (II) ALLEGATIONS OR CLAIMS THAT ANY VENDOR DATA INFRINGES ON THE INTELLECTUAL PROPERTY RIGHTS OF A THIRD-PARTY OR VENDOR.