Privacy Policy

This Privacy Notice outlines how we process Personal data, commit to protecting your information, and provide the framework for effective management of data protection matters while providing our Services. This Privacy Notice does not cover how Dataspike's Clients may treat Users' Personal data. Clients provide this information in their privacy statements, which are not subject to Dataspike's control.

Agreement - the Service Provider Agreement concluded with each Client, its annexes and appendices;
BIPA - the Biometric Information Privacy Act of 2008 in Illinois, US;
Client - the legal entity to which Dataspike provides Services under the Agreement;
Service(s) - the personal identity verification service and connected services provided by Dataspike;
Applicant ID - a set of technical functionalities and related services provided by Dataspike to Applicants designed to assist them in simplifying identity verification and, upon their request, sharing of Personal data with Dataspike’s Clients;
Data Controller, or Controller - natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal data; i.e. Client or Dataspike when it has its own purposes - for the purpose of this Notice;
Data Processor, or Processor - a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller; i.e. Dataspike when it processes data on behalf of its Clients;
Data Providers - third-party service providers or public authorities used to collect additional information necessary for the provision of the Services;
Data Subject - any individual whose personal data Dataspike may process on behalf of the Controller (the Client’s customers);
Personal data - any information relating to an identified or identifiable Data Subject;
Special categories of personal data - personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, or data concerning health or data concerning a natural person's sex life or sexual orientation;
EU GDPR - Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation);
Filing system - any structured set of Personal data which is accessible according to specific criteria, whether centralised, decentralised, or dispersed on a functional or geographical basis used for service provision;
UK GDPR - EU GDPR as implemented in the UK’s domestic legal system;
User or Applicant - any individual in respect of whom the identity verification procedure (or any of its elements) is performed as part of the Services provided to a Client (may be referred to as ‘you’ in this Notice);
Website - Dataspike - AML and KYC Verification
Privacy Policy - this Privacy Policy available at Dataspike - Privacy
Processing - any operation or set of operations performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction;
Personal data breach - a breach of data security leading to unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored, or otherwise processed;
Consent - any freely given, specific, informed and unambiguous indication of the Data Subject’s wishes by which they, by a statement or by clear affirmative action, signify agreement to the processing of their personal data;
Standard Contractual Clauses - standard sets of contractual terms and conditions adopted by the European Commission (or UK-designated authorities) and ensuring appropriate safeguards for data transfers from the EEA and the UK to third countries, which the Controller and the Processor both sign up to, where necessary;
EEA - European Economic Area (the European Union Member States, Norway, Iceland and, Liechtenstein);
AML/CFT - Anti-Money Laundering / Combating the Financing of Terrorism legal rules and standards as envisaged in FATF recommendations, EU regulations, and national legislation;
Politically Exposed Persons (PEPs) - individuals who are or have been entrusted with prominent public functions (e.g., heads of state or government, senior politicians, senior government, judicial or military officials, senior executives of state-owned corporations, important political party officials), as well as their relatives and close associates;

Dataspike adheres to the principles of Personal data protection as envisaged in the EU GDPR and the UK GDPR, and other applicable laws. Under these principles, Dataspike assists Controllers in ensuring that Users’ Personal data is:

1. Processed fairly and lawfully and in a transparent manner in relation to the Data Subject;
2. Processed for specified, explicit, and legitimate purposes only and not further processed in a manner that is incompatible with those purposes;
3. Adequate, relevant, and limited to what is necessary in relation to the purposes for which they are processed;
4. Kept accurate and up to date;
5. Retained in a form permitting identification of Data Subjects for no longer than is necessary for the purposes for which they are processed;
6. Processed in a manner that ensures their appropriate security;
7. Not transferred outside the European Economic Area (EEA) or the UK without adequate protection.

[а] Performance of the Agreement While serving Clients, Dataspike mainly processes your data as a Processor for Clients’ benefit. Dataspike processes Personal data for the performance of Agreements, including indicated Services, obligations arising from Agreements, and related rights, as well as for the execution of rights and fulfilment of obligations deriving from legal acts and processing Users' requests.
Dataspike collects and further processes Users' data for Clients, which may include matters of compliance with applicable AML/CFT and/or other laws and regulations and/or Client's internal customer due diligence procedures. Once Personal data is no longer necessary for the relevant purpose, acting on Client’s written instructions, Dataspike transfers the data to Clients and then erases it from its servers without leaving any backup copies.
[b] Other purposes We may process your data for purposes that serve Dataspike's legitimate interests, which include the following purposes:

