--- title: "Exporting Personal Data" slug: "exporting-personal-data" updated: 2025-07-04T10:07:17Z published: 2025-07-07T11:25:40Z canonical: "docs.onespan.com/exporting-personal-data" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Exporting Personal Data OneSpan Risk Analytics provides the PL/SQL procedure ExportPersonalData to export data stored in the OneSpan Risk Analytics database. This data comprises all the personal data of a digital banking service user: - Information about the relationship individual, i.e. the digital service user: - Relationship identifier. - Relationship name, address, email, phone number if provided etc. - Information on the relationship accounts, including: - Account identifier. - Account number, BIN number etc. - Balance if provided etc. - All events received from this relationship: - All transaction fields, including device, IP, and geolocation information. - All non-monetary fields, including device, IP, and geolocation information. - All alerts generated by events received from this relationship. - All actions taken via the OneSpan Risk Analytics application (alerts completion and status, memo etc.). ## Exporting personal data To export personal data 1. Enter SET SERVEROUTPUT ON for SQL * Plus to print the output generated by the DBMS_OUTPUT package from the ExportPersonalData procedure. 2. To export the personal data of a digital banking service user, enter execute ExportPersonalData('[LAB_SEC]', '[REL_REF]'); where [LAB_SEC] is the security label, i.e. the name the OneSpan Risk Analytics environment, and [REL_REF] is the relationship reference of the relevant user. > execute ExportPersonalData( 'CORP99', 'RS02_20180509175325'); The command delivers the personal data in the output generated by the DBMS_OUTPUT package in XML format. The following SQLPlus script sample connects to the OneSpan Risk Analytics Oracle database schema, and uses the input parameter [LAB_SEC] to identify the user and export their digital banking data. Exportdata.sql: ```plaintext SET SERVEROUTPUT ON EXECUTE ExportPersonaldata('&1','&2'); DISCONNECT EXIT ``` Command line: sqlplus IRM/irm@localhost:1521/orcl @exportdata.sql DBANK Custo2 > custo2.xml In this example, the command executes the exportdata script for a digital banking user referenced as Custo2 in the DBANK environment; the Oracle connection uses the IRM user and irm password, on port 1521 for SID orcl, and the digital banking user data is written to the custo2.xml file. ## Affected tables Personal data is exported from the following tables: - EVENT - PT_ACCOUNTS - PT_APPLICATIONS - PT_NON_MON_EVENTS - PT_Q_RECORDS - PT_Q_REJECTS - PT_RELATIONSHIPS - PT_TXN - PT_USER_EVENTS