CINXE.COM

<!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no"/> <style> @import url("https://static.threema.ch/fonts/labgrotesque.css"); * { font-family: 'Lab Grotesque', Helvetica, Arial, sans-serif; } body { margin: 0; padding: 10px; } body.dark { background-color: #222222; color: white; } a { color: #4fbc24; text-decoration: none; font-size: inherit; } body.work a { color: #0A87F0; } body.dark a { color: #4fbc24; } body.dark.work a { color: #0A87F0; } a.btn { display: inline-block; color: #fff; text-align: center; vertical-align: middle; user-select: none; background-color: #05A63F; padding: 0.6rem 0.75rem; border-radius: 1px; margin-top: 10px; } body.work a.btn { color: #fff; background-color: #0A87F0; } body.dark a.btn { color: #fff; } h2 { font-size: 18pt; margin-top: 10px; margin-bottom: 10px; } p, ul, li { font-size: 10pt; } time { font-size: 10pt; font-style: italic; } ul.references { margin-top: 40px; padding: 0; font-size: 10pt; list-style-type: none; } </style> </head> <body class="light threema"> <div id="main"><div> <h1>Privacy Policy</h1> <h2>1. General</h2> <p>The “<strong>Threema App</strong>” was developed to process and store as little metadata as possible on a central server. The identification of a user of the Threema App (hereinafter “<strong>User</strong>”) takes place exclusively via an 8-digit alphanumeric ID (hereinafter “<strong>Threema ID</strong>”) and a public key, both of which are randomly generated by the User when setting up the Threema App.</p> <h3>A. Scope of Application</h3> <p>This Privacy Policy applies to all data processing activities that take place while using the Threema App in its latest version and are related to personal data, namely:</p> <p><a href="#a-setting-up-the-threema-app">A. Setting up the Threema App</a>;<br> <a href="#b-address-book-synchronization">B. Address Book Synchronization</a>;<br> <a href="#c-sending-messages">C. Sending Messages</a>;<br> <a href="#d-sending-messages-to-broadcast-ids">D. Sending Messages to Broadcast IDs</a>;<br> <a href="#e-voice-and-video-calls">E. Voice and Video Calls</a>;<br> <a href="#f-group-calls">F. Group Calls</a>;<br> <a href="#g-license-verification">G. License Verification</a>;<br> <a href="#h-crash-reports">H. Crash Reports</a>.</p> <p>Threema as the data controller is a limited liability company under Swiss law with its registered office in Pfäffikon SZ (municipality of Freienbach), Switzerland, and business identification number (hereinafter “<strong>UID</strong>”) CHE-221.440.104.</p> <p>When a User uses the Threema App, personal data is, unless otherwise stated in this Privacy Policy, processed and, if necessary, stored exclusively on Threema’s own servers in two data centers of an “ISO 27001”-certified colocation partner located in Zurich, Switzerland (hereinafter “<strong>Threema Servers</strong>”).</p> <p>As a company with its registered office in Switzerland, Threema and the data processing it carries out are subject to Swiss data protection law (Federal Act on Data Protection of September 25, 2020, SR 235.1; hereinafter “<strong>FADP</strong>”). For data subjects residing in the territory of the EU or the EEA (marked with “<strong>for EU/EEA</strong>”), European data protection law (Regulation (EU) 2016/679 of April 27, 2016, General Data Protection Regulation; hereinafter “<strong>GDPR</strong>”) may additionally apply.</p> <p>Personal data pursuant to Art. 5 lit. a FADP [for EU/EEA: Art. 4 No. 1 GDPR] is information that relates to an identified or identifiable natural person.</p> <h3>B. Controller</h3> <p>Threema GmbH<br> Churerstrasse 82<br> 8808 Pfäffikon SZ<br> Switzerland</p> <p>UID: CHE-221.440.104</p> <h3>C. Data Protection Officer</h3> <p>Threema GmbH<br> Data Protection Officer<br> Churerstrasse 82<br> 8808 Pfäffikon SZ<br> Switzerland</p> <p>Email: <code>privacy at threema dot ch</code></p> <h3>D. Representative in the EU (Art. 27 GDPR)</h3> <p>ACC Datenschutz UG<br> Messestrasse 6<br> 94036 Passau<br> Germany</p> <h3>E. Swiss Supervisory Authority</h3> <p>Federal Data Protection and Information Commissioner (FDPIC)<br> Feldweg 1<br> 3003 Bern<br> Switzerland</p> <p>Telephone: +41 58 462 43 95<br> Contact form of the FDPIC: <a href="https://www.edoeb.admin.ch/edoeb/en/home.html">Link</a></p> <h2>2. Processing Activities</h2> <p>Depending on how a User uses the Threema App, Threema processes different categories of personal data about the User for different purposes, based on different legal bases and with different storage periods, if any personal data is stored at all.</p> <h3 id="a-setting-up-the-threema-app">A. Setting up the Threema App</h3> <h4>Processing</h4> <p>In addition to the Threema ID and the key pair (public and private key), various other data points are generated and linked to the Threema ID on the Threema Servers when the Threema App is set up on the User’s mobile device.</p> <h4>Categories of Processed Personal Data</h4> <p>When setting up the Threema App, the following personal data is generated and stored as inventory data on the Threema Servers:</p> <ul> <li>Google push token (Android);</li> <li>Apple push token (iOS).</li> </ul> <p><strong>Note:</strong> On mobile devices without Google Play services and in the “<strong>Threema Libre</strong>” version of the Threema App, no Google push tokens are generated. Users can find more information on Threema Libre on the Threema website: <a href="https://threema.ch/en/faq/libre_info">Link</a></p> <p>The following personal data, which is optional for the use of the Threema App, may be provided voluntarily by the User and is stored only in the form of one-way encrypted hash values as inventory data on the Threema Servers:</p> <ul> <li>Telephone number of the User (one-way encrypted);</li> <li>Email address of the User (one-way encrypted).</li> </ul> <p>All personal data, including the one-way encrypted hash values, is protected on its way to the Threema Servers by transport encryption in order to make it impossible for third parties to intercept the data.</p> <p><strong>Note:</strong> Before a User’s telephone number and/or email address is linked to their Threema ID, this personal data must be verified as being that of the User in an automated process.</p> <p><strong>Email address verification:</strong> To verify a User’s email address, it is transmitted to the Threema Servers after having been entered in the Threema App, and processed in plain text in order to send the User an email with a confirmation link.</p> <p><strong>Telephone number verification:</strong> For the verification of a User’s telephone number, it is transmitted to the Threema Servers after having been entered in the Threema App, and processed in plain text. The User will then receive a confirmation code by SMS.</p> <p>For the delivery of the confirmation code to the User to verify the telephone number, Threema relies on the services “eCall” of F24 Schweiz AG, Samstagernstrasse 45, 8832 Wollerau, Switzerland, (hereinafter “<strong>F24</strong>”) as well as “IMASYS” of Swissphone Wireless AG, Fälmisstrasse 21, 8833 Samstagern, Switzerland (hereinafter “<strong>Swissphone</strong>”). Both F24 and Swissphone are “ISO 27001”-certified and host their services “eCall” and “IMASYS” in Switzerland. Users can find more information on data protection at F24 and Swissphone on the websites of F24 (<a href="https://ecall-messaging.com/en/company/data-security-and-protection/">Link</a>) and Swissphone (<a href="https://www.swissphone.com/de-ch/loesungen/anwendungsfaelle/business-messaging/">Link</a>).</p> <p><strong>Note for Users outside of Switzerland and EU/EEA:</strong> To deliver the confirmation codes by SMS to Users outside of Switzerland and EU/EEA, Threema relies on the services of Twilio Inc., 101 Spear Street, 5th Floor, San Francisco, California, 94105, USA (hereinafter “<strong>Twilio</strong>”). Users can find more information on data protection at Twilio under the following link from Twilio: <a href="https://www.twilio.com/en-us/legal/privacy">Link</a></p> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Use of the Threema App’s features by the User (contract performance).</li> </ul> <h4>Legal Basis</h4> <p>The processing and storage of personal data for setting up the Threema App is based on the overriding private interest (use of the Threema App by the User; contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>The processing of the User’s personal data for setting up the Threema App is necessary to enable the User to use the Threema App as contractually agreed.</p> <h4>Storage Period</h4> <p>The push token stored when setting up the Threema App is stored on the Threema Servers for a <strong>maximum of 1 year</strong>, calculated from the date of the last connection of a Threema ID to the Threema Servers, and then automatically deleted. The User may delete the stored push token <strong>at any time</strong> (see <a href="#6-control-options-of-the-user">Section 6</a>).</p> <p>The one-way encrypted hash values of the telephone number and/or email address of the User are stored on the Threema Servers <strong>until revocation</strong> so that Users who reactivate their Threema ID with a backup do not have to relink this data. The User may delete this data <strong>at any time</strong> (see <a href="#6-control-options-of-the-user">Section 6</a>).</p> <p>The telephone number and/or email address of the User processed for verification is stored on the Threema Servers for a <strong>maximum of 1 month</strong> as a one-way encrypted hash value, provided the User does not complete the verification process. In the event of successful verification, the telephone number and/or email address are linked as one-way encrypted hash values to the Threema ID of the User.</p> <h3 id="b-address-book-synchronization">B. Address Book Synchronization</h3> <h4>Processing</h4> <p>In order to facilitate finding other Users of the Threema App, a User may voluntarily enter their telephone number and/or email address in the Threema App and link it to their Threema ID (see <a href="#a-setting-up-the-threema-app">Section 2.A.</a>).</p> <p>If Users voluntarily activate the optional contact synchronization in the Threema App, one-way encrypted hash values of telephone numbers and/or email addresses in the contact list of their mobile device are transmitted to the Threema Servers manually (by pulling down the screen) or automatically approximately every 24 hours to search for identical hash values of telephone numbers and email addresses that other Users have linked to their Threema IDs. If identical hash values are found that other Users have linked with their Threema ID, these Users will appear in the Threema App contact list stored on the mobile device. In this way, the locally stored contact list of the Threema App automatically stays up to date.</p> <h4>Categories of Processed Personal Data</h4> <p>For address book synchronization, the following personal data is processed on the Threema Servers only as one-way encrypted hash values:</p> <ul> <li>Telephone number of the User and their contacts (one-way encrypted);</li> <li>Email address of the User and their contacts (one-way encrypted).</li> </ul> <p>In addition, the one-way encrypted hash values are protected on their way to the Threema Servers by transport encryption in order to make it impossible for third parties to intercept the hash values.</p> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Use of the Threema App’s features by the User (contract performance).</li> </ul> <h4>Legal Basis</h4> <p>The processing of the telephone number and/or email address of a User and of persons in the contact list on the User’s mobile device (only in the form of one-way encrypted hash values) for address book synchronization in a User’s contact list in the Threema App is based on the overriding private interest (use of the Threema App by the User; contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>The processing of telephone numbers and/or email addresses of persons in the contact list on a User’s mobile device is necessary to enable the User to use the Threema App as contractually agreed.</p> <h4>Storage Period</h4> <p>The storage period of the telephone number and/or email address provided by the User is identical to the storage period for inventory data processed for setting up the Threema App (see <a href="#a-setting-up-the-threema-app">Section 2. A.</a>).</p> <p>The one-way encrypted hash values of the telephone numbers and/or email addresses of persons in the contact list on a User’s mobile device are <strong>immediately</strong> deleted from the Threema Servers after an address book synchronization has been performed. They are <strong>never permanently</strong> stored on the Threema Servers, unlike the telephone number and/or email address linked with a User’s Threema ID.</p> <h3 id="c-sending-messages">C. Sending Messages</h3> <h4>Processing</h4> <p>The Threema App encrypts all message content (text messages, media files, and system messages) and voluntarily and optionally set nicknames and profile pictures of Users by means of a secure end-to-end encryption process.</p> <p>Since the private key to decrypt a message is stored exclusively on the recipient’s mobile device, Threema doesn’t have access to message contents of Users.</p> <p>Interested Users can find more information about the encryption in the Threema App in Threema’s Cryptography Whitepaper on the Threema website: <a href="https://threema.ch/en/faq/why_secure">Link</a></p> <h3 id="d-sending-messages-to-broadcast-ids">D. Sending Messages to Broadcast IDs</h3> <h4>Processing</h4> <p>In addition to the Threema App for consumers, Threema also offers “<strong>Threema Work,</strong>” a software for business customers. Threema Work offers additional features compared to the Threema App, including “<strong>Threema Broadcast.</strong>”</p> <p>With Threema Broadcast, special Threema IDs can be created. They are marked with an asterisk (“*”) at the beginning of the 8-digit ID (hereinafter “<strong>Broadcast ID</strong>”).</p> <p>Broadcast IDs are principally used for one-way one-to-many communication, i.e., sending the same message to several Users, whereas between Users of the Threema App, two-way one-to-one communication takes place. Users of the Threema App are still able to send messages to Broadcast IDs.</p> <p><strong>Note:</strong> A Broadcast ID can receive messages from Users like a Threema ID. As the endpoint of the end-to-end encryption, such messages will be decrypted by the private key of the Broadcast ID on the Threema Servers, but they are never permanently stored (with one exception).</p> <p><strong>“Save Chat History” feature</strong>: With Broadcast IDs, groups can be created, and Users of the Threema App can be invited to such groups. In such groups, the business customer behind the Broadcast ID has the option to activate the “<strong>Save Chat History</strong>” feature.</p> <p>Groups of a Broadcast ID, in which the “Save Chat History” feature has been activated, can be recognized by the cloud emoji (☁️), which is technically mandatory and prefixed to the name of the group of the Broadcast ID. Users who were members of such a group before activation (or deactivation) of the feature automatically receive a warning in the form of a system message.</p> <p>If this feature is activated, all encrypted message content sent into the group of a Broadcast ID by Users is not only decrypted on the Threema Servers upon receipt by the Broadcast ID, but also stored.</p> <p><strong>Note:</strong> The controller responsible for the processing of decrypted message contents in connection with the use of the “Save Chat History” feature of a Broadcast ID is the respective business customer of Threema, who decides on the activation and thus the purposes and means of this data processing. Threema processes this personal data on behalf of its business customer, i.e., as a processor.</p> <h4>Categories of Processed Personal Data</h4> <p>Upon receipt of a message by a Broadcast ID, the following personal data is processed and, if the “Save Chat History” feature is activated, stored on the Threema Servers:</p> <ul> <li>Message content (decrypted).</li> </ul> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Use of the Threema App’s features by the User (contract performance);</li> <li>Use of Threema Broadcast’s features by business customers (contract performance).</li> </ul> <h4>Legal Basis</h4> <p>The processing of decrypted message contents of Users and their storage in a group of a Broadcast ID, in which the “Save Chat History” feature has been activated, is based on the overriding private interest (contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>This data processing is necessary to enable business customers to use Threema Broadcast as contractually agreed.</p> <h4>Storage Period</h4> <p>The decrypted message content is stored on the Threema Servers for the following durations, calculated from receipt by the Broadcast ID, and then automatically deleted:</p> <ul> <li>Text messages: <strong>180 days</strong>;</li> <li>Polls: User responses to polls from a Broadcast ID for a <strong>maximum of 180 days</strong>, calculated from the date the poll was sent by the Broadcast ID.</li> </ul> <h3 id="e-voice-and-video-calls">E. Voice and Video Calls</h3> <h4>Processing</h4> <p>In addition to exchanging text messages and media files, Users of the Threema App can also communicate with each other independently of the public telephone network via internet-based voice and video calls.</p> <p>An encrypted system message (see <a href="#c-sending-messages">Section 2.C.</a>) is sent when starting voice and video calls to establish the call with the correct User of the Threema App and to inform them of the incoming call. The callee answers with a corresponding encrypted system message, which informs the calling User whether the callee accepts or declines the call.</p> <p>If the callee accepts the call, the IP addresses of the two Users are transmitted to and processed on the Threema Servers. In principle, the processing ends with the establishment of a direct peer-to-peer connection between the Users without further processing of the IP addresses on the Threema Servers. Further transmission of the voice or video call is only carried out via the Threema Servers in the following cases:</p> <ul> <li>Establishing a peer-to-peer connection fails;</li> <li>The caller’s contact is labeled with the verification level 1 (red) in the callee’s contact list;</li> <li>One of the call participants has activated the “<strong>Always Relay Calls</strong>” option.</li> </ul> <p>Like for sending messages (see <a href="#c-sending-messages">Section 2.C.</a>), the Threema App encrypts all voice and video call contents using a secure end-to-end encryption process. Threema doesn’t have access to the Users’ call contents.</p> <h4>Categories of Processed Personal Data</h4> <p>To establish voice and video calls between Users, and to transmit them via the Threema Servers if no peer-to-peer connection can be established, the following personal data is processed on the Threema Servers:</p> <ul> <li>IP addresses of the call participants.</li> </ul> <p>The IP addresses of the call participants are only processed after the callee has accepted the voice or video call.</p> <p>Users can deactivate voice and video calls in the Threema App.</p> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Use of the Threema App’s features by the User (contract performance).</li> </ul> <h4>Legal Basis</h4> <p>The processing of IP addresses for the establishment and potential transmission of voice and video calls is based on the overriding private interest (use of the Threema App by the User; contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>This processing of IP addresses for the establishment and potential transmission of voice and video calls is necessary to enable the User to use the Threema App as contractually agreed.</p> <h4>Storage Period</h4> <p>The IP addresses of the Users are <strong>immediately</strong> deleted from the Threema Servers after the peer-to-peer connection between the call participants has been successfully established or, if the call is transmitted via the Threema Servers, after the voice or video call has been terminated. IP addresses are <strong>never permanently</strong> stored on the Threema Servers for voice and video calls.</p> <h3 id="f-group-calls">F. Group Calls</h3> <h4>Processing</h4> <p>In addition to individual voice and video calls between two Users, the Threema App also offers “<strong>Group Calls</strong>” with more than two Users at the same time.</p> <p>As a member of a group, a User can start a Group Call with the other members of the group. Like individual calls, a Group Calls allows both voice and video transmission.</p> <p>Group Calls are only transmitted via special servers, so-called “<strong>Selective Forwarding Units</strong>” (hereinafter “<strong>SFU</strong>”). To start a Group Call, a User must first establish a connection to the SFU, for which their IP address is processed. As soon as the connection to the SFU has been successfully established, a system message notifies the other members of a group that a Group Call has been started and they can join. Like for the establishment of individual voice and video calls, encrypted system messages (see <a href="#c-sending-messages">Section 2.C.</a>) are sent by the Threema App to enable the correct Users of the Threema App to join the Group Call and to inform them that the Group Call has been started.</p> <p>After informing the other members of the group with a system message, the Threema Apps of all members of a group, including of the one who started the Group Call, will continually request the status of the Group Call on the SFU until the Group Call is terminated. As long as the Group Call is active, the IP addresses of all members of the group, including of those who do not join the Group Call, are continually processed in order to request the status of the Group Call on the SFU, and permanently processed to maintain the connection to the SFU during participation in the Group Call.</p> <h4>Categories of Processed Personal Data</h4> <p>To establish and transmit a Group Call, the following personal data is processed on the SFU:</p> <ul> <li>IP addresses of the Users who are members of a group in the Threema App in which a User has started a Group Call.</li> </ul> <p>Unlike individual voice and video calls, the IP addresses of Users who are members of a group in the Threema App in which a User has started a Group Call are processed on the SFU as soon as the system message is delivered that a Group Call has been started.</p> <p><strong>Note:</strong> This processing of IP addresses also takes place if a User has deactivated Group Calls in the Threema App.</p> <p>For Group Calls, the Threema Servers are used and SFU operated by Leaseweb Netherlands B.V., Hessenbergweg 95, 1101 CX Amsterdam, the Netherlands (hereinafter “<strong>Leaseweb</strong>”). The SFU are located in an “ISO 27001”-certified data center of Leaseweb in Amsterdam, the Netherlands. Users can find more information on data protection at Leaseweb on the website of Leaseweb: <a href="https://www.leaseweb.com/sites/default/files/Legal/LSW_NL_B2B_v1November2022_Privacy_Statement.pdf">Link</a></p> <p>The Netherlands is a member of the European Union, falls within the scope of application of the GDPR, and is included in the list of states under Annex 1 to the Ordinance on Data Protection of August 31, 2022 (“<strong>DPO</strong>”; SR 235.11); therefore, its legislation does ensure adequate data protection; Art. 16 Sec. 1 FADP in connection with Art. 8 Sec. 1 DPO.</p> <p>Like for individual voice and video calls (see <a href="#e-voice-and-video-calls">Section 2.E.</a>), the Threema App encrypts all Group Call contents with a secure end-to-end encryption process. Neither Threema nor Leaseweb have access to the Users’ call content.</p> <h4>Purpose</h4> <p>The aforementioned personal data will be processed by Threema for the following purposes.</p> <ul> <li>Use of the Threema App’s features by the User (contract performance).</li> </ul> <p>The use of Leaseweb’s SFU for Group Calls serves the purpose of ensuring the lowest possible latency and smooth communication for Users of the Threema App when using Group Calls.</p> <h4>Legal Basis</h4> <p>The processing of IP addresses for the establishment and potential transmission of Group Calls is based on the overriding private interest (use of the Threema App by the User; contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>The processing of IP addresses for the establishment and potential transmission of Group Calls is necessary to enable the User to use the Threema App as contractually agreed.</p> <h4>Storage Period</h4> <p>The IP addresses of Users that are processed on the SFU for the establishment and transmission of Group Calls are immediately deleted from the SFU after the Group Call has ended, irrespective of whether the SFU are those of Threema or Leaseweb. IP addresses are <strong>never permanently</strong> stored for Group Calls.</p> <h3 id="g-license-verification">G. License Verification</h3> <h4>Processing</h4> <p>Threema finances its business by collecting license fees instead of selling the data of its Users. When generating a Threema ID during the set-up of the Threema App, an automatic license verification is performed to verify the User’s authorization to use the Threema App.</p> <p>During the license verification, a pseudonymized digital purchase receipt from the app store (Apple/Google/Huawei) where the User purchased the Threema App is transmitted to the Threema Servers and verified. A one-way encrypted version of this purchase receipt is stored as a hash value together with a counter, and the purchase receipt is then <strong>immediately</strong> deleted.</p> <p><strong>Note:</strong> The User’s purchase receipt transmitted to Threema is not linked to the User’s Threema ID.</p> <p>If a license key from Threema’s own “<strong>Threema Shop</strong>” (<a href="https://shop.threema.ch/en">Link</a> to the Threema Shop) is used for licensing, the license key is transmitted and verified on the Threema Servers instead of the purchase receipt. After verification, the license key is stored together with a counter on the Threema Servers.</p> <p><strong>Note:</strong> The User’s license key transmitted to Threema is not linked to the User’s Threema ID.</p> <h4>Categories of Processed Personal Data</h4> <p>If the Threema App has been purchased from an app store, the following personal data is processed for license verification during the set-up of the Threema App:</p> <ul> <li>Digital purchase receipt (pseudonymized and then one-way encrypted).</li> </ul> <p>If the Threema App has been purchased via the Threema Shop, the following personal data is processed for license verification during the set-up of the Threema App:</p> <ul> <li>License key.</li> </ul> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Verification of a User’s authorization to use the Threema App and thus for preventing misuses and piracy (contract performance).</li> </ul> <h4>Legal Basis</h4> <p>This data processing is based on the overriding private interest (contract performance) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR].</p> <h4>Necessity</h4> <p>This data processing is necessary to verify the User’s authorization to use the Threema App, and thus to prevent misuses and piracy.</p> <h4>Storage Period</h4> <p>The one-way encrypted hash value of the pseudonymized digital purchase receipt and the license key are stored together with a counter on the Threema Servers for <strong>30 days</strong> and then automatically deleted.</p> <h3 id="h-crash-reports">H. Crash Reports</h3> <h4>Processing</h4> <p>In order to improve the stability and reliability of the Threema App and to further develop the Threema App, Threema relies on crash reports from Users.</p> <p>It depends on the operating system of the mobile device (Android or iOS) used by the User which data is processed by Threema when evaluating crash reports of the Threema App and how this data is collected by Threema.</p> <p><strong>Note:</strong> As an alternative independent from the operating system, Users of the Threema App can voluntarily send crash reports within the Threema App to the Threema ID “*<strong>SUPPORT.</strong>” To send crash reports via the Threema App, the debug log (hereinafter “<strong>Debug Log</strong>”) must be activated in the Threema App. The Debug Log is never sent automatically to Threema, but only manually by the User.</p> <h4>Categories of Processed Personal Data</h4> <p><strong>iOS:</strong> No personal data is processed by Threema when evaluating crash reports from Users with an iOS operating system.</p> <p><strong>Android:</strong> No personal data is processed by Threema when evaluating crash reports from Users with an Android operating system.</p> <p><strong>Debug Log of the Threema App:</strong> The following personal data is processed when evaluating Debug Logs of the Threema App:</p> <ul> <li>Log files.</li> </ul> <h4>Purpose</h4> <p>The aforementioned personal data is processed by Threema for the following purposes:</p> <ul> <li>Bug fixing and product improvement.</li> </ul> <h4>Legal Basis</h4> <p>The processing of Debug Logs is based on the overriding private interest (bug fixing and improvement of the product) of Threema; Art. 31 Sec. 2 lit. a FADP [for EU/EEA: Art. 6 Sec. 1 lit. b GDPR.</p> <h4>Necessity</h4> <p>This data processing is necessary to fix bugs of the Threema App and to further improve the Threema App.</p> <h4>Storage Period</h4> <p>The data from Debug Logs of the Threema App is stored by Threema on the Threema Servers <strong>until their analysis</strong> and then anonymized or deleted.</p> <h2>3. Disclosure of Data to Third Parties</h2> <p>Principally, Threema does not disclose to third parties any personal data that is transmitted by the User when using the Threema App and that is then processed and stored on the Threema Servers.</p> <h3>Verification of Telephone Numbers with F24 or Swissphone</h3> <p>In connection with the verification of telephone numbers, personal data of Users, namely their telephone numbers, is processed by F24 or Swissphone in Switzerland (see <a href="#a-setting-up-the-threema-app">Section 2.A.</a>).</p> <h3>Verification of Telephone Numbers with Twilio (Only for Users Outside of Switzerland and EU/EEA)</h3> <p>In connection with the verification of telephone numbers of Users outside of Switzerland and EU/EEA, personal data, namely their telephone numbers, is processed by Twilio in the USA (see <a href="#a-setting-up-the-threema-app">Section 2.A.</a>).</p> <h3>Group Calls via SFU of Leaseweb</h3> <p>In connection with Group Calls, personal data of Users, namely their IP address, may be processed by Leaseweb in the Netherlands (see <a href="#f-group-calls">Section 2.F.</a>).</p> <p>Threema reserves the right to disclose personal data to third parties (e.g., lawyers) if it is necessary for the assertion, exercise, or defense of legal claims by Threema.</p> <h2>4. Collection of Data from Third Parties</h2> <p>Principally, Threema does not collect from third parties any personal data that is transmitted by the User when using the Threema App and that is then processed and stored on the Threema Servers.</p> <h2>5. Data Security</h2> <p>In addition to using state-of-the-art encryption methods, Threema takes all necessary technical and organizational measures to prevent unauthorized access and misuse of data of Users of the Threema App. The security measures are continuously improved in line with technological developments.</p> <h2 id="6-control-options-of-the-user">6. Control Options of the User</h2> <p>In addition to the legal claims of data protection law (see <a href="#7-rights-of-the-user">Section 7</a>), Threema provides Users the following control options over their personal data:</p> <h3>Rectification, Completion, and Deletion of Telephone Numbers and Email Addresses</h3> <p>The User may rectify or complete their telephone number and/or email address in the Threema App under “<strong>My Profile.</strong>”</p> <p>The User may unlink their telephone number and/or email address from their Threema ID at any time by deleting the corresponding data in the Threema App under “<strong>My Profile.</strong>”</p> <p>Alternatively, the User may also unlink the data on the Threema website: <a href="https://myid.threema.ch/unlink">Link</a></p> <p>The corresponding one-way encrypted hash values of the User’s telephone number and/or email address will then be deleted <strong>immediately</strong> from the Threema Servers.</p> <h3>Deletion of Push Tokens</h3> <p>The User may delete the push tokens currently linked to their Threema ID at any time by resetting the push tokens in the Threema App under “<strong>About Threema &gt; Troubleshooting</strong>”.</p> <h3>Threema Push Instead of Google Push Token</h3> <p>Users may use Threema’s own push service “<strong>Threema Push</strong>” as an alternative to the Google push token. Users can find out more about Threema Push in the corresponding <a href="https://threema.ch/en/faq/threema_push">FAQ article</a> on the Threema website.</p> <h3>Information About Inventory Data</h3> <p>Users may request information about their inventory data, including personal data, stored by Threema and linked to the User’s Threema ID at any time by sending the message “<strong>info</strong>” to the Threema ID “*<strong>MY3DATA.</strong>” Users can find out more in the corresponding <a href="https://threema.ch/en/faq/get_my_data">FAQ article</a> on the Threema website.</p> <h3>Deletion of All Inventory Data by Revocation</h3> <p>The User may <strong>immediately</strong> delete their Threema ID and all information linked with it, including personal data, at any time. To do so, the User must revoke their Threema ID via the following link on the Threema website: <a href="https://myid.threema.ch/revoke">Link</a></p> <p>The revocation of the Threema ID is irreversible, and a <strong>Revocation Password</strong> must be set in advance in the Threema App.</p> <h2 id="7-rights-of-the-user">7. Rights of the User</h2> <p>As data subjects, Users of the Threema App can assert various claims under data protection law against Threema.</p> <p>In order to fulfil these claims, Threema may have to process personal data of data subjects. In particular, Threema must be able to identify the data subject in order to ensure that the data subject rights are not exercised by anyone other than the data subject and that no personal data is unlawfully disclosed to third parties.</p> <p>Regarding the processing of personal data through the use of the Threema App, secure identification of the data subject is only possible via algorithmic proof of possession of the private key associated with the Threema ID via a so-called key derivation. This is ensured in the case of automated inventory data information for Users of the Threema App via the Threema ID “*<strong>MY3DATA</strong>” (see <a href="#6-control-options-of-the-user">Section 6</a>).</p> <p>Depending on the applicable law, data subjects may exercise the following rights in relation to personal data against Threema:</p> <h3>Right to Information</h3> <p>Art. 25 and 26 FADP [for EU/EEA: Art. 15 GDPR]</p> <p>A data subject has the right to request information about their personal data processed by Threema.</p> <h3>Right to Correction or Completion</h3> <p>Art. 32 Sec. 2 FADP [for EU/EEA: Art. 16 GDPR]</p> <p>A data subject has the right to request that Threema corrects inaccurate or completes incomplete personal data without undue delay.</p> <h3>Right to Deletion</h3> <p>Art. 32 Sec. 2 FADP [for EU/EEA: Art. 17 GDPR]</p> <p>A data subject has the right to request that Threema deletes their personal data without undue delay.</p> <h3>Right to Withdrawal of Consent</h3> <p>only for data processing based on <strong>consent</strong>; Art. 30 Sec. 2 FADP [for EU/EEA: Art. 7 Sec. 3 GDPR]</p> <p>A data subject has the right to withdraw their consent to the processing of their personal data by Threema. This has the consequence that Threema may no longer continue the data processing based on this consent. The processing of the User’s personal data by Threema up to this point in time on the basis of the User’s consent remains lawful.</p> <h3>Right to Objection</h3> <p>only for data processing based on <strong>legitimate interests</strong>; Art. 30 Sec. 2 FADP [for EU/EEA: Art. 21 GDPR]</p> <p>A data subject has the right to object to the processing of their personal data by Threema where such personal data is processed based on Threema’s overriding private interests; Art. 31 DSG [for EU/EEA: Art. 6 Sec. 1 lit. f GDPR].</p> <h3>Right to Blocking</h3> <p>Art. 32 FADP [for EU/EEA: Art. 18 GDPR]</p> <p>For the protection of their personality, a data subject has the right to request that Threema blocks the processing of their personal data.</p> <h3>Right to Data Transfer</h3> <p>Art. 28 and 29 FADP [for EU/EEA: Art. 20 GDPR] [only for data processing based on <strong>consent</strong> or <strong>a contract</strong> and with the aid of <strong>automated procedures</strong>]</p> <p>A data subject has the right to receive the personal data they have provided to Threema in a structured, commonly used, and machine-readable format, provided that:</p> <ul> <li>the processing is based on consent or on a contract; and</li> <li>the processing is carried out with the aid of automated procedures.</li> </ul> <h2>8. Timeliness and Amendment of this Privacy Policy</h2> <p>Threema reserves the right to amend this Privacy Policy from time to time in order to comply with changed legal requirements or to implement new features in the Privacy Policy. The current Privacy Policy is always linked in the Threema App.</p> </div></div> </body> </html>

Pages： 1 2 3 4 5 6 7 8 9 10