Data Protection & GDPR
Last updated: 2026-11-11
Roles under GDPR
For customer data processed in the platform, the customer is the data controller and Klart is the data processor. Klart is a trading name; the contracting legal entity is Lexabit AB (Sweden) or its Danish entity Lexabit ApS, depending on which entity the customer's agreement is with. Contracts, DPAs and invoices therefore name a Lexabit entity, and the processing described in this Trust Center is the same in either case. Klart enters into a Data Processing Agreement (GDPR Article 28) with each customer. The agreement is available on request from compliance@klart.com.
Data we process
| Category | Examples | Source |
|---|---|---|
| Account & user data | Login credentials, session and authentication metadata | Created at sign-up / sign-in |
| Client & case records | Client and case records the customer creates in the platform | Entered by the customer |
| Bank account & transaction data | Account and transaction data from connected bank accounts | Retrieved under an authorized PSD2 consent through regulated open-banking providers (currently Enable Banking) |
| Company & registry data | Public company information plus registered role holders (directors, board members — name, date of birth, address) and beneficial owners | Public national business registries via Klart's self-hosted data registry |
| Audit logs | Integration activity and login metadata | Recorded by the platform's logging infrastructure |
Data residency
Klart is hosted entirely on DigitalOcean in Amsterdam — the application server, database, and CDN all run in the Amsterdam region, with object storage in the DO Spaces AMS3 region. All customer data therefore resides within the EU (Netherlands). The self-hosted MongoDB registry — on the same Amsterdam infrastructure — holds this public-registry dataset; it does not contain the customer's own client, case, or user data.
Retention & deletion
Data is retained for as long as the customer's account remains active and used to deliver the platform's features. Logs and audit records are kept for fixed periods, after which they are deleted automatically:
| Record | Retention |
|---|---|
| Application logs | 7 days |
| Debugging data (request and job traces) | 7 days |
| Integration HTTP logs | 14 days |
| Security log (credential access, security notification events) | 90 days |
| Platform audit events | 90 days |
| Audit events for access, permission and feature-activation changes | At least 1 year |
| Financial records (subscriptions, charges, payments) | For the life of the customer account |
| Administrative, integration, file-access and credential audit trails | For the life of the customer account |
Requests for data deletion or erasure are handled operationally by contacting the compliance contact below.
Data-subject rights
Data subjects can access and correct their personal data through the application's normal features (for example, account and profile settings). Requests for data export or erasure beyond what the application supports are handled by contacting compliance@klart.com.
Sub-processors
Klart uses a small number of sub-processors to deliver the platform, including hosting and outbound email , and lists operational service providers where customer personal data may incidentally appear. Open-banking and company-data providers are used under a different model — see Sub-processors & Service Providers and Banking & Data Providers for details.