In short: your CRM vendor processes your customers’ data on your behalf, and the data processing agreement under the revised Federal Act on Data Protection (FADP) sets out what it may do with that data. Nine clauses make the difference: purposes, instructions, location, security, sub-processors, transfers, breach notification, assistance and termination. Check them before you sign, then again each time the DPA is updated.
The FADP data processing agreement, or DPA, is accepted with a single click at sign-up and never read again. Yet it is the document you will have to produce if a client or the Federal Data Protection and Information Commissioner (FDPIC) asks questions. Our FADP compliance audit for CRMs lists it as item no. 1; this article opens the document and reads it clause by clause.
Why does the data processing agreement matter as much as the CRM itself?
Because the FADP keeps you responsible for the data you entrust to others. Art. 9 FADP allows processing to be delegated by contract, provided the vendor only does what you would be entitled to do yourself and guarantees data security. A technically flawless CRM with a vague contract remains a risk.
Art. 9 of the Federal Act on Data Protection adds that no statutory or contractual duty of confidentiality may stand in the way, and that the processor may only delegate in turn with your prior authorisation. The stakes are personal: Art. 61(b) FADP provides, on complaint, for a fine of up to CHF 250,000 for any private individual who intentionally delegates processing without these conditions being met. See what the FADP requires of company directors. For fiduciary firms and medical practices, professional secrecy may limit what you are allowed to delegate.
Which 9 clauses should you check in an FADP data processing agreement?
Purposes, instructions, location, security, sub-processors, transfers, breach notification, assistance with data subject rights, and return and deletion. Each one ties back to an article of the FADP or of the Data Protection Ordinance (DPO), and each can be checked in a few minutes in your vendor’s DPA.
- 1
Subject matter, purposes and data categories
5 minThe contract describes the data processed and a specific purpose: providing the CRM service. Wording such as “improving our services” opens the door to uses you could not justify yourself (Art. 9(1)(a) FADP).
- 2
Processing on your instructions only
5 minThe vendor processes your data only on your instructions. Look for any reservation allowing it to reuse the data for its own purposes (marketing, model training) and require that it be excluded or limited to anonymised data.
- 3
Hosting and access locations
5 minThe hosting country and the countries from which support staff access the data are named. Every foreign country will have to appear in your privacy notice (Art. 19(4) FADP).
- 4
Security measures in an annex
6 minAn annex describes encryption, access control, logging and backups, mapped against the objectives and measures in Arts. 2 and 3 DPO. Check how the vendor proves it: certification, audit report or right of inspection.
- 5
Sub-processors
6 minAn accessible list with each role and country, advance notice before any addition, a right to object and a way out if you disagree: this is the contractual form of the prior authorisation required by Art. 9(3) FADP.
- 6
A safeguard for every transfer outside Switzerland
5 minFor each country, the contract names the basis under Art. 16 FADP: adequacy, Swiss-US DPF certification or standard clauses recognised by the FDPIC. A DPA written for the GDPR must refer to Switzerland explicitly.
- 7
Notification of security breaches
4 minArt. 24(3) FADP requires the processor to notify you of any breach as soon as possible. Look for a stated deadline and the content of the notification, which you will need to decide whether to alert the FDPIC.
- 8
Assistance with data subject rights
4 minWhen someone requests access, you are the one who answers (Art. 25 FADP); the vendor undertakes to help you extract, correct or delete the data concerned.
- 9
Return and deletion at the end of the contract
5 minExport format, retrieval window, then a deletion deadline that includes backups. Without a written deadline, you cannot demonstrate destruction in line with Art. 6(4) FADP.
How should you read the list of sub-processors?
Line by line, with four questions: what role, which country, what safeguard, and can you refuse a newcomer? The hosting provider is only one line: email delivery, support or AI often add further countries.
Pipedrive’s DPA, updated on 2 July 2026, illustrates a common mechanism: a new sub-processor is announced by email to administrators, there are 10 calendar days to object, and the affected services may then be terminated if no agreement is reached within 30 days. This right only works if someone reads those emails: an administrator account in the name of a former employee makes it purely theoretical.
| List column | What it should state | Warning sign |
|---|---|---|
| Provider | Exact company name | Generic category (“cloud providers”) |
| Role | Hosting, email, support, AI | Role missing or too broad |
| Country | Place of processing and access | “Worldwide” with no detail |
| Safeguard | Adequacy, DPF or standard clauses | No basis stated |
Which safeguard must the contract name for transfers outside Switzerland?
A specific safeguard for each destination country. For the EU, the Federal Council’s adequacy list is enough. For the United States, you need either a recipient certified under the Swiss-US DPF or standard clauses recognised by the FDPIC. The contract must say so, because you have to carry this over into your privacy notice.
Annex 1 to the DPO lists the countries deemed adequate, including all EU member states. Since 15 September 2024, the Federal Council has added US companies certified under the Swiss-US Data Privacy Framework, with no further safeguard required. For other cases, the FDPIC recognises the EU standard contractual clauses, adapted to Swiss law, and using them no longer requires notification. Technical measures may be added if the recipient’s legal system allows disproportionate access by the authorities.
Pipedrive’s DPA provides for processing that may take place “globally”, names Pipedrive, Inc. as the recipient in the United States and relies on the EU standard clauses for Switzerland. HubSpot lists no data centre in Switzerland: the EU, Canada, Australia and two US regions. Access by US authorities (CLOUD Act), still debated among lawyers, is covered in our comparison of hosting in Switzerland or in Europe.
What should the export and deletion clause provide at the end of the contract?
A complete export in a reusable format, a retrieval window with a stated length after termination, and a deadline for permanent deletion, backups included. Without these dates, you do not know when to retrieve your customer file or when it disappears from the vendor’s systems.
Pipedrive’s DPA gives an example of a clause with figures: closed accounts deleted within 180 days, archive backups kept for 90 days. What matters is that the deadline is written down and compatible with Art. 6(4) FADP: destroy or anonymise data as soon as it is no longer needed. Test the export before signing, attachments and custom fields included; it is one of the criteria for choosing a CRM for a Swiss SME.
FAQ: FADP data processing agreements and CRMs
Is the DPA accepted online at sign-up enough as a data processing agreement?
Yes, if it contains the necessary commitments: Art. 9 FADP requires a contract, not a handwritten signature. Keep the accepted version and its date.
Is a DPA drafted for the GDPR valid under the FADP?
It often covers the essentials, but it must refer explicitly to Swiss law and to the FDPIC for transfers. If Switzerland is not mentioned, ask for an addendum.
What should I do if the vendor adds a sub-processor in a country that is a problem for me?
Exercise your right to object within the stated period. Failing that, the prior authorisation required by Art. 9(3) FADP remains your argument, and the termination clause your way out.
Do I have to mention my CRM’s sub-processors in my privacy notice?
Yes, at least by category of recipient (Art. 19(2) FADP). Each foreign destination country must also be named, together with the safeguard relied on (Art. 19(4) FADP).
Who answers a customer asking for access to their data stored in the CRM?
You do. Under Art. 25 FADP, the controller who uses a processor remains responsible for providing the information.
A readable contract is a selling point
The contract engages your liability as much as the tool does; the sub-processor list shows where your data really goes; a termination clause without a stated deadline is a gap in your compliance. For the terminology, see our FADP glossary for SMEs; in the event of an incident, follow the steps for reporting a data breach to the FDPIC.
A clear DPA, data in Switzerland and a short list of sub-processors: an SME that can show this answers its clients’ questionnaires in a single page. Helvee is a CRM hosted in Switzerland and designed for the FADP. To see where Helvee hosts your data and which sub-processors it uses, contact us.
