HR & payrollSympa and the GDPR: agreement, role and data location.
Sympa is a hr & payroll tool. Most customers use it as a processor, it explains how to get its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- HR & payroll
- Usual role
- Usually a processor
- Data location
- Often European Union (Netherlands and Ireland), check your account
- Agreement
- Obtained through the vendor
What does Sympa do with personal data?
Manage employee records, payroll, time off and other HR processes. That is how Privacyboard describes a typical use of Sympa, as a starting point you can edit.
The data usually involved: employee names, contact details, contract and payroll data, bank details, absences and other HR records.
Is Sympa a processor or a controller?
Most customers use Sympa as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for hr & payroll tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Sympa store personal data?
Sympa is usually associated with European Union (Netherlands and Ireland), but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account.
What Sympa says (read on 2026-11-05): “Customer personal data is stored in EU data centers.” Source: https://www.sympa.com/about/trust-centre/data-protection/
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Which legal basis usually applies to Sympa?
For the usual use of Sympa, companies most often rely on performance of a contract and legal obligation (GDPR Article 6(1)). Employment contracts, payroll and the records employers must keep (tax, social security, working time) rest on the contract and on employment law.
Health data such as sick notes is sensitive: limit who can see it and rely on an employment-law condition of Article 9.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Does Sympa have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Sympa does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.
What we noted when we opened the page: Sympa Trust Centre page says customer data processing is governed by the DPA Sympa has in place with each customer; no public DPA text. Says customer data is stored in EU data centres on Azure in the Netherlands and Ireland.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Open the Sympa reference pageHow to declare Sympa
- 1
In your privacy policy
Name Sympa as a recipient, say what it is used for (manage employee records, payroll, time off and other HR processes) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Sympa with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Sympa to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Sympa
- Limit access to HR and managers who need it, and review it when someone leaves.
- Set retention periods per record type: payroll and contracts often have legal minimums, candidates and former staff do not keep forever.
- Check where the data is hosted and any transfer outside the EEA.
- Tell employees which tool holds their data in your staff privacy notice.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is Sympa GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Sympa is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Sympa have a DPA?
Sympa does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://www.sympa.com/about/trust-centre/data-protection/.
Is Sympa a data processor?
Usually, yes. Most customers use Sympa as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Which legal basis applies when I use Sympa?
For the usual use of Sympa, companies most often rely on performance of a contract and legal obligation (GDPR Article 6(1)). Employment contracts, payroll and the records employers must keep (tax, social security, working time) rest on the contract and on employment law. Health data such as sick notes is sensitive: limit who can see it and rely on an employment-law condition of Article 9.
Where does Sympa store data?
Sympa is usually associated with European Union (Netherlands and Ireland), but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account. What Sympa says (read on 2026-11-05): “Customer personal data is stored in EU data centers.” Source: https://www.sympa.com/about/trust-centre/data-protection/
Do I need to mention Sympa in my privacy policy?
Yes, if Sympa handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Sympa to my vendor list?
In Privacyboard, pick Sympa from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
Compare all hr & payroll tools
Privacyboard is not affiliated with Sympa. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.