• Where it’s not prohibited by applicable laws and provided we have permission from our Clients, we may process some personal data, including biometrics, to develop and improve identity verification services to prevent and detect fraud and other illicit activity as part of substantial public interest via machine learning;
• Given the nature of our Services, we are to detect and prevent criminal activity, fraud, and money laundering by checking the provided User data against records of confirmed or suspected illegal activity, fraud or money laundering. If any sign of this appears, we will inform our Clients of this;
• In connection with the purpose above, we may also conduct profiling, statistical analysis, and analytics in AML/CFT tendency, fraud detection, and prevention. Our system may aggregate Users’ data to generate reports and charts our Clients may use when assuming the risk likelihood associated with specific characteristics;
• We can process Personal data, including biometric data, to identify a User or a Client’s representative for identification purposes to process data subject access request or the Client’s request accordingly;
• We sometimes may be obliged to process or retain all or part of Personal data for the establishment, exercise, or defence of legal claims;

We process some Personal data while adhering to the principles of Personal data handling, namely lawfulness and accountability, by obtaining the legal basis for processing specific Personal data concerning certain Users, as required under laws applicable to such Users. Maintaining records that we have obtained such a legal basis is essential to prove that we comply and adhere to our legal obligations outside and in the European Union and the United Kingdom.
[c] Applicant ID Applicant ID allows Applicants to use their Personal data for identity verification with multiple Clients that are entities that have acceded to our Applicant ID Client Terms and Conditions (“Participants”) including to be able to execute your right to data portability and obtain necessary Personal data based on your instructions using Applicant ID. Applicants can submit their documents and other necessary information to create a Applicant ID and subsequently request Dataspike to share their Personal data with the Clients with whom they want to verify their identity. The processing of Personal data within the Applicant ID, including the creation of a dedicated storage space (“Data Pool Key”) for an Applicant is carried out by Dataspike as a data controller. After sharing Personal data upon the Applicant’s request with a specific Client, the re-verification is carried out by Dataspike as a data processor acting on behalf of its Clients. The processing of Personal data within the Applicant ID also includes the purposes of Service Development and Fraud detection, including profiling, as described above in point [b].

