data protection

Data processing agreement under the FADP: when you need one

AA
Aurum Avis Labs Author
9 min read

Data processing agreement under the FADP: when you need one

You need a data processing agreement under the Swiss FADP whenever another organisation processes personal data on your instructions and you remain the controller. That covers your managed service provider, payroll bureau, newsletter tool, CRM host, backup provider, and most cloud subscriptions where customer or employee data sit on someone else’s servers. Art. 9 FADP requires a contract or another legal instrument with minimum content. The agreement does not replace your own security measures under Art. 8 FADP, but without it you lack a clear basis to instruct, audit, and stop processing.

This is for owners and the person who signs IT contracts in a Swiss company with about 20 to 250 staff. You may have been asked for a «DPA» in a customer audit or noticed that Microsoft and your MSP mention «data processing» in small print. This article is about Switzerland and Art. 9, not about transfers to the United States. It is orientation, not legal advice.

Who is controller and who is processor

You are the controller when you decide why and how personal data are processed: customer files, applicant CVs, employee payroll, patient lists in a practice, tenant dossiers. The processor acts only on your documented instructions. Your IT partner who administers Microsoft 365 mailboxes for your tenant is typically a processor for the content they can access. Microsoft as host is often another processor in the chain. A fiduciary who runs your books on their system may be controller for some data and processor for others; the contract should say which role applies to which dataset.

If a supplier uses your data for its own analytics, product improvement, or unrelated marketing, that goes beyond processing on your behalf. That needs a separate legal basis and is not «just an AVV».

  • Art. 9 FADPContract required

    Written agreement or equivalent with defined minimum points.

  • Your dutyArt. 8

    You still implement appropriate technical and organisational security.

  • SubprocessorsDisclosure

    Processors need your authorisation or general permission plus information on changes.

  • BreachCooperation

    Processor must help you meet notification duties where a high risk is likely.

What the contract must cover

Swiss law lists topics the agreement must address: subject matter and duration of processing, nature and purpose, type of personal data and categories of data subjects, your obligations and rights, and what the processor may and may not do. In practice, vendor «data protection addenda» often mirror GDPR wording; for a Swiss controller they still work if the substance matches Art. 9.

Check that the document says the processor processes only on your instructions, keeps confidentiality, ensures security, uses subprocessors only with permission, assists with data subject requests and breach handling, deletes or returns data at the end, and allows audits or provides audit reports. If the vendor is outside Switzerland, the agreement should describe how cross-border disclosure is regulated. That is a different question from whether the United States is an adequate destination.

How you actually get the document

Large cloud vendors embed processing terms in online conditions and offer a downloadable PDF. That counts as a legal instrument if you can show you use the service under those terms. Store the date, version, and link in a «processor agreements» folder, not only an undated screenshot.

An MSP or niche supplier often sends its own PDF. Read whether it states that the partner acts only on your instructions and which subprocessors it uses for backup, monitoring, or support. If the contract lists your duties but stays silent on the processor’s duties, a core Art. 9 point is missing.

When you buy a tool on a credit card, there may be no signature. You still need the minimum content for anyone who processes personal data on your behalf. Request the vendor’s standard DPA before you import employee or customer data.

Typical partners in a KMU

Managed service providers with admin access to mail, identities, or backups almost always need an agreement. Payroll and HR software, applicant tracking, marketing automation, and survey tools process employee or contact data. Industry software (practice management, property administration, legal case tools) often hosts sensitive data; the vendor’s terms plus a processing annex matter for insurer and customer questionnaires.

Software you only install on your own servers in Switzerland may still use a support engineer abroad who can see screens; ask the partner how they handle remote support access. A spreadsheet on a shared drive without a vendor is still your responsibility under Art. 8; there is no processor contract, but access control becomes critical.

Subprocessors when the chain changes

