Launching soonNow testing with a small group of Irish businesses

EzyReviews

Data processing terms

When EzyReviews handles personal data about a business's own customers, the business decides why and how that data is used (it's the controller) and we handle it only for the business (we're its processor). Article 28 of the GDPR says that needs a written contract with these terms. They form part of our terms and conditions, which a business accepts when it signs up, and apply for as long as we process the data. Where they differ from the rest of the terms on data protection, these terms apply.

"You" means the business; "we" and "us" mean EzyReviews, run by Hamad Hafeez in Ireland (contact@ezyreviews.ie). Words like personal data, processing, controller, processor, sub-processor and personal data breach mean what they mean in the GDPR.

1. What we process for you

2. Your instructions

We process the data only on your documented instructions: these terms, and what you choose in your dashboard and settings. That includes any transfer outside the European Economic Area (section 5). If the law requires us to process it in another way, we'll tell you first, unless the law forbids that. If we think an instruction breaks data protection law, we'll tell you straight away.

We never sell your customers' data, use it to market to them for ourselves, or combine it with another business's data. The one exception is the "do not email" list: when someone unsubscribes from every business using EzyReviews, we keep a scrambled (hashed) form of their address and honour it for every business, because they asked us to.

3. People who handle the data

Only people who need to, to run, support and fix the service, can see your customers' data, and each is bound to keep it confidential.

4. Security

We keep appropriate technical and organisational measures (Article 32), including: encryption in transit and at rest; each business able to see only its own data, enforced in the database; server-only records (such as access tokens and customers' contact details waiting to be sent) that can't be read from any browser; scrambled (hashed) forms instead of raw IP and email addresses where we only need to recognise something again; roles that limit what each of your team members can see; and an activity log of what's done in your dashboard. We review these measures as the service changes.

5. Sub-processors

You authorise us to use these sub-processors for your data:

We'll tell you by email at least 30 days before we add or replace a sub-processor. If you object on reasonable data protection grounds, tell us; if we can't resolve it, you can cancel before the change takes effect. Each sub-processor is bound by a written contract with data protection obligations at least as protective as these. We remain responsible to you for what our sub-processors do. Where data goes outside the European Economic Area, it's protected by the European Commission's Standard Contractual Clauses or the EU–U.S. Data Privacy Framework, as applies to each sub-processor.

Some services you connect yourself are not our sub-processors: they're your own providers. These include Google (your Business Profile), WordPress, Zapier, Make, and your booking or CRM system.

6. Helping you with people's rights

Your dashboard lets owners and admins download everything, and find or erase one customer's details (Reports › Data and privacy). If someone asks us directly about data we process for you, we'll pass the request to you without undue delay and won't answer it ourselves unless you ask us to. We'll help you, as far as we reasonably can, to answer requests to see, correct, delete, restrict or move data, and objections.

7. Breaches, and your other duties

If we become aware of a personal data breach affecting your data, we'll tell you without undue delay, and in any case within 48 hours, with what we know: what happened, the data and people likely to be affected, the likely consequences, and what we're doing about it. We'll add more as we learn it. We'll also help you, as far as the information available to us allows, with your security duties, notifying the Data Protection Commission and the people affected, data protection impact assessments and any consultation with the Commission (Articles 32 to 36).

8. When you leave

Before you close your account, you can download your data from the dashboard. When you close it, we delete your data 30 days later (you can cancel that until then). If your subscription ends without closing the account, we delete it within 12 months, as our privacy policy explains. Sub-processors' backups are overwritten on their normal cycle. We only keep what the law requires us to keep (billing records), and never customers' data.

9. Showing that we comply

We'll give you the information you reasonably need to show that we meet Article 28, and answer your reasonable questions about how we process your data. If that isn't enough, you or an auditor you choose (bound to confidentiality) may inspect our compliance, with at least 30 days' notice, no more than once a year unless there's been a breach or a regulator requires it, at your cost.

10. Your part

11. Liability and changes

Each of us is responsible for our own compliance with data protection law. Between you and us, liability under these terms is as set out in the terms; nothing limits either of our responsibilities to the people whose data it is. We may update these terms to keep up with the law or the service, and will tell you about significant changes in advance, as the terms explain. Irish law governs these terms, as it does the rest of the terms.