1.Australian businesses that have an establishment in the EUâ€¨
2.Australian businesses that sell goods and services in the EU; andâ€¨
3.Australian businesses that monitor behaviour of individuals in the EU.â€¨
If your business sells software you might fall under all three of these business categories.
However, it is only important to consider the GDPR in regards to any personal data your business might manage. The GDPR makes clear that a wide range of identifiers can be classified as â€˜personal dataâ€™, including a name, an identification number, location data, an online identifier or one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.
If you have realised that you might be liable under the GDPR then there are a few steps you should take as soon as possible. The GDPR has a lot in common with Australiaâ€™s Privacy Act, so hopefully your business already complies with most of Europeâ€™s regulation. However, WorkingMouse has noted three main differences between the laws that we have raised with our clients who have overseas customers. All businesses with software that is available to clients in Europe should ensure compliance with the following (in addition to Australiaâ€™s Privacy Act compliance):
Article 6 of the GDPR tells us that one of the conditions for the lawfulness of processing personal data is consent. This is defined in Article 4 as:
â€œany freely given, specific, informed and unambiguous indication of the data subjectâ€™s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or herâ€.
The UKâ€™s Information Commissioner's Office further clarified what changes some of the terms in this definition will require for compliance. For example, â€œclear affirmative actionâ€ means that pre-ticked opt-in boxes for data collection will no longer be satisfactory. Consent requests must also: Basically, while your website probably already has consent requests, they are likely less explicit or as obvious as required by the GDPR. Looking at solutions such as two-step verification can help demonstrate your businessâ€™ compliance with the regulation.
Basically, while your website probably already has consent requests, they are likely less explicit or as obvious as required by the GDPR. Looking at solutions such as two-step verification can help demonstrate your businessâ€™ compliance with the regulation.
The entire regulation offers some serious restrictions for data controllers and affords heavy protection to individuals (data subjects). Perhaps one of the strongest protections is the data subjectâ€™s right to erasure (also known as the â€˜right to be forgottenâ€™). Article 17 of the GDPR affords the individual the right to data erasure without undue delay at their verbal or written request.
This means that if as a controller of data you are requested to erase an individuals data, and you have disclosed the personal data to others (a third party), you must contact each recipient and inform them of the erasure, unless this proves impossible or involves disproportionate effort. If asked to, you must also inform the individuals about these recipients.
Applying this principle to an online environment where personal data has been made public can be challenging due to the vastness of the internet. For these circumstances the regulation requires that reasonable steps should be taken to inform other controllers who are processing the personal data to erase links to copies or replication of that data. To determine what steps are reasonable you should take into account available technology and the cost of implementation.
In some circumstances a request for data erasure could be seen as manifestly unfounded or excessive. In these circumstances you might be able to request a â€œreasonable feeâ€ to deal with the request or refuse to deal with it, if you can justify this decision. However, considering the focus on individual protection in these regulations, it is better to be more cautious and design your software to be able to erase data if requested.
Another significant difference to note between the Australian Privacy Act and the GDPR is Article 12, which grants an individual the right to data portability. This right is an extremely new idea and requires a controller to provide the individual with a copy of their personal data in a structured, commonly used and machine-readable format so that the individual may transmit the data to a different controller, or provide another controller direct access to transfer the data to their server.
Examples of structured, commonly used and machine-readable formats that are suitable for data portability under the regulation include CSV, XML and JSON. However, this does not mean you are obliged to use them. Other formats exist that also meet the requirements of data portability.
Providing data portability on your software platform may be quite complex to achieve. There are therefore some limits to transmitting data to another controller. For example, this right does not create an obligation for you to adopt or maintain processing systems which are technically compatible with those of other organisations.
All the big companies from Spotify to Instagram have had to implement ways for you to download a complete collection of your data on their platform, including a complete history of what photos you have liked and exactly which songs you have listened to.
The GDPR is now in full effect. Online business, even those based in Australia, should ensure they are prepared to deal with any requests or concerns raised by individuals interacting with their online presence from within Europe. Though some Australian businesses may not yet, or ever, feel the impact from this new legislation, it is important that businesses who currently or in the future plan to have an establishment in the EU, sell goods or services in the EU or collect data from the EU, begin to consider some of the significant changes to data collection from this regulation.