Ordinance
on the Surveillance of Post and Telecommunications
(SPTO)


Open article in different language:  DE  |  FR  |  IT
Art. 43 Information Request Type IR_15_COM: Information on subscribers to other telecommunications or derived communications services

1 In­form­a­tion Re­quest Type IR_15_­COM com­prises the fol­low­ing data about sub­scribers to oth­er tele­com­mu­nic­a­tions or de­rived com­mu­nic­a­tions ser­vices (e.g. mes­saging ser­vices, com­mu­nic­a­tions ser­vices in so­cial net­works:79

a.
if avail­able, the unique sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
b.
the iden­ti­fic­a­tion data spe­cified in Art­icle 19 and, if known, data on the nat­ur­al per­son or leg­al en­tity, ad­di­tion­al con­tact data and the gender of the nat­ur­al per­son;
c.
the fol­low­ing data about each ad­di­tion­al tele­com­mu­nic­a­tions ser­vice or de­rived com­mu­nic­a­tions ser­vice that the sub­scriber ob­tains from the pro­vider:80
1.
the unique iden­ti­fi­er that in­dic­ates the pro­vider,
2.
the unique ser­vice iden­ti­fi­er (e.g. user name),
3.
the peri­od over which the ser­vice was used (start, first ac­tiv­a­tion and if ap­plic­able, ter­min­a­tion),
4.
the statuses of the ser­vice as des­ig­nated in­tern­ally by the pro­vider (e.g. act­ive, sus­pen­ded, blocked) and their peri­od of valid­ity in each case,
5.
the list of oth­er ad­dress­ing re­sources or iden­ti­fi­ers re­gistered in con­nec­tion with this ser­vice,
6.81
the name of the ser­vice.

2 The re­quest for in­form­a­tion shall spe­cify the peri­od to which the re­quest relates. It shall con­tain at least one of the fol­low­ing query cri­ter­ia:82

a.
sur­name(s), first name(s);
b.
date of birth;
c.
coun­try and post­code or coun­try and place;
d.
street and, if pos­sible, house num­ber;
e.
iden­tity doc­u­ment num­ber and, op­tion­ally, the type of iden­tity doc­u­ment;
f.
name and, op­tion­ally, the re­gistered of­fice of the leg­al en­tity;
g.83
UID or LEI;
h.
sub­scriber iden­ti­fi­er (e.g. cus­tom­er num­ber);
i.84
ad­dress­ing re­source or iden­ti­fi­er (e.g. user ad­dress, pseud­onym, unique ap­plic­a­tion-spe­cif­ic iden­ti­fi­er);
j.85
iden­ti­fi­er as­so­ci­ated with the ser­vice con­cerned, such as a re­cov­ery ad­dress­ing re­source.

3 In the case of the cri­ter­ia in para­graph 2 let­ters a–d, a second query cri­terion shall be ad­ded. If search­ing for char­ac­ter strings (let. a, c, d and f), the pro­vider shall search for the spe­cified spelling of the term in ac­cord­ance with the FD­JP reg­u­la­tions.86

79 Amended by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

80 Amended by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

81 In­ser­ted by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

82 Amended by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

83 Amended by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

84 Amended by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

85 In­ser­ted by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

86 In­ser­ted by No I of the O of 15 Nov. 2023, in force since 1 Jan. 2024 (AS 2023 685).

Diese Seite ist durch reCAPTCHA geschützt und die Google Datenschutzrichtlinie und Nutzungsbedingungen gelten.

Feedback
Laden