The right documents
Up-to-date links to data processing agreements (DPAs), privacy policies, and providers’ own subprocessor lists.
SUBPROCESSOR MANAGEMENT, SIMPLIFIED
Your subprocessor list might already be out of date. You just don’t know it yet.
New services enter your stack. Provider details change. DPA links move. Komplya helps you spot what needs review, understand why, and decide what to update.
Built in Sweden. Hosted in Europe.
Built for teams across Europe.
From a change to your published list
New information comes in
Cloudline updates its DPA with a new processing location.
Komplya suggests a next step
Check whether the new location applies to your service.
Possible update: add the Netherlands to Cloudline’s processing locations.
You review
Check your contract and setup. Accept, edit, or dismiss the suggested change.
You publish
Publish the updated entry when you’re ready. Your list stays under your control.
New information comes in
The optional CLI spots a Postbird email SDK in your dependency list.
Komplya suggests a next step
Confirm whether you use Postbird to send emails containing personal data.
If this is a subprocessor relationship, consider adding Postbird to your list.
You review
Confirm how you use it. Add the provider with your own purpose text, or dismiss the suggestion.
You publish
Review the new entry and publish when you’re ready. A package never adds itself to your list.
Provider research, maintained for you. Every decision stays yours.A closer look
PROVIDER RESEARCH, TAKEN OFF YOUR PLATE
Your providers change. Your list should keep up.
Keeping a list accurate means knowing what changed since your last review. Komplya brings together current DPA links, service details, and processing locations, with background research that explains what deserves your attention.
The details that matter
Provider and service information, processing locations, and the sources behind our recommendations.
A reason to review
Relevant changes brought to your attention, with an explanation and a suggested next step.
Start with the list you have
Add the providers you already list and describe how you use them. Komplya brings the provider research; you bring your business context.
Understand the relationship
See why a service might belong on your list, with relevant documentation, explained recommendations, and open questions.
Review, then publish
Accept, adjust, or dismiss a suggestion. Publish the changes you approve, when you’re ready.
FROM YOUR STACK TO YOUR SUBPROCESSOR LIST
Find potential subprocessors with the Komplya CLI.
Add the Komplya command-line tool to your CI pipeline. As your dependencies change, Komplya spots services your list may be missing and suggests what the person responsible for the list should review.
The CLI reads only your dependency lists. It never reads, scans, or uploads your application source code. The Komplya CLI is open source, so you can verify exactly what it reads and sends.
The CLI is optional. You can always add providers yourself.
A change in your dependencies
A service SDK appears
A useful signal from your development workflow.
Komplya suggests a closer look
What does the package do? Does your use send personal data to a provider?
You decide what it means
Review the context before changing your list.
A dependency is a clue. Your actual use determines the relationship.
Who is Komplya for?
Komplya is for software teams across Europe that process customer data and maintain a subprocessor list. It gives developers and the people responsible for that list a shared view of provider information and recommendations.
What provider information does Komplya maintain?
Komplya curates provider and service details, current links to DPAs and privacy policies, processing locations, and providers’ own subprocessor lists. Recommendations include their sources and a suggested next step when relevant information changes.
Does Komplya decide who our subprocessors are?
No. Komplya offers recommendations with reasoning and sources. Your actual use of a service matters, and you may reach a different conclusion. You decide which providers belong on your list and what you publish.
Does the CLI access our source code?
No. The optional Komplya CLI reads dependency lists only; it does not read, scan, or upload application source code. The CLI is open source, so you can inspect what it reads and sends. You can also add providers yourself.
REQUEST EARLY ACCESS
Know when your list needs another look.
Komplya brings relevant changes, the evidence behind them, and suggested next steps into one place. You decide what belongs on your list and when to publish.