In this third and final article of our series, we address the requirements FinTech companies must observe when managing their KYC data. We focus on two specific areas: data retention and deletion, and the rights of data subjects whose data is being processed.
Data retention and deletion of KYC data
First, you must establish how long KYC data will be stored and when it will ultimately be deleted. According to European data protection laws, personal data no longer needed for the purposes for which it was collected must be deleted and no longer processed. This means FinTech companies must ensure they store only KYC data required for their business operations, and only for as long as necessary. While the retention period depends on the purpose of data processing, it is in some cases also legally prescribed. In Germany and Switzerland, for example, statutory retention periods of up to ten years apply to accounting and tax records, and the European Money Laundering Directive requires companies to retain a copy of their KYC processes for five years after the end of a business relationship or after an occasional transaction.
Once retention periods are established, you must define a process for deleting data after the specified timeframe. Various deletion methods exist—from overwriting to degaussing to physical destruction. Particularly when large volumes of data are processed across multiple systems, automating deletion routines is one of the best ways to reduce the risk of data protection non-compliance and avoid human error. For this reason, a deletion process should be implemented in your system from the outset, and every data record should automatically be tagged with a future deletion date.
Another option is to anonymize the data, since data protection laws do not apply to fully anonymized data. Sometimes this may be preferable to deletion, as aggregated anonymized data might still be needed for statistical purposes. However, this is often easier said than done—for data to be considered truly anonymized, there must be no way to re-identify individuals through conventional technical or organizational means.
Against this backdrop, it is advisable to establish a deletion concept for KYC data that specifies how long data will be retained and how it will be deleted. This must take into account both the period during which data is needed for the relevant processes and any legally prescribed retention periods.
Rights of data subjects
The second important aspect concerns the rights of data subjects with respect to their KYC data. Under the GDPR and the Swiss Federal Data Protection Act (DSG), persons whose data is being processed have a range of rights, one of the most important being the right to be informed about data processing (for example, through a privacy policy).
It is important to make this privacy policy accessible as early as possible in the customer relationship, since the person must be informed at the time their data is first collected. This means the privacy policy should be visible and accessible both on your website and in your app, as well as during the customer registration process. It is also important that customers can access the privacy policy at any later time.
Additionally, data subjects in most cases have the right to data portability—that is, they can request that their personal data be transferred to them or to another company in a standard format such as Excel. For this reason, it is important for FinTech companies to implement the necessary technical tools to extract relevant data in a structured, commonly used and machine-readable format (such as CSV, XML and JSON formats) and to enable its transmission to the relevant data processor or to the data subject. Various approaches exist to achieve this—either through direct transmission of the requested data or by providing access to a download area that allows the data subject to extract the requested data themselves.
In addition to the right to information and the right to data portability, data subjects have various other rights in the KYC process. These include the right to access and correct data stored about them, as well as the right to deletion of data when it is no longer required for the purposes for which it was collected.
Key takeaways
Just as the collection and monitoring of KYC data requires special attention from FinTech companies, so too does the management of this data—particularly with respect to storage and requests from data subjects. Against this backdrop, it is important to pay attention to the following:
-
Retention periods: Personal data may only be stored for as long as it is needed for the purposes for which it was collected, or for as long as legal retention periods prescribe (for example, accounting, tax and anti-money laundering laws provide for various retention periods ranging from five to ten years). After these periods expire, data processing should cease either through deletion or anonymization.
-
Data deletion: Deletion of data should be carried out in such a way that it becomes unusable, either through destruction of physical archives or through the use of automated tools to delete large datasets.
-
Deletion concept: The retention period for each category of KYC data should be established, and the respective deletion process should be defined and automatically implemented in your systems.
-
Rights of data subjects: The rights granted to data subjects by data protection laws must be observed. In particular, data subjects must be informed about the processing of their data (for example, through a privacy policy). This information should be provided in an accessible and easily understood form and at the earliest possible stage of the KYC process. When setting up your own procedures and systems, you should also take the necessary technical measures to comply with other rights—such as the right to data portability.