Dataspike carries out multiple types of automated processing, including, but not limited to, collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination, or otherwise making available, alignment or combination, restriction, erasure or destruction.
Document сheck For fraud detection, Dataspike subjects Personal data from photos and scanned copies of documents to automated reading and verification of authenticity by conducting different checks, such as completeness of records, screenshots detection, or cross-checking of all data from all submitted documents (e.g. name, date and place of birth, signature). We also check the document's security features, including the embedded security chip, machine-readable zone (MRZ), barcodes, QR codes and other security components used for genuine data validation. Our system analyses the results of the above to make an inference regarding the document’s trustworthiness.
Biometric processing methods Dataspike may process biometrics to verify whether provided facial images are likely to match depending on the Service chosen by a particular Client. The processing of biometrics means extracting facial features from uploaded or recorded facial images on government-issued identity documents submitted by Users and comparing them.
There are several reasons why Clients ask for such biometrics processing. Generally, Clients may wish to check whether an identity document genuinely belongs to a User by comparing a provided facial image to the facial image contained in the identity document.
In addition, Clients may ask us to check whether a User is alive and genuine. To do this, we use our Liveness check to determine if the User isn’t holding a mobile phone, showing any signs of constraint, or attempting to defraud the system using emulators, static images, or ‘deep fakes’. As a rule, Users are prompted to blink, smile, or move their device while passing Liveness. During such checks, we may also detect signs of fraud or other spoofing attacks by comparing Users’ facial features to those of known masks. Simultaneously, we may also check whether the User may be generating multiple identities by inspecting whether we have previously verified him/her on behalf of a particular Client. To determine if the User is known to a specific Client, we compare the User's facial image to those of other Users previously verified on behalf of that particular Client.
When required by Clients, we assist in the authentication process. For this, Clients may ask their Users to pass liveness. During this process, a User’s face is recognized, and the result is compared with the biometric data records of the said User obtained previously.
For each authentication attempt, we will compare the new liveness facial image with the biometrics of the said User obtained previously.
Video identification processing Usually, video identification is a process where a person who is to be identified and an employee-operator sit opposite one another "face to face" in video transmission and communicate with one another. The process is carried out if a Client has a legal obligation to do so (for example, due to AML / CFT regulation). To perform video identification, we provide Clients with functionality so that they can conduct a video interview with Users during onboarding. If Clients prefer, the video identification interview can be carried out by Dataspike operators. The content of the video interview and its nature are also completely dependent on the Client’s requirements.
Data validation These data validation checks enable Clients to verify data against databases of third-party Data Providers and detect whether a User is involved in illicit activities, money laundering or terrorism financing. To do this, we will check the data extracted from the uploaded documents or provided by the User against a database of third-party Data Providers. Data Providers we may use depend on Clients’ needs and Users’ location and may include ID registers, proof of address checks, the Social Security Administration and other government or commercial sources and databases, consumer credit agencies, PEP lists, global and country-specific sanctions lists, and adverse media sources.
Throughout the course of Clients’ relationship with their Users, we may assist Clients in periodically screening Users’ data against databases to help prevent, detect, and investigate fraud and money laundering.
Sometimes, Clients ask us to conduct phone or email risk scoring. When we do it, we screen a User’s email address or phone number with the combination of IP address, where available, together with the publicly available information provided by the Third-Party Processors or Data Providers, based on the data mentioned above and get the risk labels based on its registrations on the web, domain name, delivery option and other parameters.
Know Your Transaction or KYT check KYT is a check that analyses transaction data relating to senders and recipients. It enables Clients to detect and report unusual/uncharacteristic behaviour and patterns that are characteristic of money laundering, terrorist financing, fraud, or other illicit activity.
Know Your Business or KYB check If a Client subscribes to the KYB check, it requires us to verify the existence, details, ownership, and control structure (e.g., ultimate beneficial owner(s)) of a legal entity through analysis of corporate documents and review of corporate registries, where available.
Fraud detection Dataspike implements a fraud detection and control network based on the anti-fraud checks required by our Clients and those included in our Services by default (e.g., Photoshop use or risk triggers calculation). Such checks require collecting, analysing, and re-using recorded User data.
Generally, Dataspike verifies whether a User’s attributes—geolocation (IP address), device signature (operating system and camera name), email address, or mobile phone—have previously been involved in or related to any fraudulent activity or may currently signal suspicious behaviour patterns and otherwise point out that the User is fake. At a Client’s order, we may check information with our Data Providers on AML/CFT regulations requirements, such as screening through adverse media mentions match or checking for residency in high-risk countries. Besides, we check whether Users create multiple identities by inspecting whether we have previously verified a User on behalf of a particular Client using biometric data comparison techniques.
All these checks are designed to help us and Clients assess the likelihood of customer trustworthiness, flag potentially fraudulent activities and assign a relevant risk score when the Client needs to acknowledge cases when Users generate multiple identities, compromise their data, or manipulate device or network information. Clients may consult with the fraud detection and control network on the fraud-related level of risk of Users under the onboarding process without accessing any Personal data.
Service development Our Clients use our Services to detect whether a real person is passing the identity verification process, as well as any impersonation or spoofing attempts, to prevent money laundering, terrorist financing, fraud, and other activities that are considered a matter of public interest. That is why we, as a service provider, are responsible for providing the highest quality services. For this reason, where we have the authorization of our Clients, and it is not prohibited by applicable law, we as a Data Controller use Personal data to develop and improve our Services by building and enhancing algorithms, developing and testing new verification options, products and services.
We do this in two ways. We deploy a system recognizing specific patterns in the information and making predictions about new datasets based on those patterns by training our algorithms or so-called 'machine learning.’ Machine learning helps create models based on the information provided by Users, such as signs of potential fake data, and selects the best models to be integrated into our system. The development of services also includes continuous improvement and assessment. We review our service delivery methods to ensure that we comply with Clients’ requirements and work appropriately by testing and correcting new features and functions. We implement initial and ongoing training for our analysts to perform those tasks to prevent machine learning models' automatic judgement. It is also beneficial while machine learning models are in the stage of development and aren't adequately suited to perform such tasks.

