1Purpose of this document
The purpose of this document is to describe key technical and organisational measures (TOMs) to comply with the requirements resulting from Art. 32 of the General Data Protection Regulation (GDPR) and applicable data protection legislation, to ensure the security of personal data and other data in Fidify’s services. These TOMs form an integral part of the Agreement between Fidify and the Customer and are incorporated by reference in the Order Form and the Fidify Data Processing Addendum (DPA).
1.1Measures implemented across the group
The TOMs outlined in this document are implemented in all Fidify group companies that develop and provide its software and services. The measures taken fulfil the requirements regarding confidentiality, integrity, availability, risk assessment, review and resilience according to Art. 32 GDPR. Where the Customer is a regulated financial entity, these measures also support the Customer’s compliance with the outsourcing and ICT third-party risk rules applicable to it (for EU customers, Regulation (EU) 2022/2554 (DORA) and the rules of the Customer’s competent authority), as identified in the Order Form.
1.2Summary of measures per Art 32 GDPR
Fidify has implemented the following measures according to Art. 32 GDPR and, where applicable, in support of the Customer’s regulatory obligations:
- access control based on least privilege and the Customer’s instructions;
- data encryption in transit and at rest;
- regular backups with point-in-time recovery;
- incident management and notification procedures in support of the Customer’s regulatory reporting obligations;
- audit and inspection rights for the Customer, its auditors and its competent authorities in connection with the Services.
2Product/Service introduction
Fidify and its group companies provide cloud-based SaaS (Software-as-a-Service) services used to collect, manage and analyse KYC and AML documentation and data from the Customer’s end-customers, as further described in the Agreement.
For example, Fidify’s platform is specifically designed to handle the documentation needs of KYC processes, reducing manual work and ensuring compliance at every step.
- Corporate document management: Efficiently gather and manage company registration documents.
- Digital document submission: Enable users to upload and review identity documents quickly.
- Secure repository: Safely store and access business-critical documents anytime.
- Comprehensive record-keeping: Maintain a complete, auditable trail of document handling for compliance.
3Risk management
Fidify’s services are considered a “high risk” service. Our platform is specifically designed to handle document management tasks required for KYC processes, ensuring that sensitive information is processed securely and in compliance with regulatory standards. Any data uploaded to the platform, including personal or corporate documents, is always controlled by the customer.
All exceptions or identified risks are managed through a defined risk management process. Security risks are reported or detected through proactive monitoring, and the resulting risk register serves as a key driver for Fidify’s ongoing risk mitigation and elimination efforts. This process is overseen by Fidify to ensure that potential risks are effectively addressed. Where the Services support a critical or important function of the Customer, Fidify’s ICT risk management takes into account the requirements of Regulation (EU) 2022/2554 (DORA).
4Privacy controls
Privacy controls are described in the Fidify Privacy Policy (fidifygroup.com/privacy). Where Fidify processes personal data on behalf of the Customer, the processing is governed by the Fidify Data Processing Addendum (DPA, fidifygroup.com/dpa), which forms part of the Agreement and incorporates the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) where required for transfers of personal data to third countries.
5Resilience
5.1Change management
Fidify updates the SaaS platform continuously and all updates are made available to all customers. Significant changes are communicated to customers before they are deployed. Fidify uses a defined Secure Development Lifecycle (SDLC), including mandatory manual and automated testing before release.
5.2Hosting and access to the production environment
All servers are managed in Google Cloud Platform (GCP). Fidify deploys its service to Google Cloud in the EU (Belgium). Where a customer's contract names another legal area, that customer's environment is hosted in the Google Cloud region agreed in the contract. Database backups are stored in the European Union, in the Netherlands and Finland (see section 10.1.1). The countries where the Services are performed and where Customer Data is processed and stored are recorded in the Order Form for customers that require it.
Access to the production environment is limited by the principle of least privilege. Staff sign in with named personal accounts protected by enforced two-step verification. Automated deployment and some administrative tooling use service-account credentials, which are held by a small number of named senior staff.
Development, test and production environments are separated.
5.2.1Configuration as code
Infrastructure and deployment configuration are defined in code and kept in version control, so every change is recorded and can be reviewed and reverted.
5.2.2Remote access from Mauritius
Personnel of Fidify (Mauritius) Ltd may access production data remotely for customer-support and operational purposes. Customer Data remains hosted in the European Union. This access is covered by the Standard Contractual Clauses between Fidify AB and Fidify (Mauritius) Ltd (DPA section 6.2) and by the following supplementary measures:
- access only over encrypted connections (see section 6.2);
- access only through Fidify’s own applications and accounts protected by two-step verification (see sections 5.2 and 7.1);
- access only by personnel who need it for a specific support or operational task;
- written confidentiality obligations for all personnel with access (see section 12.3.3).
5.3Vulnerability management
5.3.1Patching
Fidify patches its core software frameworks as soon as possible when a new long-term support (LTS) version is available. Fidify does not use beta versions in production and keeps to the latest LTS version. Patches are planned as part of the normal development and operations planning process, which runs in two-week sprints.
Regular patching. Patches that do not interrupt use of the system are applied to production continuously. Patches that may cause downtime are applied in a maintenance window or during a communicated planned outage. A patch is accepted when it passes Fidify’s automated and manual tests; a new software version is typically kept in the test environment for several days before it is applied to production.
Emergency patching. Where a critical vulnerability is detected or announced by a vendor and waiting for the regular patching window would carry a high impact, an emergency patching window is scheduled. The Fidify CTO decides whether patches are applied in an emergency patching window.
Exceptions in patching. Any exception to patching must be approved by the Fidify CTO.
5.3.2Security testing
An independent third party performs penetration testing and a security review of the Services at least once a year. The most recent test, covering the web portal, the Upload Center and the mobile app, was carried out in January 2026. Reports from completed security testing are kept, and a summary of the most recent test is available on request.
Validated critical and high findings are prioritised over feature work until they are fixed. Fidify’s target remediation times for validated vulnerabilities are:
- Zero-day vulnerability: as soon as possible
- Critical risk: 30 days
- High risk: 90 days
- Medium and low risk: scheduled with regular development work
5.4Log management and audit trails
5.4.1Operating system
Fidify runs its services on Google Kubernetes Engine (GKE) Autopilot, where Google manages, patches and logs the underlying node operating systems.
5.4.2Application
Application and infrastructure logs are collected centrally in Google Cloud Logging. A log entry typically includes:
- date and timestamp;
- level (warning, error, info);
- host;
- service;
- content (the text of the log entry).
Application logs are retained in accordance with applicable law and Fidify’s data retention policies, for reviewing the data in case of incidents and to support the Customer’s regulatory reporting obligations. Access to logs is restricted to selected operations personnel.
The Services record user activities such as logins, uploads and data exports in the audit trail. All services log their actions at info level, and warnings and errors are stored as well.
5.4.3Time synchronisation
Server clocks are synchronised by Google Cloud’s managed time service, and logs are recorded in UTC.
5.4.4Personal data in logs
Logs may contain identifiers such as internal user IDs, email addresses and IP addresses, which are needed to investigate incidents and prevent abuse. Fidify keeps personal data in logs to the minimum necessary, and logs are protected by the access restrictions in section 5.4.2.
6Personal data protection
6.1Encryption at rest and pseudonymisation
In accordance with Fidify’s Information Security Policy, all Restricted KYC data is encrypted at rest using industry-standard cryptographic algorithms and secure libraries.
User-created passwords are protected using one-way BCrypt hashing, which incorporates:
- a unique, per-user salt to protect against rainbow table attacks;
- at least 1024 iterations to slow down brute-force attempts;
- irreversibility, ensuring passwords cannot be decrypted back to their original form.
Access to customer data within the Services is role-based. Fidify personnel access customer data only where needed to provide support or operate the Services (see section 7.1).
All KYC data stored at rest is encrypted using AES with a minimum key length of 256 bits. Where supported by the cloud provider, we further limit access by restricting visibility of managed instances to authorised provider personnel only.
Additionally, uploaded files are encrypted using a hybrid encryption approach:
- Files are encrypted with AES-GCM: on the phone when uploaded from the Fidify App, and as soon as they reach Fidify’s servers when uploaded on the web. The AES key is then encrypted using ECDH-derived symmetric keys.
- The ECDH shared secret is established using the user’s private key and the portal’s public key.
- HKDF with HMAC-SHA256 is used to derive the final key used to encrypt the AES key.
- The encrypted payload includes a salt, IV, ciphertext and authentication tag, all Base64-encoded for safe transmission and storage.
Keys are released only to the people and environments entitled to read the file: the person who uploaded it, and the firm they share it with. Fidify operates the environments that hold the keys, under the access controls described in this document. This layered approach provides confidentiality and integrity across platforms (iOS, Android and web).
6.2Encryption in transit
All communication to and from Fidify services, external services and users is encrypted using HTTPS (TLS).
7Confidentiality
The following sections describe the levels and nature of access provided to users based on the sensitivity of the data and their legitimate business need to access personal data.
7.1Admin rights management
Access to servers and cloud resources is managed by Fidify and granted on the principle of least privilege. Staff use named personal accounts protected by enforced two-step verification. A limited number of service-account credentials are used for automation and administration and are held by named senior staff.
Normally, only senior team members have access to the production environment. Temporarily elevated privileges can be given for time-limited tasks; in that case, access is given only to a specific environment (test, stage or production).
Where a support request requires it, Fidify staff may sign in to a customer’s portal through a support account. This access is used only to provide support or operate the Services, on the customer’s instructions.
7.2Monitoring
Fidify uses Google Cloud’s logging and monitoring services. Google Cloud Admin Activity audit logs record administrative operations on cloud resources. Application errors are reported to Fidify’s error-monitoring service. Monitoring data and logs are restricted to privileged users on different levels, depending on their need to access them to provide a functional and secure service.
8Integrity
Data integrity is a wide concept and a set of different measures are taken to ensure it. First, data is validated when it is transferred to Fidify. Second, access and write operations to databases are restricted and, third, backups ensure that data can be restored to its original status. These measures support the availability, authenticity, integrity and confidentiality of Customer Data as required under Art. 32 GDPR and, where applicable, Regulation (EU) 2022/2554 (DORA).
9Availability
Data availability is ensured through redundancy of most (but not all) of our services. All services are monitored and alerted to product teams for remedy. The measures in place are designed to ensure the availability, authenticity, integrity and confidentiality of Customer Data, including personal data.
10Ability to restore availability and access to personal data
Below is defined how availability, and unauthorised or accidental destruction of personal data, is controlled.
10.1Business continuity and disaster recovery
Business continuity and disaster recovery are described in Fidify’s Business Continuity Plan and Incident Management Procedure, which are part of Fidify’s ISMS documentation. Where the Services support a critical or important function of the Customer, Fidify supports a documented exit plan in accordance with the Agreement, including continued provision of the Services during the transition period and support for the migration of Customer Data to the Customer or an alternative provider.
10.1.1Data backup and restore
Database servers are backed up with at least the following configuration:
- Continuous transaction-log archiving
- Base backups twice a day
- Point-in-time recovery: 30 days
- Backup location: EU dual region (Netherlands and Finland), encrypted
Backups are stored separately from the production databases.
11Software management and vulnerability management
11.1Application environment
11.1.1Dependencies
Third-party and open-source dependencies used to build and run the Services are declared in code with pinned versions (lock files), which are checked automatically in the build pipeline.
11.1.2Vulnerability management
Vulnerabilities identified in dependencies or through security testing are assessed and fixed according to the targets in section 5.3.2. Fixes for critical vulnerabilities are tested in the test and staging environments before release.
11.2Employee workstations and mobile devices
Software installation and vulnerability management are defined in Fidify’s Mobile Device Policy.
12Communication security
12.1Network security management
12.1.1Network controls
Application environments (test, staging and production) only include features strictly necessary for application functionality.
12.2Sessions
Sessions in the web portal expire after 7 days. Sessions in the Fidify App expire after 30 days. Users can end a session at any time by logging out.
12.3Information transfer
12.3.1Agreements on information transfer
Customers can import and export data to and from the Fidify user interface manually, for example using Excel, if needed.
12.3.2Electronic messaging
Fidify communicates with users outside the application by email, and with Fidify App users through push notifications.
12.3.3Confidentiality or non-disclosure agreements
Contracts between Fidify group companies and customers contain confidentiality clauses consistent with section 8 of the Fidify General Terms and Conditions. Where the Customer is subject to statutory professional secrecy, Fidify’s confidentiality obligations extend to all information covered by that obligation, as set out in the Order Form and the DPA. For contractors and employees at Fidify group companies, a standard template is used which also contains a confidentiality clause that includes protection of all customer data. Confidentiality obligations relating to personal data and trade secrets continue for as long as the information remains protectable under applicable law, and professional secrecy obligations survive termination of the Agreement without time limit, to the extent required by applicable law.
13Physical security
Access to Fidify physical facilities is protected by personal key cards and a secret PIN. In addition, sensitive areas such as network, legal documents and internal IT are protected. All access (successful or attempted) is monitored, alerted and logged.
Fidify uses Google Cloud for server, network and storage infrastructure. Google is certified to the ISO 27001 standard, with its clear focus on, for example, access control, physical security and handling of physical media and devices.
The Google Cloud Security whitepaper, which covers physical security:
https://cloud.google.com/security/overview/whitepaper
The Google Infrastructure Security Design Overview, which details physical security measures:
https://cloud.google.com/security/infrastructure/design
The “Data Processing and Security Terms” page, which includes information about data storage handling:
https://cloud.google.com/terms/data-processing-terms
14Sub-processors
Fidify engages sub-processors such as data centre operators to deliver the Services and to process data on Fidify’s and its customers’ behalf, in accordance with the Fidify Data Processing Addendum (DPA). The sub-processors’ data centres are as a minimum ISO 27001-certified. An up-to-date list of sub-processors and their processing locations is maintained at fidifygroup.com/subprocessors. Documentation of the technical and organisational measures of the respective sub-processor is available on request.
15Regulatory cooperation and audit rights
Where the Customer is a regulated financial entity, Fidify will provide the Customer, on reasonable request, with the information the Customer reasonably requires to comply with its regulatory obligations relating to the use of ICT third-party services (for EU customers, including the key contractual provisions under Art. 30 of Regulation (EU) 2022/2554 (DORA) and information needed to maintain its register of information under Art. 28(3) DORA). The full set of regulatory cooperation commitments is set out in section 15 of the Fidify General Terms and Conditions.
The Customer, its auditors and its competent authorities (and any person appointed by them) have the right to access, inspect and audit Fidify’s relevant premises, systems and records in connection with the Services, in accordance with the audit provisions of the DPA and section 15 of the Fidify General Terms and Conditions. Fidify will make available the results of any relevant third-party audit or certification to reduce the need for individual on-site audits where appropriate.
Fidify will cooperate with the Customer’s competent authorities and support the Customer with incident reporting and the testing of operational resilience to the extent relevant to the Services.
16Incident management and notification
Fidify maintains an incident management procedure as part of its ISMS documentation. In the event of a personal data breach, Fidify will notify the Customer without undue delay after becoming aware of the breach, in accordance with the DPA and Art. 33 GDPR, and will support the Customer in assessing whether notification to affected data subjects is required under Art. 34 GDPR. Where the Services support a critical or important function of a regulated Customer, Fidify will also assist the Customer with ICT-related incident reporting to the Customer’s competent authorities as required under the applicable outsourcing rules (for EU customers, Art. 19 of Regulation (EU) 2022/2554 (DORA)).