Build with AIPlan for data protection

Your app is taking shape. MainPath brings hosting, access rights and data protection documents together, so your team can explain how it runs before your first customer asks.

Example: DPA and TOM documents as part of your project foundation

The important questionsBefore the first release

Running your application involves more than choosing a server region. MainPath helps you address these points concretely.

  • What runs where?

    Processing locations for platform operations are documented. You decide where your connected application servers are hosted.

  • Which documents are available?

    Organisation admins can generate and download personalised DPA and TOM documents in MainPath.

  • Who can access the project?

    Organisations, roles and project memberships determine your team’s access.

  • Which services are connected?

    Your own connections, such as Sentry or an email service, belong in your review of the data flows.

A shared foundationWith clear responsibilities

MainPath provides

  • Documentation of platform operations and processing locations
  • Personalised data protection documents for your organisation
  • Roles, access rights and an audit log of changes

Your team decides

  • Which personal data your application needs
  • Where the application runs and which additional services it uses
  • Which access rights and measures fit your use case

The documents describe platform services. Assessing your application and its data flows remains your responsibility.

Give the right accessFor each role in your team

When several people build a project with AI, access credentials do not need to end up in chats or personal scripts. Assign appropriate roles and project access in MainPath.

  • Grant access to the right projects
  • Match roles to the team’s responsibilities
  • Follow changes in the audit log
Explore access rights

From your ideato a setup you can explain

  1. Review the documents

    Add your organisation details and review the DPA, TOMs and service scope in MainPath.

  2. Choose your hosting

    Decide which servers run your application and record the additional services you use.

  3. Set up access

    Invite your team, assign appropriate rights and add the information needed for your own data protection review.

Your projectWith a clear foundation

Explore the documents and access controls MainPath provides for your organisation. Discuss the setup with your IT and data protection team before getting started.

Questions about hosting and data protection

Does MainPath make our application GDPR-compliant automatically?

No. MainPath provides technical and contractual groundwork for platform operations. Your team assesses the data your application processes and any additional requirements for your use case.

Which documents can we download?

Organisation admins can generate personalised documents under Compliance and contracts, including the DPA, TOMs and a description of the service scope. The documents use your stored organisation details.

Compliance and contracts

Does everything run exclusively in the EU?

MainPath’s primary hosting is in Germany. Individual platform services and connections you enable may involve other processing locations. The compliance overview describes platform operations; you review additional services separately.

View processing locations

Can we keep our own servers and services?

Yes. You can connect your own servers. You can also connect additional services, such as SMTP or Sentry, using your own credentials. Assess and document those connections and your application’s data flows for your project.

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