We may collect and further process the following Personal data of Users depending on the particular Service being provided to Clients:

• General personal data

  Full name, sex, personal identification code or number, date of birth, legal capacity, nationality and citizenship, location (street, city, country, and postcode).

• Identity document data

  Document type, issuing country, number, expiry date, MRZ, information embedded into document barcodes (may vary depending on the document), security features.

• Facial image data

  Photos of the face (including selfie images) and photos or scans of the face on the identification document, videos, and sound recordings.

• Biometrical data

  Facial features.

• Banking details

  Cardholder name, expiry date, first 6 and last 4 digits of the card number.

• Contact details

  Address, e-mail address, and phone number.

• Transaction data

  Full name of the sender and the recipient, the address of the sender and the recipient, and the Unique identifier of the counterparties provided by Dataspike and the particular Client.

• Technical data

  Information regarding the date, time, and activity in the Services; IP address and domain name; software and hardware attributes (e.g., camera name and type); general geographic location (e.g., city, country) from User’s device.

• Geolocation data

  IP address.

• Unique identifier

  Applicant ID created only for identifying the User in the Dataspike system.

• Relevant publicly available data

  Information regarding a person’s status as a Politically Exposed Person (PEP) or presence on sanctions lists.

• Additional information

  Data provided by the User during communication with Dataspike (e.g., requests, reports).

• Device behavioural data

  User ID, device fingerprint data (screen size, user agent, browser, incognito mode, type of device, operating system, geolocation), screen resolution, session languages, operating system verification, focus/blur of the window, time of the day, focus in/out, paste, mouse movement, battery usage to detect emulator, detect touch/mouse/keystroke events, G meter/AccelMeter

Dataspike may process Personal data of children, understood as individuals under the age of majority under national laws of a Client’s country of incorporation, when the Client ensures that the person with parental responsibility for the child has consented to such processing or when the child may consent themselves to the processing according to the national laws without parental consent. As the data controller, it is the Client's responsibility to determine when parental consent is required based on the type of Personal data collected, and to fully understand the regulatory requirements and age restrictions related to processing data without parental consent in the countries where the Client operates and from which it gathers Users. If Dataspike becomes aware that a child's Personal data has been submitted without the necessary parental consent (for instance, through an internal audit), the data may be deleted without undue delay.

When Dataspike is engaged by its Clients to perform identity verification procedures in respect of their Users, the processing of Personal data by Dataspike is covered by those legal grounds that are relied on by the Clients Dataspike has the Agreement with. In line with Article 6 of the EU and UK GDPR, Controllers should rely on an appropriate legal ground when processing Personal data. Most of our Clients rely on the following grounds for processing Personal data:

• Article 6(1)(c) of the GDPR: “[personal data] processing is necessary for compliance with a legal obligation to which the controller is subject”;
• Article 6(1)(e) of the GDPR: “[personal data] processing is necessary for the performance of a task carried out in the public interest”;
• Article 6 (1)(a) of the GDPR: “the data subject has given consent to the processing of his or her personal data for one or more specific purposes”.

We may process your Special categories of personal data if a Client has a reasonable legal ground for such processing. Clients who process biometric data for the purpose of uniquely identifying a User may rely on following legal bases to do so:

• Article 9(2)(g) of the GDPR: “processing is necessary for reasons of substantial public interest, on the basis of Union or Member State law which shall be proportionate to the aim pursued, respect the essence of the right to data protection and provide for suitable and specific measures to safeguard the fundamental rights and the interests of the data subject”;
• Article 9(2)(a) of the GDPR: “the data subject has given explicit consent to the processing of those personal data for one or more specified purposes, except where Union or Member State law provides that the prohibition referred to in paragraph 1 may not be lifted by the data subject”.

