4Pay Privacy Policy
Last updated: 15.09.2025
Introduction
1.1. 4Pay IT Solutions LTD (hereinafter (“4Pay”, “we”, “our”, “us”) values your privacy and is committed to protecting it in accordance with applicable data protection laws, including the General Data Protection Regulation (GDPR). This Privacy Policy aims to inform you about how 4Pay processes personal data strictly in its role as a data processor, acting solely on the documented instructions of its business customers (data controllers) who use our services.
1.2. This Privacy Policy outlines our current practices and commitment to data protection and privacy. We strive to collect and process only the data that is strictly necessary for our interactions with (prospective) customers, (future) partners, and users or visitors of our websites and online resources, in order to provide services and/or information for specific and legitimate purposes.
1.3. 4Pay is dedicated to safeguarding the confidentiality and privacy of the information in its possession and is committed to the proper use and protection of personal data, ensuring transparency and respect for individual rights in accordance with applicable data protection legislation (“data protection law”), including EU Regulation 2016/679 (GDPR), where applicable.
1.4. Our Privacy Policy is available in its latest version on the homepage of our website: http://krionyx.com. We encourage you to review it carefully, as it explains how we collect, use, share, and protect the personal data we obtain.
General Provisions
2.1. This Policy should be read together and in conjunction with the relevant Terms of the service provided by 4Pay and applies also to use of our website and online systems pursuant to the relevant Terms. 4Pay in this Privacy Policy refers to 4Pay business, that is responsible for processing personal data exclusively as a processor, acting only under the instructions of the relevant data controller (our business customer).
2.2. This Privacy Policy applies to personal data processed by 4Pay solely in its capacity as a data processor and as described in this Privacy policy. It contains information on:
The personal data we collect;
How we use personal data;
With whom personal data might be shared, and
2.3. This Policy is addressed to natural persons (“data subjects”) in the context of relationships that arise between 4Pay and its Customers, where natural persons:
2.4. In this Policy, “Personal Data” (also, “personal information”, “information”, “data”) refers to information that identifies you or may identify you (e.g. your name, address, identification number). “Processing” of Personal Data refers to actions such as collecting, handling, storing and protecting personal data.
2.5. Some links on 4Pay websites may contain links or lead/originate to/from non-4Pay websites or areas with their own data protection policies, which may differ from our Privacy Policy. Please ensure that the relevant policies of other entities are acceptable to you prior to using other sites or areas. 4Pay does not accept any responsibility or liability for third party websites. Additionally, if you are not a data subject to whom this Policy is addressed, please refer to the privacy policy of the relevant data controller entity of your personal data to learn more about how the entity processes it. 4Pay may be involved in your data processing as the processor, as in the cases referred to in this Privacy Policy.
2.6. 4Pay maintains an internal Record of Processing Activities (ROPA) documenting all categories of personal data processed, purposes, retention periods, and recipients, as required under GDPR Article 30.
Required Personal Data
3.1. The establishment and legality of contractual relations and provision of services between 4Pay and its Customers is dependent on provision of the information requested by 4Pay, which includes personal data of data subjects. It is an obligation to provide personal data to us:
– Under our legal obligations. Provision of personal data may be required under legal obligations applicable to our Customers (controllers). Where such obligations apply (e.g. AML, fraud prevention), 4Pay processes personal data only on behalf of and under the documented instructions of the controller. 4Pay itself does not determine the legal basis for such processing;
– For contractual purposes. Establishment of business relations for provision of services, execution of transactions and for the performance of contractual obligations between both parties (4Pay and its Customers) requires provision of certain personal data;
– Our legitimate interests. Based on legitimate interests identified by the relevant controller (e.g. ensuring security, fraud prevention), 4Pay may process data under the controller’s instructions.
3.2. Personal data is requested prior to the establishment and during the contractual relationship. Failure to provide requested data to us may result in us not being able to enter into a contract (establish business relations), or execute an order without requested data, or that we may no longer be able to continue with an existing relationship and provision of services and would have to terminate the relationship.
3.3. 4Pay, as a provider of payment services and payment methods to merchants/providers of services and goods often acts as a processor of personal data in respect to these businesses, who are the responsible parties as controllers for your personal data and its processing. For example:
3.3.1. When 4Pay provides technical processing services for card or online payments, acting strictly as a data processor, it processes only the following categories of personal data received from the controller and necessary for the technical execution and reporting of transactions:
– transaction identifiers (internal order ID, date and time, amount, currency, and status);
– merchant identifier (controller’s company name or code);
– technical connection data (IP address of the Customer’s system, API request/response logs);
– limited contact data of the Customer’s authorized representatives (business email and phone number) used for communication and support.
No cardholder data (such as full card numbers, CVV codes, or customer payment credentials) and no end-user identification documents are stored or otherwise retained by 4Pay.
3.3.2. Client controllers may use the 4Pay software to technically transmit data between their end users and their banks or payment providers for the purpose of initiating payments. 4Pay itself is not a payment initiator and does not transfer any funds; it only provides a secure technical interface.
3.4. These actions are performed only at the request of the controller, that is, the company that directly conducts financial transactions and accounting while receiving services from 4Pay. Accordingly, we recommend that you review the relevant policies of the controller on its website or request them directly if you are a user of a service provided by the controller based on 4Pay software. In such cases, 4Pay acts solely as a data processor and does not determine the purposes of personal data processing. At the same time, 4Pay may define certain technical methods for processing the order.
Collection and Use of Personal Data
4.1. Sources of Data
4Pay collects limited personal data from the following sources:
– Submitted data: information provided by the Customer (merchant/controller) during onboarding or in the course of the business relationship (e.g., business contact details of the Customer’s authorised representatives).
– Service-generated data: technical and transactional information generated automatically when the Services are used (e.g., transaction identifiers, merchant identifiers, API request/response logs, IP addresses of the Customer’s systems).
– Public or third-party data: only if required to verify the Customer’s corporate details (e.g., company registry data).
4.2. Scope of Data Processed
Acting strictly as a data processor, 4Pay processes only the following categories of personal data received from the Customer and necessary for the technical execution and reporting of transactions:
– transaction identifiers (internal order ID, date and time, amount, currency, status);
– merchant identifier (controller’s company name or code);
– technical connection data (IP address of the Customer’s system, API request/response logs);
– limited contact data of the Customer’s authorised representatives (business email and phone number) used for communication and support.
4.3. Exclusions
4Pay does not collect or retain:
– full payment card data (PAN, CVV, expiry dates),
– customer payment credentials,
– end-user identity documents, financial statements, income data or other sensitive personal information.
All processing is performed solely under the documented instructions of the Customer (data controller) and only to the extent necessary to provide the Services.
Purposes for which we use your personal data
4.4. Your data is processed with the data-minimization principle in mind. We aim to limit the processing of your data and the type of data processed to strictly the data needed for a lawful reason. 4Pay processes only the personal data provided by the Customer (data controller) as necessary for the technical processing of orders and related transactions. 4Pay does not verify the accuracy, completeness, or lawfulness of such data, and the Customer remains solely responsible for ensuring that the personal data it provides to 4Pay is accurate and collected in compliance with applicable Data Protection Law.
Data may be processed by 4Pay under the documented instructions of the controller for purposes such as:
Legal bases – Lawful reasons for processing
4.5. As a data processor, 4Pay does not determine the lawful basis for processing personal data. The lawful basis is determined solely by the relevant controller (our business customer). Any references to legal bases in this Policy are included only as illustrative examples of typical processing contexts instructed by controllers (e.g., performance of contract, legal obligation, legitimate interests, or consent). 4Pay does not rely on or choose a legal basis independently.
4.5.1. Performance of a contract (illustrative example): when the controller processes personal data to perform its contract with an end-user, 4Pay may be instructed to process data to technically enable such services.
4.5.2. Legal obligation or public interest (illustrative example): when the controller is legally required to collect or share certain data (e.g. AML, fraud prevention), 4Pay may be instructed to process such data on its behalf.
4.5.3. Legitimate interests (illustrative example): when the controller determines that processing is necessary for its legitimate interests, 4Pay may process data accordingly under the controller’s documented instructions.
4.5.4. Consent (illustrative example): where the controller relies on consent from the end-user, 4Pay may process personal data under the controller’s instructions.
4.6. We have set out below for in a table format, an indicative description for your convenience, of the ways we may use your personal data as set out above, and which of the legal bases we may rely on to do so; we have also identified what our legitimate interests are and may be where appropriate.
| Purpose (what we use your information for) | Lawful reason (as determined by the controller) | Typical controller interests (illustrative examples) |
|---|---|---|
Acceptance processes to establish relationship: To review Customer’s application | Performance of contract (to establish a contractual relationship) Legal Obligation Legitimate Interests | Compliance with applicable regulations governing the provision of Company’s services Record Keeping Legal obligations during the review of an application |
AML/TF, fraud prevention activities: To identify, examine, prosecute and prevent crime or fraud To verify Customer and identify his (continued) eligibility for the requested services and ability for management of the account To manage risk internally for the Company and externally for the Customers To comply with applicable laws and regulations To provide information to authorities upon request To respond and solve complaints | Legal Duty Public Interest Performance of contract Legitimate Interest | To establish and implement an internal fraud and crime identification and reporting mechanism Compliance with applicable regulations governing the provision of Company’s services Cooperation with authorities at a national and international level To fulfill our legal and contractual obligations |
Conducting of business relationship: To deliver the requested products and services To execute and manage customer’s payment orders and to perform our obligations arising from Customer’s transaction To apply on the Customer’s account any fees and charges To collect any due funds To communicate with the Customer and provide information | Performance of contract Legal Obligation Legitimate Interest | Fulfilment of our legal and contractual duties Compliance with applicable regulations governing the provision of Company’s services Typical controller interests (illustrative examples) in providing the requested services at a satisfactory and anticipated level Record Keeping maintenance |
To provide information in relation to the (requested) products and services available To communicate with Customers and provide support to meet Customer’s needs To manage relations of the Company with counterparties, partners, and service providers | Performance of contract Legal Obligation Legitimate interests | To ensure products and services are suitable for Customers To develop and improve products and services and to define applicable charges To identify the target market To fulfill our legal and contractual obligations |
To improve services and products To manage our cooperation with other service providers To analyze Customers, and efficiency of operation of products and services To launch and test new products To develop new products and expand its business For Marketing activities | Performance of contract Legal Obligation Legitimate Interest | To develop and improve products and services and to define applicable charges To fulfill legal and contractual obligations |
To manage the Company’s operations, financial and business ability, communication channels and organizational planning | Legal Obligation Legitimate interests | Compliance with applicable regulations governing the provision of Company’s services To fulfill its legal and contractual obligations |
For proper execution and performance of the agreement between the Customer and the Company: To exercise rights set out in agreements To inform the Customer in relation to any changes to the Terms and Conditions of the services provided | Legal Obligation Performance of contract Legitimate interests | Compliance with applicable regulations governing the provision of Company’s services To fulfill its legal and contractual obligations |
Retention period
Who receives your personal data
6.1. 4Pay functions receive your personal data in the context of 4Pay’s operations. This is required in order to provide carry out requests and provide services, and to perform our contractual and legal obligations.
6.2. We will not share personal data with third parties unless this is necessary for our legitimate business needs, to carry out requests, provide services and/or as required or permitted by law. Third parties under these circumstances include:
6.2.1. Service providers
We will disclose personal data to third party partners and service providers (processors) so they can process it on our behalf where required. In all such cases, these third parties act strictly as sub-processors, and 4Pay remains responsible for ensuring that sub-processors are bound by appropriate contractual obligations in accordance with Article 28(4) GDPR. These service providers are required to provide sufficient assurances in accordance with data protection law. (e.g. being bound contractually to confidentiality and data protection obligations). We will only share personal data necessary for them to provide their services.
Cloud infrastructure providers
In particular, we use trusted third-party cloud service providers, including Google Cloud, to host and process personal data. These providers act strictly as sub-processors on our behalf and are contractually bound to comply with data protection and confidentiality obligations in line with GDPR. Google Cloud, as our infrastructure provider, maintains industry-leading security standards and certifications, ensuring the confidentiality, integrity, and availability of personal data.
6.2.2. Auditors, advisors and consultants
We may disclose personal data for purposes and in the context of audits (e.g. external audits, security audits), to legal and other advisors, in order to investigate security issues, risks, complaints etc.
As such, personal data may be transferred and disclosed to:
6.2.3. Regulatory authorities, law enforcement, courts
We may disclose personal data to comply with applicable legislation, regulatory obligations, to respond to requests of regulatory authorities, government and law enforcement agencies, courts and court orders of the country of 4Pay’s local business/supranationally, such as:
6.2.4. Other recipients may be any person/legal entity/organization for which you ask your data to be transferred to (e.g. reference etc.) or give your consent to transfer personal data.
6.2.5. We may also disclose your data in circumstances such as the following:
International Data Transfers
6.3. We are a company with a global reach. Your personal data may be processed locally in the EEA/local country of our operation, or in another country where we or our partners operate worldwide, as permitted by law. Your personal data may be transferred from the European Union/European Economic Area (EU/EEA) or from another country that restricts transfers of personal information to third countries or to international organizations if the transfer is necessary and has a legal basis as described in this document. Such transfers take place for example:
The processors (or controllers) in third countries in these cases shall either:
Personal data may be stored in data centres located within the European Union and, where necessary, outside the EU/EEA. In cases of international transfers, we ensure that appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) approved by the European Commission, Binding Corporate Rules (BCRs), or other lawful transfer mechanisms recognized under EU law.
6.4. Such transfers are carried out in compliance with Chapter V GDPR, with safeguards such as SCCs, BCRs or equivalent mechanisms.