← Back to blog

DPA and TOMs from your organisation details

The documents MainPath introduced on 5 August 2026, the organisation details they use and how to prepare them for review.

ComplianceOrganisations
DPA and TOMs from your organisation details

Before a project starts, a customer asks for the data processing agreement and a list of the services involved. If the paperwork lives in old messages or separate project folders, the team first has to find the relevant version.

On 5 August 2026, MainPath introduced a dedicated compliance area. It generates documents from the details and configuration of your organisation.

Four documents and a list of providers

Four documents are available for every organisation, each in German and English:

  • Data processing agreement (DPA). The contract between you and MainPath as the processor
  • Technical and organisational measures (TOMs). The safeguards that apply to access, transmission and availability
  • Privacy policy. How processing works in the context of MainPath
  • Scope statement. What MainPath takes on and where your responsibility begins

There is also a list of subprocessors showing which services are involved in processing. Customers can use it when preparing their own documentation.

Each document can be downloaded as a PDF. A ZIP export brings all the documents together for a single handover.

Bring company details and project services together

In your organisation settings, you enter the company name, address and contact person. Those details flow automatically into the generated PDFs. Check them before exporting, especially if the address or responsible person has changed.

The project overview also shows the services in use. If one project uses Firebase, another Sentry and a third Mailtrap, the compliance area lets you see those assignments together.

The audit log complements the paperwork with evidence of who changed what and when. The audit log complements the paperwork with evidence of who changed what and when.
The audit log complements the paperwork with evidence of who changed what and when.

Share the documents with customers and reviewers

Starting a customer project. When a new customer asks for data protection paperwork before signing, you can provide the documents as a ZIP for review.

Audits and certifications. An ISO 27001 review may ask for evidence of the providers involved and the agreements in place. The documents help bring that information together. Which evidence meets the requirements of a particular review still needs to be established separately.

Tenders. In the public sector and regulated industries, a DPA and TOMs are often among the requested documents. The export provides material you can compare with the tender requirements.

What the documents cover

MainPath provides documents and describes processing on its side. This does not replace legal advice. Discuss with your legal counsel whether your use case needs additional measures, such as a data protection impact assessment for particularly sensitive data. The generated documents support that review; they do not automatically establish the legal suitability of your entire project.

Data processing and operation in the EU

The compliance area complements operation and data processing in the EU on servers you select yourself. For teams working with public sector, healthcare or finance customers, the operating location and supporting documentation are often part of the project requirements. Read more on the page about hosting in the EU.

Prepare the paperwork for your next customer request

Create your organisation with its company name, address and contact person. These details form the basis of the documents you can pass on for review.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab