Posts

Very interesting indeed, how about using the U.S. marine's system for communication, i.e. the SBAR approach.

It's quite popular and has even been taken up by the NHS staff. Per the method, your communication should be composed of four paragraphs:

1. Situation (what's happening)

2. Background (basic information about the issue)

3. Assessment (what do you think is going to happen or how the issue will unfold)

4. Recommendation (what you require the other party to do)

Thoughts? 

DMOZ 8th February 2017 11:33 PM

I'm not the SEO expert, but I think Google is way smarter than that at the moment!

Same with me what sort of things will I need to setup or what else do I need to implement

thanks”

 
Simply follow the guidelines set out in the document, and you should be fine. You may want to have a chat with your webmaster/developer to check that you are able to execute these functions within your code (e.g. to delete user's data from all your services and databases without having to disassemble your entire system) and that you have someone who could professionally review your data protection security.
 
 
The DPO doesn't have to be an employee: you can simply outsource it as you may do with webdevelopment, server hosting, marketing, etc.

 

So if you already have a data controller number and nominated bod, then all is OK? Or is there anything above and beyond the normal data protection  requirements we need to implement?”
 

Depends on what you mean by "normal data protection". If it complies with reasonable security standards and anyone can request to be erased from all your services + you declare exactly what you will do with users' data and consent them for it (I'm just saying things most people probably aren't doing at the moment) then there is nothing more you need to do.

The whole purpose of this regulation is to end the culture of reckless datahandling, e.g. keeping your customers in an Excel spreadsheet or laundering data through endless algorithms, data aggregators, etc. 

why does this effect us as we are not part of the EU ,or are in the process of leaving , is it because we still in that it concerns us ...thanks”
 

1. It will become law May next year, regardless of the current negotiating process. Unless, of course, there will be a different international agreement to say otherwise. Until a formal withdrawal, we are part of the EU. The Government is yet to initiate the process of negotiating the withdrawal which is only the beginning of that road.

2. If you want to deal with any companies operating in the European Economic Area (perhaps we'll still be part of that after leaving the EU), the rules will still be binding + you yourself may use services of some companies registered in, e.g. Luxemburg (even if you don't know about it! )  

 

Hope that helps!

The new General Data Protection Regulation (GDPR) is a piece of legislation that will seriously affect every organisation in different ways, yet more than half of European companies are not aware of the new Regulation coming into force in May 2018.

The GDPR is a Regulation aiming to strengthen, standardise and unify the rules concerning data protection and data processing. The Regulation will be directly applicable throughout the EU from 25 May 2018, without requiring implementation by the EU Member States through national law. The Regulation aims to:

harmonise the current legal framework, which is fragmented across Member States;return control over personal data back to the users; andintroduce new Data Protection Officers to supervise the storage and processing of personal data.

Most likely, yes. You may not be aware of that, but almost every modern app, website an online service involves personal data processing. This is why under current data protection laws everyone responsible for using data has to follow strict rules called ‘data protection principles’.

Come May 2018, this may not be good enough.

If you use personal data in any capacity — by storing it, transferring it, analysing it or even simply holding it to carry out an online transaction — you will be dealing with data processing.

What is the new Data Protection Officer (DPO) and do I need one?

The GDPR requires companies to nominate a data protection officer (“DPO”) under certain circumstances. Thus even a relatively small start-up may need to nominate a DPO if their core activities involve “regular and systematic monitoring of data subjects on a large scale” or consist of “processing on a large scale of special categories of data” (as per article 37 of the GDPR).

There is no legal requirement for a DPO to hold any official qualifications but they are expected to have reasonable knowledge and experience to fulfill their duties.

The DPO will need to ensure that the data is stored properly and that the business complies with the data protection rules and regulations.

The GDPR requires that companies give certain information to individuals about the processing of their personal data. Examples of this type of information include the identity of the company processing their data, and the contact details of the relevant DPO, where applicable.

In addition, customers will need to be informed of the legal basis for such processing. Individuals will have much greater say in determining how their data may be lawfully used, with active rights to change consent based processing and rights to object to processing based on “implied” rights (i.e. legitimate interests). You’ll have to allow for the consent to be withdrawn at any point, and the security and privacy settings to be set to the high level by default. Your users will also be able to request that all their data be erased from your databases and services.You will also have to tell your users about any data security breach, as well as inform the regulator about it.

The rules on transferring data to other organisations, or outside Europe are stringent and require the controller to take full responsibility for proper and secure handling supported by effective due diligence and contractual measures.

The changes introduced by the GDPR will ultimately require a substantial review of privacy policies and statements, which will include any contracts that you might have with sub-contractors who process personal data on your behalf (such as cloud service providers).

Start documenting your data processing practices. Start defining the categories of data, the purpose of the data and who has responsibility for the data.

Everything from a simple loyalty card app to a multi-layered customer profiling systems will have to closely trace what is happening with every piece of data.

Even if you are not obligated to nominate a DPO at present, it might still make sense to nominate a member of your staff internally as soon as possible, as doing so will help to focus implementation and drive accountability.

Start thinking about potential risk areas. The GDPR implements the so-called risk-based approach, which means that the greater the risks posed to the privacy rights of individuals, the more safeguards and transparency will be needed.

Now, many apps simply take the required user data and process it in a variety of different algorithms, putting chunks of data into a number of databases (e.g. for sales, user profiling, purchasing behavior, statistics or usage history).

All organisations will be expected to promote privacy and data protection compliance from the start when creating new products and services. Privacy impact assessments must be carried out as a matter of routine, especially when considering new arrangements that may involve handling sensitive data fields, or large volumes of personal data.

What if I’ve got any questions?

We’re here to help! The new Regulation will require major changes and substantial data protection review. It will affect almost all businesses in the UK and across Europe, with some global ramifications for international companies based here.

We understand that this may be a daunting process and that is why you should start preparing for the GDPR early.

Our team can assist you in preparing for the Regulation. We can carry out a privacy impact assessment for your organisation, help you develop effective organisational controls and governance structures and draft all the necessary data processing documentation required by the GDPR enabling you to achieve compliance with the GDPR.

Just unsubscribe me! 22nd December 2016 10:38 PM

I think they're just trying to reach out to you and convince you to stay... However, I don't quite think it's the best method to do that; clearly didn't work in your case!

Tipping Postman, Bin Men, etc 28th November 2016 11:46 PM

I think getting him a modest gift, e.g. a card / chocolates / something nice wouldn't hurt your budget and it will go a long way as a nice gesture! 

Vacancy in the NHS IT department 19th November 2016 3:13 PM

I imagine the campaign "Ban reply to all option" would gain some traction

Copywrite Question 12th June 2016 12:15 AM

Your blog is commercial if you use it for commercial purposes, i.e. to charge fees, sell products/services, advertise for a commission, etc. If the post is for informative purposes only, i.e. you won't be profiting from it directly, then it should not be considered "commercial".

 

Also, please note that by writing about something (i.e. you use your own words, the post is yours, you're just describing the thing), you would not infringe their copyright, as this will just be your work. 

You can't, however, copy-paste their content and change it.

A useful rule of thumb is to read the text first, as an inspiration, do your reading/research etc. and then proceed to writing your posts from scratch. This way, starting from a blank page, you will be sure that the work is yours.

 

I hope that helps!