CRMSellsy and the GDPR: agreement, role and data location.
Sellsy is a crm tool. Most customers use it as a processor, it publishes its data processing agreement, and it usually keeps data in France. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- CRM
- Usual role
- Usually a processor
- Data location
- Usually France
- Agreement
- Published by the vendor
What does Sellsy do with personal data?
Manage prospect and customer relationships and sales activities. That is how Privacyboard describes a typical use of Sellsy, as a starting point you can edit.
The data usually involved: business contact names, email addresses, company details and sales communications.
Is Sellsy a processor or a controller?
Most customers use Sellsy as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for crm 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 Sellsy store personal data?
Sellsy usually keeps data in France for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs.
What Sellsy says (read on 2026-11-05): “Les Données à Caractère Personnel des Utilisateurs sont hébergées en France.” Source: https://go.sellsy.com/informations-legales/conditions-generales
How to find yours: Check account settings → data hosting, or the provider’s documentation.
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 Sellsy?
For the usual use of Sellsy, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). Customer records support the contract; following up business contacts is a common legitimate interest.
The interest you would state: “Managing our relationships with customers and with business contacts who may be interested in our services.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Cold messages to individuals (not professionals) need consent. The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Sources: CNIL: rules for prospecting by email, EDPB Guidelines 1/2024 on legitimate interest
Does Sellsy have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. Sellsy publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep.
What we noted when we opened the page: Article XII of the Sellsy CGV (in force 2 May 2025) sets processor terms under GDPR Article 28. Contracting entity SELLSY SAS, La Rochelle. Says personal data is hosted in France; some sub-processors outside the EU, with Article 45/46 safeguards.
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.
Read the Sellsy agreementHow to declare Sellsy
- 1
In your privacy policy
Name Sellsy as a recipient, say what it is used for (manage prospect and customer relationships and sales activities) 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 Sellsy 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 Sellsy 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 Sellsy
- Define a retention period for inactive leads and contacts.
- Make sure you can find, export and delete one contact across the CRM.
- Record the legal basis for outreach, and respect objections to marketing.
- Record the region and any transfer outside the EEA.
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 Sellsy GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Sellsy is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it publishes a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Sellsy have a DPA?
Yes. Sellsy publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep. You can read it at https://go.sellsy.com/informations-legales/conditions-generales.
Is Sellsy a data processor?
Usually, yes. Most customers use Sellsy 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 Sellsy?
For the usual use of Sellsy, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). Customer records support the contract; following up business contacts is a common legitimate interest. The interest you would state: “Managing our relationships with customers and with business contacts who may be interested in our services.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does Sellsy store data?
Sellsy usually keeps data in France for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs. What Sellsy says (read on 2026-11-05): “Les Données à Caractère Personnel des Utilisateurs sont hébergées en France.” Source: https://go.sellsy.com/informations-legales/conditions-generales
Do I need to mention Sellsy in my privacy policy?
Yes, if Sellsy 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 Sellsy to my vendor list?
In Privacyboard, pick Sellsy 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
Privacyboard is not affiliated with Sellsy. 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.