| Non binding translation Executive Order No. 665 of 6 July 2000 See the Danish version Executive Order on Number Information Databases Pursuant
to section 34(2) of Act No. 418 of 31 May 2000 on Competitive
Conditions and Consumer Interests in the Telecommunications Market, the
following provisions shall apply: PART 1 Definitions and scope 1. This Executive Order shall apply to: 1) Requirements for delivering number information data. 2) Collection and registration of number information data. 3) Consumer protection. 2.-(1)
Number information data shall mean information about subscriber numbers
assigned to end-users, containing the name, address, occupation (if
applicable), subscriber number and the category of service for which
the subscriber number is used. (2) Data sellers shall mean the
providers of telecommunications networks and telecommunications
services who reassign 8-digit subscriber numbers to end-users. (3) Data buyers shall mean all parties that wish to buy number information data. (4)
General and publicly available number information databases and
registers shall mean lists of number information data for all end-users
as opposed to a data seller's or a data buyer's more specialized
registers, e.g. of certain types of business operators etc. PART 2 Requirements for delivery of number information data 3.-(1)
Data sellers shall deliver the number information data on end-users
that the sellers have recorded pursuant to sections 8 and 9, subject to
section 11, of this Executive Order, as well as section 34(3) of the
Act on Competitive Conditions and Consumer Interests in the
Telecommunications Market. (2) The obligation in subsection (1) shall not include: 1)
Information delivered for the purpose of number information databases
or registers other than general and publicly available number
information databases and registers. 2) Versions of the registers mentioned in subsection (1) where the register has been further processed via data processing. (3)
Data sellers shall only be obliged to deliver number information data
as mentioned in subsection (1) to the extent that such data is
available to the data seller. (4) If the data seller is not in
possession of number information data as mentioned in subsection (1),
the data seller shall deliver the information recorded in the customer
databases that form the basis for billing. 4. In
connection with the delivery of number information data under section
3, it shall be without significance whether the data seller has placed
the data in question in a special intra-group business area or company,
provided that the data is still available to the data seller. 5.-(1)
Number information data may solely be required to be resold at the same
degree of validation as it is already held in the data seller's
database. (2) In cases where the data structure of the feed
system does not match the data structure in Annex 1, adaptation shall
be made in connection with the transfer of data from the data seller to
the party who requests the data in question. This adaptation shall be
made by the data seller. 6. As a minimum, data sellers shall provide the following updating solutions: 1) Daily electronic updating. 2) Total extract indicating which data has been modified within the last quarter, or delivery of modified data once a month. 7.-(1) When delivered, number information data shall be structured as specified in Annex 1. (2) Data buyers may demand that number information data be delivered to them electronically. (3) Data buyers may demand that number information be delivered to them in the format described in Annex 2. PART 3 Collection and recording of number information data 8.-(1)
The collection and recording of number information data by data sellers
for the purpose of inclusion in registers of end-users' installation or
user addresses shall be made when telecommunications subscription
agreements are established between providers and end-users and when
subsequent modifications are made in such data. (2) Number
information data that the data seller requests from the end-user under
subsection (1) in connection with the establishment or modification of
a telecommunications subscription agreeement between a provider and an
end-user shall correspond, as a minimum, to the data specified in Annex
1, items 1-13. (3) Beyond subsections (1) and (2), there is no
independent obligation on the data seller to initiate collection or
updating of number information data at existing end-users for the
purpose of being able to pass this on to data buyers. (4) At
the request of the end-user, the data seller shall include data as
specified in Annex 1, items 15-17. Data sellers shall be responsible
themselves for recording the data specified in Annex 1, item 14. 9.-(1)
Data sellers and data buyers shall carry out amendments or
modifications of an end-user's number information data directly after
the end-user's application for amendment or modification thereof. (2)
The data seller and the data buyer shall be separately responsible for
the amendments and modifications made under subsection (1). (3)
Data sellers may demand payment for omitting information about
end-users, provided that this shall not exceed the costs involved in
adapting and updating databases in connection with the omission of
information. PART 4 Consumer protection 10.
In connection with the establishment or modification of customer
relationships, data sellers shall inform end-users of the rights
mentioned in sections 9 and 11, as well as the rights following from
section 34(3) of the Act on Competitive Conditions and Consumer
Interests in the Telecommunications Market, and section 29(3) of the
Executive Order on the Central Register of Persons. 11.
Publishing or passing on data in excess of the data specified in Annex
1, items 1-14, shall only be allowed to the extent that the end-user
has explicitly consented thereto. PART 5 Coming into force 12.-(1) This Executive Order shall come into force on 15 July 2000. (2) Executive Order No. 580 of 24 June 1999 on Number Information Databases shall be repealed. National Telecom Agency, 6 July 2000 Jørgen Abild Andersen / Lars Sten Jørgensen Annex 1 Data regarding the registered end-user shall be specified as follows: 1. Subscriber number 2. First name(s) 3. Surname 4. Occupation 5. Street name 6. House number 7. Floor 8. Unit on floor 9. House name 10. Locality 11. Postcode 12. Postal district 13. Business name 14. Marking if the number relates to a prepaid card 15. "Internal structuring" and physical location of numbers at end-users who have been assigned several telephone numbers 16.
Information indicating how the end-user wants to appear in number
information databases, including any information about marketing 17. Use (to the extent that the end-user has explicitly consented to information being passed on, cf. section 11) Annex 2 Formats: Comma separated ASCII file with quotation marks (") around the field content and character set equal to Danish Windows 95. A. File content, total extract The extract file shall contain data organized in the following fields: - Telephone number - Occupation - First name - Surname - Street name - House number - Floor - Unit on floor - House name - Locality - Postcode - Postal district - Business name - Prepaid card - "Internal structuring" and physical location of numbers at end-users who have been assigned several telephone numbers - Use (to the extent that the end-user has explicitly consented to information being passed on) - Information indicating how the end-user wants to appear in number information databases - Change marking/date/time (cf. section 6) Field description Telephone number: Telephone number or the text "HEMMELIG"(confidential). Occupation: Occupation of user or blank. First name: User's first name or blank. Surname: User's surname or blank. Street name: Street name or the text "ADR-HEMMELIG" if confidential. House number: House number supplemented with stairway letter where relevant, or blank. Floor: Floor number or blank. Unit on floor: Floor unit or blank. House name: Separate name of the house, if any, or blank. Locality: Name of locality or blank. Postcode: Postcode or blank. For foreign addresses, the field may be left blank. Postal district: Postal
district or blank. For foreign addresses, the foreign postcode may be
recorded together with the postal district and country. Business name: Name of business. Prepaid card: Indication showing if the number relates to a prepaid card. Internal structuring: "Internal structuring" and physical location of numbers at end-users who have been assigned several telephone numbers. Use: To the extent that the end-user has explicitly consented to information being passed on, the use should be stated. Appearance desired by customer: Information
indicating how the end-user wants to appear in number information
databases, including any protected or confidential names. B. File content, updating extract The
extract shall contain "SLET"(delete)/"RET"(correct)/"OPRET"(create)
made in the data seller's customer system for a certain period elapsed.
The updating files shall contain the following fields: - Telephone number - Confidential/omitted marking - Type of change - Date of change - Occupation - First name - Surname - Street name - House number - Floor - Unit on floor - House name - Locality - Postcode - Postal district - Business name - Prepaid card - "Internal structuring" and physical location of numbers at end-users who have been assigned several telephone numbers - Use (to the extent that the end-user has explicitly consented to information being passed on) - Information indicating how the end-user wants to appear in number information databases Field description Telephone number: Telephone number or the text "HEMMELIG" (confidential). Confidential/omitted marking: -U = "Udeladt" (omitted) -H = "Hemmelig" (confidential) -A = Address confidential Type of change: - SLET (delete) - RET (correct) - OPRET (create) Date of change: Date of updating Annex 1 numbering system, normally equal to invoicing date of last order. Occupation: Occupation or blank. First name: First name or blank. Surname: Surname or blank. Street name: Street name or the text "ADR-HEMMELIG" if confidential. House number: House number supplemented with stairway letter where relevant, or blank. Floor: Floor number or blank. Unit on floor: Floor unit or blank. House name: Separate name of the house, if any, or blank. Locality: Name of locality or blank. Postcode: Postcode or blank. For foreign addresses, the field may be left blank. Postal district: Postal
district or blank. For foreign addresses, the foreign postcode may be
recorded together with the postal district and country. Business name: Name of business, or blank. Prepaid card: The text "F" (if the number relates to a prepaid card), or blank. Internal structuring: "Internal structuring" and physical location of numbers at end-users who have been assigned several telephone numbers. Use: To the extent that the end-user has explicitly consented to information being passed on, the use should be stated. Appearance desired by customer: Information
indicating how the end-user wants to appear in number information
databases, including any protected or confidential names. C. Updating in respect of unlisted numbers Updating shall be based on the telephone number field: 1. "SLET" (delete) if number found in own base. 2. "RET" (correct) if number found in own base, otherwise "OPRET" (create). 3. "OPRET" (create) if number not found, otherwise "RET" (correct). If
the telephone number field in the change file contains "HEMMELIG"
(confidential) then "OPRET" (create). The order should be as stated. To
ensure the confidentiality of unlisted numbers, current "SLET" and
"RET" are not possible. Removal of deleted and old confidential
data must therefore be carried out via total extracts or via the status
file for unlisted numbers. This is done by deleting all "HEMMELIG" in
own base and then recreate all "HEMMELIG" from the status file or total
extract. |