devXY Logo

devXY Cloud

Data Processing Agreement

How devXY GmbH processes personal data on your behalf in devXY Cloud.

Last updated: 15 November 2026

Scope and roles

This data processing agreement ("DPA") is between devXY GmbH, Neuhofstrasse 3c, 6340 Baar, Switzerland ("we"), and the customer that uses devXY Cloud under our Terms of Service ("you"). It forms part of the Terms of Service and applies for as long as they do.

It covers the personal data that you and your users store in, or send to, the applications your organization runs on devXY Cloud ("customer data"). For customer data, you are the controller and we are your processor. If you yourself process customer data on behalf of another controller, we are your sub-processor, and you are responsible for passing on that controller's instructions to us.

This DPA does not cover the data we process as a controller in our own right, such as portal accounts, audit logs, support requests and billing records. Our Privacy Policy describes that processing.

This DPA is meant to meet Article 28(3) of the EU General Data Protection Regulation ("GDPR") and Article 9 of the Swiss Federal Act on Data Protection ("FADP"). Terms such as "personal data", "controller", "processor" and "personal data breach" have the meaning given in the GDPR, or the equivalent meaning in the FADP.

Subject matter and duration

The subject matter of the processing is providing devXY Cloud to you as described in the Terms of Service: running the applications you select, storing their data and files, backing them up, and delivering the emails they send.

The processing lasts as long as we provide devXY Cloud to you, and afterwards until we have deleted customer data as described under Deletion and return.

Nature and purpose of the processing

We host, store, back up, restore, transmit and delete customer data, and run the applications that process it. Where your applications send emails and your organization has not configured its own mail server, we deliver those emails.

We process customer data only to provide, secure and support devXY Cloud for you. We do not use it for our own purposes, do not sell it, and do not combine it with other customers' data.

Types of personal data and categories of data subjects

You decide which applications you run and which data you store in them, so the types of personal data and the categories of data subjects depend on your use. They typically include:

  • Data subjects: your users of the hosted applications, such as employees and contractors, and the people whose data you or they store in those applications, such as customers, contacts and meeting participants.
  • Types of personal data: names, email addresses, account and sign-in details within the applications, content and files that users create or upload, calendar and booking details, and technical data such as IP addresses that the applications receive.

You must not store special categories of personal data (Article 9 GDPR) or data on criminal convictions (Article 10 GDPR), or sensitive personal data under the FADP, unless you have checked that the measures described in this DPA are adequate for it.

Processing only on your instructions

We process customer data only on your documented instructions, including with regard to transfers to a third country, unless the law of Switzerland, the European Union or an EU member state to which we are subject requires otherwise. In that case, we tell you about that legal requirement before processing, unless the law prohibits this on important grounds of public interest.

Your instructions are:

  • the Terms of Service and this DPA;
  • the settings you and your owners and admins choose in the portal, such as the applications, region and resources of each instance; and
  • further instructions that an owner or admin of your organization gives us in writing, including by email or support request, as long as they are within the scope of devXY Cloud.

We tell you without delay if we believe that an instruction infringes the GDPR, the FADP or other data protection law. We may then suspend carrying out that instruction until you confirm or change it.

Confidentiality

We make sure that everyone we authorize to process customer data is bound by confidentiality, by contract or by law, and processes it only on your instructions.

Our staff access customer data only where this is needed to provide or support the service. If a devXY administrator acts on one of your instances without being a member of your organization, the portal requires a reason and records the action and its reason in your organization's audit log.

Security of processing

We take the technical and organizational measures required by Article 32 GDPR and Article 8 FADP to protect customer data, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing. The measures in place are described under Technical and organizational measures.

We may change these measures as technology and threats develop, as long as the overall level of protection does not decrease.

You are responsible for the security of what you control: the configuration and use of your applications, the accounts and permissions you grant, and the secrets and credentials you manage.

Sub-processors

You give us general authorization to engage sub-processors to process customer data. The sub-processors we use, with their location and purpose, are listed in our Privacy Policy under Sub-processors for devXY Cloud. That list forms part of this DPA.

