Calling Name Database Sample Clauses

The Calling Name Database clause establishes the terms under which a telecommunications provider accesses and uses a database that associates telephone numbers with the names of their subscribers. Typically, this clause outlines the provider’s obligations regarding the accuracy, security, and permitted uses of the database, such as ensuring that subscriber information is only used for call display or related services. Its core practical function is to ensure that calling name information is managed responsibly and in compliance with privacy and regulatory requirements, thereby protecting both the service provider and end users from misuse or unauthorized disclosure of personal data.
Calling Name Database. BellSouth shall make available its calling name database at rates, terms and conditions contained in BellSouth’s calling name database Agreement.
View SourceView Similar (29)
Calling Name Database. 11.5A.5.1 Verizon shall permit TCG to transmit a query to Verizon’s CNAM database for the purpose of obtaining the name associated with a line number for delivery to TCG’s local exchange customers. To the extent TCG provides local switching utilizing its own switch, TCG may request that Verizon provide CNAM database storage and validation services pursuant to a separate agreement or an amendment to this Agreement negotiated by the Parties.
View SourceView Similar (2)
Calling Name Database. Verizon shall permit AT&T to transmit a query to Verizon’s CNAM database for the purpose of obtaining the name associated with a line number for delivery to AT&T’s local exchange customers. To the extent AT&T provides local switching utilizing its own switch, AT&T may request that Verizon provide CNAM database storage and validation services pursuant to a separate agreement or an amendment to this Agreement negotiated by the Parties.
View Source

Related to Calling Name Database

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • Processing of Customer Personal Data 3.1 UKG will: 3.1.1 comply with all applicable Data Protection Laws in the Processing of Customer Personal Data; and 3.1.2 not Process Customer Personal Data other than for the purpose, and in accordance with, the relevant Customer’s instructions as documented in the Agreement and this DPA, unless Processing is required by the Data Protection Laws to which the relevant UKG Processor is subject, in which case UKG to the extent permitted by the Data Protection Laws, will inform Customer of that legal requirement before the Processing of that Customer Personal Data. 3.2 Customer hereby: 3.2.1 instructs UKG (and authorizes UKG to instruct each Subprocessor) to: (a) Process Customer Personal Data; and (b) in particular, transfer Customer Personal Data to any country or territory subject to the provisions of this DPA, in each case as reasonably necessary for the provision of the Services and consistent with the Agreement. 3.2.2 warrants and represents that it is and will at all relevant times remain duly and effectively authorized to give the instructions set out in Section 3.2.1 on behalf of each relevant Customer Affiliate; and 3.2.3 warrants and represents that it has all necessary rights in relation to the Customer Personal Data and/or has collected all necessary consents from Data Subjects to Process Customer Personal Data to the extent required by Applicable Law. 3.3 Schedule 1 to this DPA sets out certain information regarding UKG’s Processing of Customer Personal Data as required by Article 28(3) of the GDPR (and equivalent requirements of other Data Protection Laws).

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Use of Customer Name Contractor may use County’s name without County’s prior written consent only in Contractor’s customer lists. Any other use of County’s name by Contractor must have the prior written consent of County.

  • 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. Consistent with this requirement, PFPC Trust may 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. PFPC Trust may also ask (and may have already asked) for additional identifying information, and PFPC Trust may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.