Clinic Management software that makes booking and rebooking multiple appointments simple and pain free.
The GDPR is the European Union’s, comprehensive privacy and data protection law that took effect on May 25, 2018. The primary aim of the GDPR is to regulate how the personal data of individuals in the EU is processed – even by businesses that have no physical or legal presence in the EU. Organizations can face hefty fines for non-compliance: up to €20 million or 4 percent of annual global revenue, whichever is higher.
There is not yet any kind of recognized GDPR certification scheme, but we’ve been working hard to ensure that we’re in compliance with the GDPR.
The new DPA governs the terms by which we, as a data processor, process data on behalf of you, our customers, (who are typically data controllers) in accordance with Article 28 of the GDPR.
According to Article 28 of the GDPR, data processors must act only upon the documented instructions of the data controller unless otherwise required by law. This, however, does not relieve us of any of our obligations or liabilities under the GDPR. We are still required to ensure that we’re in compliance with the GDPR.
We’ll continue to review our security measures, as we always do, to stay at the forefront of evolving industry standards and best practices.
No, while we’ve done our best to make it easier for you to be compliant, you’ll still need to address your own practices regarding GDPR compliance.
Much of how you collect, use, and dispose of personal data is not determined by your data processor (that’s us). Thus, each organization should get its own professional guidance on the topic to help ensure compliance. Here’s an additional resource from the UK Information Commissioner’s Office: https://ico.org.uk/for-organisations/resources-and-support/data-protection-self-assessment/getting-ready-for-the-gdpr/.
Typically, you (the Pabau customer) will be considered a data controller (i.e., an organization that determines the purposes and means of the processing of personal data) and we will always be considered a data processor under the law.
Controllers and processors each have their own respective obligations under the law. When a data controller engages a service provider like us, the service provider is typically a data processor acting on behalf of the controller, and the processor acts at the behest of the controller. As stated above, our DPA will govern the relationship, and the nature of the processing activities, between Pabau and its customers.
According to GDPR Article 4, personal data means…“any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.”
So, what does that mean for you?
Within your Pabau account, that would include your customers’ contact information. And they may at some point ask you to forget them, or modify their information to be accurate, etc. You would then be responsible for fulfilling that request.
If you are processing personal data on the basis of the data subject’s consent, you will need to include a mechanism to collect that consent, which could include an unticked checkbox which the data subject can tick to consent to the processing of his or her data. If you can consider this type of arrangement as a “contract” between you and the individual who requested the “something,” then you may be able to skip the checkbox altogether, and base your processing on the need to perform your obligations under this “contract”.
Yes. Article 17 of the GDPR sets out the data subject’s right to have his or her data erased (also known as the “right to be forgotten”) when certain (broad) grounds apply, such as (without limitation) when the personal data are no longer necessary for the purposes of processing, where consent, as the sole basis of processing, has been withdrawn, or where the data subject has objected to the processing of his or her personal data and you have no “compelling legitimate grounds” to continue the processing. It’s important to note how broadly this right applies: in practice, there will be few circumstances where the GDPR will not require the deletion of data at the data subject’s request.
No, please note that the use of pre-ticked opt-in boxes is not valid under the GDPR. Silence or inactivity on the part of the data subject, as well as merely using a service (without first ticking a box to indicate agreement) doesn’t count as “consent”.
Book a demo
Leave your details and a member of our team will be in touch shortly. Signing up to a demo allows you full access to learn about our software and the features that are key to business growth.