GDPR FAQ
Straight answers to the questions stores actually ask about GDPR and reviews — roles, consent, transfers and deletion.
Review before publishing. This is guidance written for the product, not legal advice. Controller/processor analysis and consent requirements vary by country and by how you use the data — have counsel confirm your position before relying on it.
Last updated 19 November 2026
Does GDPR apply to my store?
- I am outside the EU. Does this affect me?
- If you sell to customers in the EU or UK, yes — GDPR (and the UK GDPR) applies based on where the customer is, not where you are. Most stores that ship internationally are in scope.
- What about my customers' reviews?
- A review contains personal data: a name, sometimes a photo, an order reference. That means it is in scope like any other customer record.
Who is the controller?
- Are you the controller or the processor?
- For your customers' data, you are the controller and Ratingsly is the processor. You decide why reviews are collected; we handle the mechanics on your documented instructions. For your own account and billing data, we are the controller.
- Why does the distinction matter?
- Because it decides who answers a customer's rights request. A shopper asking for their data approaches you first, as the controller, and you instruct us as processor.
The Data Processing Agreement
- Do you offer a DPA?
- Yes. It is available to every customer, including on the free trial, and it incorporates the Standard Contractual Clauses where a transfer outside the EEA is involved. Ask support and we will send it for signature.
- Do you have sub-processors?
- Yes — hosting, database, email delivery, messaging and payments. The current list is in the DPA and we notify customers before adding a new one that processes personal data.
Where is data stored?
- Which region?
- Primary application and database hosting is in the European Union. Backups are encrypted and stored in the same region.
- Is anything transferred outside the EU?
- Some supporting services, such as email delivery and payment processing, operate from the United States. Those transfers are covered by Standard Contractual Clauses with additional technical safeguards.
Handling customer requests
- A customer asks to see or delete their data. What do I do?
- You have 30 days to respond as controller. In Ratingsly you can search by email or order ID, export everything held about that person, and delete it. Deletion removes the review and any associated personal data, and is logged.
- Can I delete a review without deleting the order record?
- Yes. Deletion of the review removes the review content and the reviewer's personal data; the order reference is retained only in anonymised form for accounting integrity.
- What if the customer only wants their name removed?
- You can anonymise a review — the content stays, the identifying fields are stripped. That is often the right answer for a review that is otherwise useful to other shoppers.
Consent for email, SMS and WhatsApp
- Do I need consent to email a review request?
- Under GDPR you need a lawful basis, not necessarily consent. For existing customers, legitimate interest is usually the basis, provided the request is about something they bought and you offer an easy opt-out. Check your local ePrivacy rules too, which are stricter in some countries.
- What about SMS and WhatsApp?
- Consent is required. Ratingsly records opt-in at checkout and honours stop requests immediately. Sending without consent is what gets business numbers banned, and it is a GDPR problem as well.
- How is consent recorded?
- With a timestamp, the channel, and the text the customer agreed to. It is exportable if a regulator asks.
Retention
- How long do you keep review data?
- For as long as your account is active, because reviews form part of your public product pages. If you close your account, you have 30 days to export, after which data is deleted.
- And order data used for scheduling?
- Deleted or anonymised 24 months after the request is sent. We do not need the order once the request has gone out.
Breach notification
- What happens if there is a breach?
- We notify affected controllers without undue delay and give you the information you need to meet your own 72-hour obligation to your supervisory authority. We do not wait until the investigation is complete to tell you something happened.
Contact
- Who do I ask about GDPR?
- Email hello@ratingsly.com with 'GDPR' in the subject. Privacy requests are answered within 30 days; general questions usually within two working days.
Questions about this page? Email hello@ratingsly.com. We answer policy questions properly rather than with a template.