Customer supportLiveAgent and the GDPR: agreement, role and data location.
LiveAgent is a customer support 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
- Customer support
- Usual role
- Usually a processor
- Data location
- Often EU (Germany/Ireland), US or Singapore, chosen at sign-up, check your account
- Agreement
- Obtained through the vendor
What does LiveAgent do with personal data?
Respond to customer enquiries and manage support conversations. That is how Privacyboard describes a typical use of LiveAgent, as a starting point you can edit.
The data usually involved: names, email addresses, account identifiers, messages and attachments provided to support.
Is LiveAgent a processor or a controller?
Most customers use LiveAgent as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for customer support 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 LiveAgent store personal data?
LiveAgent is usually associated with EU (Germany/Ireland), US or Singapore, chosen at sign-up, 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 LiveAgent says (read on 2026-11-05): Account region chosen at sign-up; “its data stays in that region” Source: https://www.liveagent.com/gdpr/subprocessors
How to find yours: Check workspace settings → data and privacy, or the provider’s documentation.
If the data is processed outside the European Economic Area, Articles 44 to 49 require a transfer mechanism, such as standard contractual clauses, an adequacy decision or the EU-US Data Privacy Framework. Your privacy policy should name it.
Which legal basis usually applies to LiveAgent?
For the usual use of LiveAgent, companies most often rely on performance of a contract (GDPR Article 6(1)). The tool is needed to deliver what the person signed up for or asked for.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Does LiveAgent have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
LiveAgent 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: GDPR page offers regional DPA templates (EU, US, Asia) to download, sign and email back for countersignature. Processor Quality Unit, s.r.o. (Slovakia), Slovak law. Data hosted on AWS in the region chosen at sign-up; SCCs with sub-processors outside the EEA.
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 LiveAgent reference pageHow to declare LiveAgent
- 1
In your privacy policy
Name LiveAgent as a recipient, say what it is used for (respond to customer enquiries and manage support conversations) 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 LiveAgent 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 LiveAgent 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 LiveAgent
- Set a retention period for closed conversations and attachments.
- Check how you would find and delete one person’s conversations when they ask.
- Review which team members and integrations can read the data.
- Record where the data is stored and any transfers 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 LiveAgent GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how LiveAgent 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 LiveAgent have a DPA?
LiveAgent 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.liveagent.com/gdpr.
Is LiveAgent a data processor?
Usually, yes. Most customers use LiveAgent 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 LiveAgent?
For the usual use of LiveAgent, companies most often rely on performance of a contract (GDPR Article 6(1)). The tool is needed to deliver what the person signed up for or asked for. This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Where does LiveAgent store data?
LiveAgent is usually associated with EU (Germany/Ireland), US or Singapore, chosen at sign-up, 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 LiveAgent says (read on 2026-11-05): Account region chosen at sign-up; “its data stays in that region” Source: https://www.liveagent.com/gdpr/subprocessors
Do I need to mention LiveAgent in my privacy policy?
Yes, if LiveAgent 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 LiveAgent to my vendor list?
In Privacyboard, pick LiveAgent 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 customer support tools
Privacyboard is not affiliated with LiveAgent. 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.