Many agreements allow subprocessors with your consent or with general permission plus a list. When the vendor adds a new data centre, backup tool, or support location, you need a way to learn about it. In practice an email newsletter or trust-centre entry is enough. Decide internally who reads those notices (IT, privacy contact, management).

If a partner refuses to name subprocessors, you do not know who sees your data. Treat that as procurement risk, not only a legal footnote.

Who can postpone the paperwork

A sole proprietorship that keeps all customer data in a paper ledger and never uses cloud tools has fewer processors. Once mail and files move to a hosted tenant, the exception disappears. Groups under 250 employees are exempt from a full processing register in many cases (Art. 24 of the Data Protection Ordinance), but that exemption does not remove Art. 9 for each processor relationship.

What an AVV is not

It is not proof that processing is lawful for every purpose you invent later. It is not a substitute for telling staff how to handle applications and customer mail. It does not automatically solve international transfers. It does not mean the processor is liable for your decision to collect excessive data.

Customer audits sometimes ask for a «GDPR DPA»; Swiss controllers can point to Art. 9 FADP and the signed addendum. For training, the wording is «training on the FADP and the GDPR»: a session does not make a company «compliant».

When not to wait

  • New cloud service holding customer or payroll data
  • MSP with admin rights on mail and identities
  • Customer audit or insurer questionnaire due soon

When you can sort later

  • Space-only warehouse with no access to contents
  • Software on your own servers with no third-party access
  • Paper archives with no digital processing by others

Checklist: a new service that holds personal data

  • Write one line on the service and purpose (mail, payroll, CRM, backup)
  • Check whether the vendor offers a processing addendum or online DPA
  • Save the subprocessor list or trust-centre link
  • Store PDF or confirmation with date in «Processor agreements 2026»
  • Ask your IT partner which tools it adds as subprocessors on your tenant

A made-up example: three contracts in one quarter

A made-up example: a metal parts distributor with 45 staff uses Microsoft 365, an external IT firm with global admin rights, a Swiss payroll provider, and a simple CRM in the cloud. The owner lists every service that stores names, mail, or salary data. Microsoft’s online terms include a processing section; the owner downloads the PDF for the audit folder. The IT partner signs its own DPA on request and lists backup and monitoring subprocessors. Payroll already had a contract; HR adds a one-page processing appendix that references Art. 9 and breach notification «as soon as possible» to the controller, as the FDPIC guide on data security breaches describes for controllers. CRM was bought on a credit card years ago; the owner logs in, finds no DPA, opens a ticket, and receives a standard addendum within two weeks. No project team, only a shared checklist and a folder «Processor agreements 2026».

The gap was visibility, not a new law. The next step was access reviews, not renegotiating every price.

What to do first

List services that hold personal data. Mark which have a signed or click-wrapped processing term. For gaps, request the vendor template before renewal. Align with your IT partner on subprocessors they add when they install backup or security tools. Store copies where finance and the audit contact can find them. Link retention for applicant files to your HR practice; our guide on how long to keep job applications in Switzerland complements processor lists for recruiting tools.

If staff mishandle data despite contracts, a live data protection awareness session covers everyday rules, breach thresholds, and what «high risk» means for notification to the FDPIC, without promising legal certainty.

Is a verbal OK with our IT guy enough?

Art. 9 expects a contract or another legal instrument with defined content. A long-standing handshake does not replace that for audit or insurance questions.

Does every cloud service need its own DPA?

Yes, once the vendor processes personal data on your behalf. A contract with your MSP does not replace Microsoft’s, Salesforce’s, or the payroll bureau’s addendum. Each relationship needs its basis.

Does Art. 9 apply to paper-only archives stored at a warehouse?

If a company stores your files without deciding purposes, it may act as processor. If it only rents space and never opens cartons, the analysis differs. Ask your adviser when the line is unclear.

Is a GDPR template from the internet enough?

It can be a starting point if it covers every Art. 9 minimum point and matches your service. Have it reviewed when sensitive data or many subprocessors are involved.

data protection fadp contracts cloud
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.