Before we add or replace a sub-processor, we update that list and email the owners and admins of your organization at least 30 days in advance. You may object to the change on reasonable data protection grounds by emailing mail@devxy.io within that period. If we cannot resolve your objection, for example by not using the new sub-processor for your data, you may terminate the affected part of devXY Cloud before the change takes effect, without a cancellation fee.

We impose on each sub-processor, by contract, data protection obligations that offer at least the same level of protection as this DPA, in particular sufficient guarantees for appropriate technical and organizational measures. We remain responsible to you for our sub-processors' performance of their obligations.

Assistance

Data subject requests

Taking into account the nature of the processing, we help you with appropriate technical and organizational measures to respond to requests from data subjects who exercise their rights under Chapter III GDPR or the FADP. If a data subject contacts us about customer data, we forward the request to you where we can identify your organization, and we do not answer it ourselves unless you instruct us to. You can access, correct, export and delete customer data through the applications you run.

Articles 32 to 36 GDPR

Taking into account the nature of the processing and the information available to us, we help you meet your obligations on the security of processing, the notification of personal data breaches, data protection impact assessments, and prior consultation with a supervisory authority. We do so in particular by providing the information in this DPA and the information about devXY Cloud that you reasonably request.

Assistance that goes beyond the functions of devXY Cloud and the information in this DPA may be charged at our usual rates, after we have told you the expected cost. We do not charge for assistance with a personal data breach caused by us or our sub-processors.

Personal data breaches

We notify you without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting customer data. We send the notice by email to the owners and admins of your organization.

As far as it is available to us, the notice describes:

  • the nature of the breach, including, where possible, the categories and approximate number of data subjects and records concerned;
  • the likely consequences of the breach;
  • the measures we have taken or propose to take to address the breach and to mitigate its possible adverse effects; and
  • a contact point for more information.

Where we cannot provide all of this at once, we provide it in phases without further undue delay. Notifying you is not an acknowledgement of fault or liability. You remain responsible for notifying supervisory authorities and data subjects where the law requires it.

Deletion and return at the end of the service

You can export customer data from your applications at any time until the cancellation of devXY Cloud takes effect. This is how customer data is returned to you.

After the cancellation takes effect, your applications stop, and we delete them and customer data as set out in the Terms of Service, after at least 14 days. We delete live customer data no later than 30 days after the cancellation takes effect.Backups that contain customer data are deleted automatically within 35 days of being made.

We keep customer data for longer only where the law of Switzerland, the European Union or an EU member state requires us to store it. In that case, we keep it confidential and process it only for the purpose the law requires.

Information and audits

We make available to you all information necessary to demonstrate compliance with Article 28 GDPR and Article 9 FADP. We allow for and contribute to audits, including inspections, conducted by you or by an auditor you mandate.

Audits are subject to the following conditions:

  • we first answer your questions in writing, and an on-site or remote audit takes place where that information is not enough to demonstrate compliance;
  • you give us at least 30 days' notice in writing, unless a supervisory authority requires a shorter period or there is a personal data breach;
  • audits take place at most once in any 12 months, unless a supervisory authority requires it or after a personal data breach affecting customer data;
  • audits take place during our normal business hours and do not unreasonably disrupt our operations;
  • the auditor is bound by confidentiality and is not our competitor;
  • audits do not give access to other customers' data, and access to our sub-processors' data centers is subject to what they allow; and
  • you bear your own costs, and you pay our reasonable costs for an audit, unless it reveals that we have materially breached this DPA.

International transfers

Customer data is processed in Switzerland and in the European Economic Area. The region you choose for each application determines where it runs and where its backups are stored, as described in our Privacy Policy under Hosting regions.

Switzerland is recognized by the European Commission as providing an adequate level of data protection, and the Swiss Federal Council recognizes the countries of the European Economic Area as providing an adequate level of protection.

