Skip to main content

Data Retention Waiver (Germany) - CSL Computer Service Langenbach GmbH

DATA RETENTION WAIVER
CSL Computer Service Langenbach GmbH

CSL Computer Service Langenbach GmbH ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request.

Registrar's Waiver Request cites the previous data retention waivers granted by ICANN to RegistryGate GmbH, ingenit GmbH & Co. KG, and 1APl GmbH on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany.

See <https://www.icann.org/news/announcement-2014-08-07-en>

<https://www.icann.org/news/announcement-3-2014-08-07-en>

<https://www.icann.org/news/announcement-4-2014-08-07-en>

Registrar and each of the registrars granted a waiver as cited above aredomiciled in Germany and subject to German law, and ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waivers previously granted to RegistryGate GmbH, ingenit GmbH & Co. KG, and 1APl GmbH.

ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms:

  1. ICANN agrees as follows:

    (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz – BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected.

    (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz – TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG.

    (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected.

    (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met.

  2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control.

  3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar.

ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.


More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."