Purchased items
‘Purchased items’ refers to statement entries that are displayed in the TWINT app. The content is restricted to the actual transaction overview. TWINT ‘sees’ neither the shopping basket nor any other data and thus cannot collect this information.
Financial information
‘Financial information’ refers to the data required to process a TWINT transaction (so that the counterparty knows which account has to be charged or credited). This data is processed by TWINT albeit in a manner that ensures the data is masked out (see also ‘Identifiers’) in order to guarantee maximum data privacy. At no time whatsoever do parties other than the bank that released the respective TWINT app have access to or can view account-specific information.
Location sharing
‘Location sharing’ must be enabled for all applications that use Bluetooth (payments via Beacon are carried out with the aid of Bluetooth). In theory, the location can be identified from the position of the Beacon, but it is not saved or reused by TWINT.
User content
‘User content’ refers to the content created by the user and sent within ‘send and receive money’ transactions (e.g. text or an image).
Browser history
‘Browser history’ comprises solely the activities required to execute transactions while using TWINT+ in the smartphone browser. No other general browser data is collected beyond that.
Identifiers
‘Identifiers’ refer to TWINT-specific user identifiers (ID). A unique ID is created for every TWINT user upon registration and this is then used to regulate access to the TWINT account. These IDs allow TWINT to implement maximum data privacy, as they ensure that personal data does not have to be used.
Diagnostic/usage data
‘Diagnostic’ data consists of operational data, such as the response time of an app, communication times with the server, and the data that is recorded in the event of an error (e.g. in the event that the app crashes). This data is used to identify errors and to optimise the TWINT app accordingly. The same also holds true for ‘usage data’ that allows us to optimise the app. This data is also solely operational data concerning the processes within the app (e.g. how quickly a registration process is carried out, whether interruptions will be caused, etc.).