Skip to main content

Sub-processors & Service Providers

Last updated: 2026-11-12

This page lists the third parties involved in delivering Klart, in three categories that reflect how each one actually touches data. We list deliberately inclusively — where there is any realistic path for customer personal data to reach a vendor, we would rather disclose it than argue it away.

Sub-processors​

Sub-processors are third parties that process customer personal data on Klart's behalf, engaged under GDPR Article 28, as part of delivering or supporting the service. Each processes data only to the extent needed for its stated function.

ProviderPurposeData categoriesRegionStatus
DigitalOcean, LLCCloud infrastructure hosting (servers, database, object storage, CDN) All platform data Amsterdam, Netherlands (EU) Active
Railsware Products Studio LLCMailtrap — outbound transactional email delivery Email addresses and notification content EU/US (provider-operated)Active
Google Cloud EMEA LimitedGoogle Workspace — internal business email and customer support correspondence (Google Cloud EMEA Limited is Google's EMEA contracting entity for Workspace) Correspondence with customer staff EU/US (provider-operated)Active

Service providers​

Operational tools we use to run the company. They are not engaged to process customer data, and no customer data is shared with them by design — but day-to-day work (support coordination, issue tracking) means customer personal data may incidentally appear in them, for example in a support ticket that quotes a customer email. We list them for exactly that reason.

ProviderPurposeExposureRegion
Slack Technologies Limited (Salesforce)Internal team communicationIncidental — customer context may be referenced in internal discussionEU/US (provider-operated)
Linear Orbit, Inc.Issue tracking and development planningIncidental — tickets may reference customer contextEU/US (provider-operated)

Slack also appears in the Data Processing Agreement's approved sub-processor list — it is included there for completeness under the same over-inclusive principle as this page; the actual engagement is as described here.

Banking & data partners​

Regulated parties we retrieve data from. They act under their own regulatory obligations and the end user's consent — Klart does not share customer data with them or instruct them to process data on Klart's behalf, so they are not sub-processors in the Article 28 sense. For transparency, every open-banking provider we have built or may build an integration for is listed here with its honest current status (mirroring Banking & Data Providers). Only Enable Banking is in use today.

ProviderPurposeBasisRegionStatus
Enable Banking OyOpen-banking (PSD2) account and transaction retrievalAuthorized TPP, supervised by its national FSA; access authorized by the end user at their bank EEAActive
Neonomics ASOpen-banking (PSD2) account and transaction retrievalAuthorized TPP; no data flows todayEEAIntegration built — not active
Tink ABOpen-banking (PSD2)Authorized TPP; not integrated, no data flowsEEANot yet integrated
Aiia A/S (a Mastercard company)Open-banking (PSD2)Authorized TPP; not integrated, no data flowsEEANot yet integrated

Enable Banking also appears in the Data Processing Agreement's approved sub-processor list — included there for completeness; the engagement model is as described here and on Banking & Data Providers, and Klart does not instruct it to process customer data on our behalf.

Public national business registries feed the self-hosted Data Registry; how each source is engaged is described on Banking & Data Providers.

MongoDB is self-hosted on Klart's own DigitalOcean infrastructure and is not a third-party sub-processor.

Changes to this list are announced to customers in advance. A downloadable export lives on the Downloads page. Questions: compliance@klart.com.