How Fidify protects client data

Published DPA. Named DPO at dpo@fidify.se. Application-level encryption. Completed DDQs available on request.
  • Independent penetration testCompleted
  • ISO/IEC 27001:2022Planned
  • SOC 2Planned
  • Data protection officerdpo@fidify.se

Encryption, residency and isolation

Encrypted with a key for every file

Every document is encrypted with its own AES-256-GCM key before it is stored. On the Fidify App, encryption happens on the phone. 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 Enterprise decrypts only inside the firm's dedicated environment. Fidify Business decrypts inside the workspace service, which Fidify operates.

Where your data lives

Client records and documents are stored in the EU, on Google Cloud. Where a client needs its data in another legal area, we host it there as part of implementation. Services that process data elsewhere are listed on our sub-processor page.

Organization isolation

Your organisation runs in its own environment with its own database. Your client records are not rows in a table you share with another customer. A small number of platform services are common to all deployments and keep each customer data separated; we will take your reviewers through exactly which is which.

GDPR-aligned

Published DPA. Named Data Protection Officer reachable at dpo@fidify.se. Sub-processor list available and kept current.

Certifications & audits

We will not display certifications we have not earned. Each audit is listed with its real status, and a date is added only once an assessor is engaged.

Independent penetration test

Independent test, January 2026

Completed

ISO/IEC 27001:2022

Certification planned

Planned

SOC 2

Type I report planned

Planned

Controls overview

A plain-language summary of the controls in place. For full technical detail (algorithms, retention windows, patching SLAs, and more) see our Technical & Organisational Measures document.

Encryption

Industry-standard encryption at rest and in transit, plus a separate AES-256-GCM key for every uploaded document. Documents from the Fidify App are encrypted on the phone.

Access control

Least-privilege access with named, MFA-protected personal accounts. No shared credentials. Production access is audited.

Vulnerability management

Automated dependency and code scanning on every build. Independent penetration test completed in January 2026. Defined patching cadence by severity.

Incident response

Documented incident management procedure with centralised logging held in the EU and a defined breach-notification process aligned to GDPR Article 33.

Backups & recovery

Databases are backed up continuously, with 30-day point-in-time recovery. Encrypted backups are kept in the EU.

Change management

Mandatory automated and manual testing before release. Separated development, test, and production environments.

AI model choice

Choose between Google, Anthropic and OpenAI models for each environment. Your AI usage is metered and visible, and no content is used to train the providers' models.

Data handling

Where data lives

Client records and documents are stored in the EU, on Google Cloud. Where a client needs its data in another legal area, we host it there as part of implementation. Services that process data elsewhere are listed on our sub-processor page. Customer remains the data controller; Fidify is the processor.

Sub-processors

We publish the current sub-processor list and notify customers of changes in line with the DPA. Every sub-processor is bound by a written data processing agreement.

Retention & deletion

Customers control retention. On termination, customer data is exported on request and deleted from active systems within the contracted window.

Personal data in logs

We avoid writing identifying personal data to application logs.

Security contact & responsible disclosure

Found a vulnerability? Need a DDQ filled? Reach the security team directly at security@fidify.se.