For the exact legal basis of processing Special categories of personal data, please refer to the privacy policy of the Client whose services you want to use.
Where Dataspike pursues its purposes, as said in Provision 4 of this Notice, Dataspike relies on Article 6(1)(f) of the GDPR – legitimate interest. Our legitimate interest arises from the strict necessity of internal analysis and ongoing development and improvement of Dataspike's Services that our Clients use to detect fraud and illicit activities to prevent money laundering, terrorist financing, and other activities, which are considered a matter of substantial public interest. In this case, we use legitimate interest if the Client grants us permission to process data provided that Dataspike's purposes are compatible with those initial purposes for which the Personal data has been collected. Such purposes are compatible due to the obligations or interests of our Clients regarding the combat of fraud and detection of any illegal actions. If Personal data we process for our own purposes are Special categories of personal data such as biometric data, we rely on substantial public interest as the basis for processing as provided in Article 9(2)(g) of the GDPR.
When Dataspike processes Personal data as a data controller for the purpose of providing Applicants with Applicant ID, we rely on the necessity for the performance of a contract with the Applicant (Article 6 para. 1 letter b) of the GDPR) for normal categories of Personal data. The processing of biometric data for the purpose of Applicant ID provision is carried out based on an Applicant’s explicit consent (Article 9 para. 2 letter a) of the GDPR).
Dataspike may be under a 'litigation holds' requirement, such as an existing legal claim, juridical procedure, or other legal obligation. In this case, Dataspike applies the legal ground specified in Article 6(1)(c) of the GDPR, which states that processing personal data is necessary to comply with a legal obligation to which Dataspike is subject.

Dataspike carries out Right to Work (RTW), Right to Rent (RTR) checks under the requirements foreseen in the Department for Culture, Media and Sport’s UK Digital Identity and Attributes Trust Framework (UKDIATF) (for Medium and High levels of confidence).
Dataspike acts as Identity Service Provider (IDSP), and provides RTW and RTR identity verification services under instructions of Clients (employers, landlords, etc.) or for individuals acting on their own behalf.
For the purposes of this section, the RTW and RTR checks entails document check, biometric personal identity verification, identity fraud checks*. Dataspike also provides activity history check (where it’s required), which is a check of records that show the person has regularly interacted with other organisations or people (e.g., educational organisations, financial organisations, travel companies or border or immigration authorities, utility services, etc.).
*If Dataspike suspects an Applicant committing identity fraud or a criminal offence when using Dataspike's identity verification solution, Dataspike reserves the right to retain the information about committed attempts and assign a risk score available for other Clients.
Dataspike collects the following data: For RTW and RTR forename, middle names (if any), current surname, date of birth; image of the main page of the identity document, showing: the individual’s name, data or birth, nationality, and photograph; and the document’s expiry date; biometrical data: facial scan(s);
Other provisions of the Privacy Notice are applied in ordinary form to the data processing activities under the RTW, RTR checks (e.g., Data Subjects’ rights, measures to ensure data protection and so on).

