Reviews & loyaltyREVIEWS.io and the GDPR: agreement, role and data location.
REVIEWS.io is a reviews & loyalty tool. Its role depends on the activity, it publishes 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
- Reviews & loyalty
- Usual role
- Depends on the activity
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does REVIEWS.io do with personal data?
Collect customer reviews, run loyalty, referral or affiliate programs and send related messages. That is how Privacyboard describes a typical use of REVIEWS.io, as a starting point you can edit.
The data usually involved: customer names, email addresses, order details, reviews, points or rewards, referral and engagement data.
Is REVIEWS.io a processor or a controller?
REVIEWS.io acts as controller for data it processes under its own privacy policy, such as published reviews.
Privacyboard does not prefill a role for this vendor on purpose. You are asked to choose, since the answer changes what your privacy policy says and which agreement matters.
Where does REVIEWS.io store personal data?
REVIEWS.io does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
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 REVIEWS.io?
For the usual use of REVIEWS.io, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). A loyalty program the customer joined is a contract; a review request after a purchase usually rests on a legitimate interest.
The interest you would state: “Asking customers for a review of their purchase and rewarding loyal customers.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Publishing a review with the author’s name needs their agreement, and review requests must be easy to refuse. 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: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest
Does REVIEWS.io have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. REVIEWS.io publishes the text of its data processing agreement as a PDF 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: EU GDPR Data Processing Addendum v1.1 (February 2019), signed by Reviews.io. Customer is controller, Reviews.io processor except data under its own privacy policy. No hosting location named; non-EEA transfers under EU SCCs.
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 REVIEWS.io agreementHow to declare REVIEWS.io
- 1
In your privacy policy
Name REVIEWS.io as a recipient, say what it is used for (collect customer reviews, run loyalty, referral or affiliate programs and send related messages) 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 REVIEWS.io 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 REVIEWS.io 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 REVIEWS.io
- Check which emails the tool sends and that each one offers an easy way to stop them.
- Decide how reviews are published: first name only, initials, or full name with agreement.
- Check how long points, reviews and referral data are kept.
- 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 REVIEWS.io GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how REVIEWS.io 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 REVIEWS.io have a DPA?
Yes. REVIEWS.io publishes the text of its data processing agreement as a PDF 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://dash.reviews.io/pdf/Reviews.io_DPA.pdf.
Is REVIEWS.io a data processor?
It depends on the activity. REVIEWS.io acts as controller for data it processes under its own privacy policy, such as published reviews.
Which legal basis applies when I use REVIEWS.io?
For the usual use of REVIEWS.io, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). A loyalty program the customer joined is a contract; a review request after a purchase usually rests on a legitimate interest. The interest you would state: “Asking customers for a review of their purchase and rewarding loyal customers.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does REVIEWS.io store data?
REVIEWS.io does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. 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.
Do I need to mention REVIEWS.io in my privacy policy?
Yes, if REVIEWS.io 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 REVIEWS.io to my vendor list?
In Privacyboard, pick REVIEWS.io 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 reviews & loyalty tools
Privacyboard is not affiliated with REVIEWS.io. 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.