We do not transfer customer data to a country without such an adequacy decision unless you instruct us to. If a sub-processor change would involve such a transfer, we tell you in the notice described under Sub-processors, and we make the transfer only with appropriate safeguards, such as the standard contractual clauses of the European Commission, as recognized under the FADP, and supplementary measures where required.

Swiss Federal Act on Data Protection

Where the FADP applies to customer data, this DPA is also a processing agreement under Article 9 FADP. In particular:

  • we process customer data only in the way you would be permitted to process it yourself (Article 9(1)(a) FADP);
  • we ensure data security as described in this DPA (Articles 8 and 9(2) FADP);
  • we engage sub-processors only with your prior authorization, which you give as described under Sub-processors (Article 9(3) FADP); and
  • we notify you as soon as possible of any breach of data security (Article 24(3) FADP), as described under Personal data breaches.

References in this DPA to the GDPR apply to processing under the FADP with the meaning of the equivalent provisions of the FADP, and the Federal Data Protection and Information Commissioner (FDPIC) is a supervisory authority within the meaning of this DPA.

Liability

Each party's liability under this DPA is subject to the Liability section of the Terms of Service. This does not limit either party's liability to data subjects under Article 82 GDPR or other mandatory law.

Precedence and changes

If this DPA conflicts with the Terms of Service on the processing of customer data, this DPA takes precedence. Otherwise, the Terms of Service apply, including their provisions on governing law and jurisdiction.

We may update this DPA. We email owners and admins at least 30 days before an important change takes effect, unless the change is required by law, and you may cancel before then. The current version is always on this page.

This DPA applies without a signature, as part of the Terms of Service.

Technical and organizational measures

This section describes the measures in place for devXY Cloud as of the date shown above.

Access to the portal

  • Sign-in to the portal goes through our own identity provider at auth.devxy.io, based on ZITADEL, and requires a verified email address.
  • Access is by invitation: an account can sign in only after we have granted it access.
  • Your organization can connect its own identity provider for single sign-on.
  • Each member has a role in the organization, and access to individual applications is granted per member.
  • A devXY administrator who acts on an instance of an organization they do not belong to must give a reason, which is recorded in that organization's audit log.

Separation between customers

  • Every application instance runs in its own Kubernetes namespace, which enforces the restricted Pod Security Standard.
  • All network traffic to and from an instance is denied by default; only the shared HTTPS gateway, and our monitoring where configured, may reach the application, and only on the port it serves.
  • Application containers run as a non-root user, cannot escalate privileges, have all Linux capabilities removed, and use a read-only root filesystem unless the application needs a writable one.
  • Resource quotas limit each instance and each organization.

Databases

  • Each instance that needs a database receives its own database and its own restricted login role.
  • Applications connect to their database over TLS.
  • In the Germany region, the database server accepts an instance's login only for that instance's own database, only over TLS and only with SCRAM-SHA-256 password authentication, and rejects all other connections.
  • In the Germany region, the database cluster runs three replicas.

Encryption and secrets

  • Applications are reached only over HTTPS, and plain HTTP requests are redirected to HTTPS.
  • Single sign-on client secrets of instances and stored mail server passwords are encrypted in the portal database with AES-256-GCM.
  • The encryption key and infrastructure credentials are kept in OpenBao and delivered to the services that need them, not stored in source code.
  • Database backups of the Switzerland region are encrypted on our side with AES-256 before they are uploaded.
  • Backups are uploaded to object storage over HTTPS.

Availability and backups

  • In the Germany region, database changes are archived continuously and a full database backup is taken daily, to object storage in Paris, France.
  • In the Switzerland region, database backups are stored in object storage in Geneva, which is replicated to a second data center in Switzerland.
  • Snapshots of application files are stored on the storage cluster in the same region.
  • Every backup is deleted automatically within 35 days of being made.

Logging

  • The portal records administrative actions, such as changes to instances, members and roles, with the actor and, where available, the IP address and browser user agent.
  • Owners and admins can view their organization's audit log in the portal.
  • Audit log entries are kept for 365 days.

Physical security

Our servers run in data centers operated by the sub-processors listed in our Privacy Policy, which control physical access to them.