The retention period depends entirely on the processing purpose. Our Clients define how long personal data should be stored and when to delete it. Generally, in line with AML / CFT regulations, regulated financial companies are obliged to store the User's data for five years after the termination of the Client’s relationship with the User or the date of the occasional transaction. In some jurisdictions, there may be a longer mandatory data retention period.
Please note that if you, as a User, would like to make a request to delete the personal data that you have provided for the purpose of a particular Client, please make that request directly to the Client that controls your verification process.
In general, Personal data, including biometric data, will be retained and stored by Dataspike and will be permanently destroyed based on a Client’s instructions when the Client’s initial purpose and/or retention period prescribed by applicable law expires, but no longer than for the period of contractual relationship with the Client.
Where Dataspike independently defines the compatible purposes or is under a legal obligation, Personal data, including biometric data, will be destroyed after Dataspike’s purposes for collecting the biometric data have been satisfied (and one (1) year of the date the purpose for collecting the data expires for residents of Texas) or after five (5) years from the provision of data to the Dataspike system, whichever occurs first. For the residents of Illinois, the retention period of Personal data, including biometric data, will be three (3) years from the date of data provision to the Dataspike system.
Disposal and Destruction Policy Any Personal data is deleted only after (a) obtaining an applicant's data deletion request in line with corresponding procedures by a Client or the Data Subject or (b) the satisfaction of the purpose for data processing, including expiration of retention period prescribed by applicable law.
To delete data from the Dataspike Identity Verification System (Dashboard and storage space), we call a method that searches for a unique applicant identifier (Applicant ID) inside the database. The database contains references, or object IDs, connected to the applicant’s Personal data provided to the system. After seeking all these references, the Dashboard system automatically removes them one by one by calling the AWS S3 API Object Deletion method, providing Object IDs are placed in the S3 bucket. After all referenced objects are found and deleted from the S3 bucket, the original applicant's Personal data is also deleted from Dataspike’s internal database located on AWS Servers. Deletion of biometrics should render it non-recoverable, even using forensic information recovery techniques.
To delete data from the equipment, we implement measures in accordance with the particular operational system of the equipment. If the information is intended to be rendered non-recoverable, the deletion must be executed by the person who owns it (typically, who has created it) by the ‘empty trash bucket’ mechanism. If any of the methods above is not secure enough considering the sensitivity of the information and such information may be recovered again, the equipment storage medium must be destroyed completely (e.g. shredded, disintegrated, pulverised, or incinerated by burning the device in a licensed incinerator, etc.) in the presence of the asset owner.
To delete data from the files located in the removable media, we call the setting and tools designated to the relevant sanitisation method - clearing or purging. If the purging method is not secure enough considering the sensitivity of the information and such information may be recovered again, the removable media containing such information must be destroyed completely (e.g. shredded, crushed, disintegrated, pulverised, or incinerated by burning the device in a licensed incinerator, etc.).
Any request to delete all or any Personal data related to a User is fulfilled within 30 days. This period is justified by the complexity of the systems and technologies Dataspike operates to process the data.
Personal data will be retained only for as long as necessary to fulfill the purposes for which it was collected or as required by law. Specific retention periods are determined based on legal obligations and legitimate interests.
When we develop and improve identity verification services to prevent and detect fraud and other illicit activity, we will keep Personal data in a pseudonymised format for the period required to calibrate and select the perfect algorithm and model for detecting fraud and other illicit activity. We may also have to store some records that have been confirmed as relating to fraudulent applications or accounts or obtaining and maintaining records to prove our compliance with legal obligations in and outside the EU and the UK. For example, regarding consent activity log history, the retention period is defined by the criteria derived from requirements by law regarding limitation periods, other applicable regulatory requirements, contractual provisions and industry standards.
When the purpose refers to the establishment, exercise or defence of legal claims (so-called ‘litigation hold’), the retention period is limited to the duration of such proceedings in a specific case or circumstance.
In any case, we do not keep your data longer than we have a lawful basis for doing so.

Upon written request from a Client, Dataspike assists the Client in exercising Data Subject’s rights. According to privacy laws, you have the right:

• to obtain confirmation as to whether or not your personal data are being processed;
• to rectify personal data, or, in other words, to correct the wrong information or complete it;
• to erase personal data, or “right to be forgotten”Please note that this right is not absolute and applies only if (i) your Personal data is no longer necessary in relation to the purposes for which was collected or otherwise processed, (ii) you object to the processing, and there are no overriding legitimate grounds for the processing of Client; (iii) the Personal data have been unlawfully processed;
• to restrict personal data processingwhere (i) the accuracy of the Personal data is contested (during the period when the Client is able to verify its accuracy); (ii) the processing is unlawful, and you object to the erasure of the Personal data and request to restrict their use instead; (iii) the Client no longer needs the Personal data for the purposes of the processing, but they are required by you to establish, exercise or defend legal claims; (iv) you have objected to processing pending the verification whether Client’s legitimate grounds override those of yours;
• to be informed as to rectification or erasure of personal data or restriction of their processing;
• to data portability, or, in other words, to receive your personal data in an appropriate format to be able to provide it to another party or transfer your personal data from one controller to another;
• to object to personal data processing if the processing is justified by the ‘public interest’ or ‘legitimate interest’ legal grounds as set out in points (e) and (f) of Article 6(1) of the GDPR;
• not to be subject to a decision based solely on automated processing unless (i) such decision is necessary for entering into, or performance of, a contract between you and the Data Controller; (ii) such decision is authorised by the law to which the Data Controller is subject and which also lays down suitable measures to safeguard your rights and freedoms and legitimate interests or (iii) such decision is based on your explicit consent.

To ask Dataspike to execute the rights mentioned above or redirect the request to the Client, you should send a free-form email to [email protected] or use this form. The information on actions taken in response to any request is provided to you within one month. That period may be extended by two further months where necessary, considering the complexity and number of the requests. In this case, we will inform you of any such extension within one month of receipt of the request, and the reasons for the delay.
Please be kindly aware that when you ask us for the execution of the rights as stated above, we may have to take steps to verify that you are the legitimate data owner and/or authorised to make the request due to a Client's request or our own legal obligation.
Dataspike guarantees that making a request for receiving Personal data is free unless a reasonable cost is to be charged where requests are unfounded, excessive, or repetitive in character.

