1 SEM shall maintain a passenger information system (API System) in order to:
- a.
- improve border controls;
- b.
- combat unlawful entry into the Schengen area and transit through the international transit zones of the airports;
- c.
- combat international organised crime and terrorism, espionage and preparations for illegal trading in weapons and radioactive materials and illegal technology transfers.375
1bis The API System contains the data in accordance with Article 104 paragraph 3 and the results of comparisons in accordance with paragraph 4.376
2 In order to check whether air carriers are fulfilling their duty to provide data, and to enforce penalties under Article 122b, SEM may retrieve data in accordance with Article 104 paragraph 3 from the API System.377
3 In order to improve border controls and to combat unlawful entry into the Schengen area and transit through the international transit zones of the airports, the authorities responsible for checks on persons at the Schengen external borders may retrieve data in accordance with Article 104 paragraph 3 from the API System.378
3bis If it is suspected that a person is preparing for or committing offences under Article 104 paragraph 1bis letter a, fedpol may retrieve the data in accordance with Article 104 paragraph 3.379
4 The data in accordance with Article 104 paragraph 3 letters a and b shall be automatically and systematically compared with the data from RIPOL, the SIS, the ZEMIS and the Interpol database for stolen and lost documents (ASF-SLTD).380
5 The data in accordance with Article 104 paragraph 3 and the results of the comparisons in accordance with paragraph 4 may only be used following the arrival of the flight concerned in order to conduct criminal or asylum proceedings, or proceedings under the law on foreign nationals. It must be erased:
- a.
- when it is established that no proceedings of this type will be conducted, or two years after the date of the flight concerned at the latest;
- b.
- on the day after the ruling in proceedings of this type takes full legal effect.
6 The data may be retained in anonymised form for statistical purposes beyond the deadlines set out in paragraph 5.
374 Inserted by No I of the FA of 20 June 2014 (Violations of the Duty of Care and to Report by Air Carriers, Information Systems), in force since 1 Oct. 2015 (AS 2015 3023; BBl 2013 2561).
375 Amended by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).
376 Inserted by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).
377 Amended by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).
378 Amended by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).
379 Inserted by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).
380 Amended by No I of the FA of 14 Dec. 2018 (Procedural Regulations and Information Systems), in force since 1 June 2019 (AS 2019 1413; BBl 2018 1685).