Dataspike assists Controllers (Clients) with the obligation of providing the mechanism for withdrawal of consent (Article 7 (3) EU GDPR and UK GDPR) and objection to processing based on legitimate interests (Article 21 (1) EU GDPR and UK GDPR).
Depending on the legal basis of processing that a Client relies on (consent or legitimate interest), the right to withdraw consent or the right to the object of processing can be exercised.
Dataspike does not make decisions regarding such requests on its own, as Dataspike acts in accordance with the written instructions of Clients, who exercises control over Personal data. Dataspike can only redirect a User’s request to the Client for whom the User was verified.
To withdraw consent or object to processing by Dataspike , you can use this link to form your request. Please note that to object to data processing, there should be overriding grounds to those we have under the legitimate interest. We underline that due to the importance of identity verification and fraud prevention to the world's financial system - so-called public interest - for which the Personal data checks are carried out, it will be rare that we have no compelling, overriding grounds to continue using the Personal data following an objection. Generally, under the given circumstances, there are better options than to terminate the processing of Personal data under the objection request. For example, it would be unfair to hide the result of previous fraudulent patterns that could allow a person to steal money from the account by pretending to be another person.

[a] Dataspike’s responsibilities, and the DPO Dataspike is responsible for establishing policies and procedures in order to comply with the EU GDPR and the UK GDPR. Our Data Protection Officer can be contacted via the following e-mail address: [email protected].
[b] Dataspike DPO’s responsibilities Dataspike’s Data Protection Officer holds responsibility for

• drawing up guidance and promoting compliance with this Privacy Notice;
• appropriate compliance with the EU GDPR, UK GDPR and Data Protection Act 2018;
• ensuring that any Personal data breaches are resolved, catalogued and reported appropriately in a swift manner;
• investigating and responding to complaints regarding data protection, including Data Subject’s requests.

[c] Dataspike’s personnel responsibilities Dataspike personnel involved in Personal data processing comply with the requirements of this Privacy Notice and other internal rules. This personnel ensures that:

• all personal data is kept securely;
• no Personal data is disclosed either verbally or in writing, accidentally or otherwise, to any unauthorised third party;
• any queries, requests and complaints regarding data protection are promptly directed to the Data Protection Officer;
• any data protection breaches are swiftly brought to the attention of the management and the Data Protection Officer;
• where there is uncertainty regarding a data protection matter, advice is sought from the Data Protection Officer.
• where there is uncertainty regarding a data protection matter, advice is sought from the Data Protection Officer.

[d] Third-Party Processors acting on behalf of Dataspike Where third-party companies are engaged to process Personal data on behalf of Dataspike, responsibility for the security and appropriate use of the data remains with Dataspike.
Before engaging a Third-­Party Processor, Dataspike ensures that it provides sufficient guarantees regarding Personal data security. In particular, a written contract establishing the types of Personal data to be processed and the purposes of such processing, as well as containing provisions on Personal data protection, are concluded between Dataspike and the Third-­Party Processor

Dataspike takes specific measures to ensure Personal data protection, including, but not limited to, the following:

• where applicable, all Personal data processing is conditioned on respective Agreements, non-disclosure agreements, and data processing agreements compliant with the EU GDPR and the UK GDPR;
• Dataspike’s specially designed API interface (iFrame) enables Data Subjects to submit Personal data directly to Dataspike’s secure servers;
• all personal data is always securely stored on the servers located in safe European data centres of a security level no lower than Tier 3;
• all Personal data is encrypted;
• personnel involved in Personal data processing is officially authorised and undergoes background checks, where it is obligatory, and regular training;
• Dataspike regularly carries out internal and external data protection and information security audits and vulnerability assessments. In particular, compliance with the EU GDPR and the UK GDPR requirements, ISO/IEC 27001, 27017 and 27018, SOC 2 Type 2, and PCI DSS has been demonstrated;
• where the processing of certain Personal data (e.g., children’s Personal data or sensitive data under certain data protection laws) would be unlawful, Dataspike takes all possible measures to identify and delete or, where appropriate, encrypt such data immediately upon its submission;
• physical, software and network security guarantees as set out below are implemented.

Suppose certain types of Personal data, such as the Dutch BSN, Korean RRN, Japanese My number card and related sensitive data, or Singaporean NRIC number, as well as other country-specific requirements, are under special protection regimes (if any). In those cases, Dataspike will take the necessary measures not to process such data, such as requesting a User to cover data with a sticker or processing restrictions using blurring technology, unless the respective Client has a legal basis for processing it freely.

Where a Personal data breach occurs or is suspected, it is reported immediately to the Data Protection Officer (DPO) or a director and, where applicable, to the data protection authority, the respective Client and, if applicable, to the individual affected by the breach. The report includes full and accurate details of the incident (including its reasons and magnitude) and outlines the planned measures to eliminate the breach.
The report is provided directly to the concerned Client, and further breach mitigation is supported.

[a] Third Parties If Clients agree, Dataspike may use third parties for data processing activities, which include the following categories:

• Third-party processors as reasonably necessary for the provision of a service under an Agreement with a respective Client engaging them to process certain data;
• Data providers when it is supposed to be used for the provision of Service under an Agreement with a respective Client.

Dataspike requires third parties to respect the security of Personal data and treat it according to the applicable law. In addition, third parties are mostly limited to only accessing or using Personal data to provide services to Dataspike and must provide reasonable assurances they will appropriately safeguard the data.
[b] Recipients Where it is required by law, Dataspike may have to provide Personal data to the recipients, which includes the following categories:

• Governmental bodies and regulatory authorities, judicial bodies, investigation bodies, sworn bailiffs, and notaries based on written and concrete requests or the duties binding upon Dataspike or its Clients stipulated by the legal enactments. Such sharing is conducted in line with strict compliance with derogations of the EU GDPR and the UK GDPR; and
• Any other Clients provided that there is a legitimate interest or any other legal reason for doing so, obtained consent or where Dataspike has been instructed to share the information on behalf of our Clients as specified above.

Dataspike confirms that all Personal data is stored on Dataspike’s servers located in the EU and/or subject to any national localisation requirements in the respective countries, where such requirements exist. Clients may choose the location of Personal data processing (including storage) to comply with the applicable laws.
Whenever a transfer of Personal data outside the EEA or the UK is carried out, Dataspike implements appropriate safeguards as set out in Chapter V of the EU GDPR or UK GDPR by transferring based on an EU Adequacy Decision (or UK Adequacy Regulations) or by concluding Standard Contractual Clauses. Third-Party Processors likewise rely on appropriate safeguards, which include binding corporate rules, Standard Contractual Clauses, or other lawful bases. Cross-border Personal data transfers from the UK to the EU/EEA countries are permitted by the UK Government. In cases of international data transfers from other jurisdictions (when we provide services on behalf of companies outside of Europe) we either transfer personal data to countries with adequate level of protection or using data transfer tools provided for in applicable laws such as appropriate contractual measures.

Dataspike does not sell Personal data and strictly complies with restrictions and prohibitions under CCPA and the EU or the UK GDPR.

Personal data processed by Dataspike may include certain ‘biometric identifiers’ (such as scans of facial geometry or voiceprints) and ‘biometric information’ (data extracted from and based on biometric identifiers), which are used to verify the identity of Users.
Whenever such biometric identifiers and/or biometric information (collectively ‘biometric data’) are used as part of the Services rendered by Dataspike to any Client, such data shall be processed by Dataspike on behalf of such Client and permanently deleted as stated in Provision 10 of this Notice. In the latter case, Dataspike shall not perform any operations regarding such data other than its storage for the period required by the applicable law.
Dataspike maintains a publicly available policy outlining our retention schedule and guidelines for permanently destroying biometric data.

This Privacy Notice is constantly reviewed and amended to comply with the relevant data protection laws.
Dataspike reserves the right to amend this Notice at any time and for any reason. Any amendments will be effective immediately upon us posting the updated Privacy Notice on our Website. Our Website users waive the right to receive specific notice about such amendments. You are invited to review this Privacy Notice anytime to stay informed about updates.
If you want to observe the previous version of this Privacy Notice, please contact us at [email protected]. Our technical and legal support teams work 24/7 and will answer you shortly.