Tag: data

GDPR Frequently Asked Questions for TeamKinetic

This document will continue to develop over time as we respond to more questions from our customer and users.  Please feel free to subscribe to stay up to date.

1. Do we need to get renewed consent from every volunteer and provider?

We will be asking all volunteers and providers to review their consent settings for communications and the sharing of their data with volunteer opportunities. You can see this email here 

Renewed consent and acceptance of the new EULA will be required when logging in.

We think the consent we have already obtained from volunteers and providers provides us sufficient cover under the ‘legitimate use’ to ensure we do not need to delete users accounts.

2. How long do you keep data after someone has unsubscribed or withdrawn consent?

Unsubscribed relates to email/SMS correspondence, and users are removed immediately from all mass communication and newsletter emails. They will still receive transactional emails specifically related to them and their volunteering. If a user withdraws consent or asks to be removed their volunteer data is immediately anonymised and their personal data is moved to a table only accessible by a system administrator. This moved data is stored for a further 7 days before being permanently removed. We do this to enable us to restore a volunteer profile deleted in error. Data in backups will disappear after our 30 day retention period. Data from backups is restorable but an hourly charge is levied.

3. What is your process if anyone exercises their right to be forgotten.

We will immediately start the removal process for any volunteer requesting to be forgotten or who asks to be removed. The data removal follows the same pattern as above in point 2.

4. How long would it take to delete their data entirely?

Volunteer data is made anonymous immediately. Personal data is immediately unavailable to volunteer administrators and providers. Data in backups will be removed after our 30 day retention period.

Data in backups is only accessible by our network administrators and not by any users at any level of our applications.

5. Do you have an archive of all the data we hold in the database?

All data is transactionally backed up daily and stored encrypted. Backups are maintained for 30 days.

6. Is the data anonymised at any point?

If a request for removal is received then volunteer data is immediately anonymised.

7. Is your data encrypted?

Password data is stored using a one-way hash using a randomised SALT with a length sufficient to prevent practical brute force or collision attacks.

All data at rest in backup or in transit is encrypted using a minimum 30 character length password.

8. Can the TeamKinetic privacy policy be found on the database by volunteers?

Yes. Our full terms and conditions and specifically our privacy policy can be found at https://teamkinetic.co.uk/vk/shared_includes/termsandconditions.htm#privacy.

9. When were your terms and conditions and privacy policy last updated?

Attached to this post are links to:

I have also included the new Schedule that I will be sending as an addendum to all customers to outline our responsibilities to you under GDPR.

10. Is the website hosted on UK based servers?

All our hosting servers are UK based.

11. Do you have an ICO certification number?

You can find our details at https://ico.org.uk/ESDWebPages/Entry/ZA036104

Registration number: ZA036104
Date registered: 14 January 2014
Registration expires: 13 January 2021
Data controller: TeamKinetic Ltd
Address:
Office 14 Parkway 2
Parkway Business Centre
Princess Road
Manchester
M14 7HR

12. Where do you explain to the volunteer that data is shared with other parties

Our email to all volunteers will reiterate that data is shared with providers and potentially external administrators where a volunteer opts to volunteer on an opportunity outside their application.

For all new volunteers, this consent is explicitly captured during the initial sign up process.

13. What fields can a provider see on a volunteer

Providers can see (but not edit);
Age
Contact phone number
Email address
Gender
Special requirements and disabilities (if the volunteer has chosen to share)
Criminal record check status
Unlocked custom registration fields

14. Can “Admin” users set some “Custom Fields” to be visible to “Providers” or not visible?

Our next release in June 2018 has enabled custom fields to be locked to admins only.

15. Can you make custom registration fields compulsory?

Yes, custom fields can be made compulsory.

16. How long do we store data on volunteer and providers?

TeamKinetic believe volunteering is a lifetime pursuit and as such see no reason to remove a volunteer profile on behalf of a volunteer due to inactivity.

We do believe it is important for a volunteer or provider to have the ability to remove themselves as and when they see fit

We appreciate that some organisations will not share our view, so we will provide a tool that will allow Admin users to search the database for inactive users based on Admin set criteria of time. This will provide a list of inactive volunteers the admin user will be able to remove from the system on mass.

17. Is there any further information of TeamKinetic and GDPR

You can read my last blog on this subject at https://teamkinetic.co.uk/blog/tag/gdpr/

And you can download our whitepaper on this subject at https://teamkinetic.co.uk/vk/shared_includes/are-you-ready-for-gdpr.pdf

18. Do we maintain Data Processing Records

Yes. We have a record of all Data Processors details and access to the data is maintain under strict regulation. We have detail records for the purpose of processing, descriptions of categories, detail data flow diagrams and full documentation of all third party data processors we work with. This is complemented by our policies on security, continuity and privacy.

19. Does TeamKinetic have a Sub-processor or level 2 processor change request process?

TeamKinetic shares very limited data with sub-processors and that data is anonymised. All sub-processes are legally bound by TeamKinetic to meet our data standard as outlined in schedule 6.


All customers are asked to review the schedule below. This will be sent in a separate email to all existing customers as an addendum to our current agreement and will require signing as soon as possible.

Schedule 6 Data Protection
1. Data Protection

1.1 For the purposes of this clause, the following definitions apply;
(i) ‘Data Controller’, ‘Data Processor’ and ‘process’ have the meanings given to them in the Data Protection Act 1998 and from May 2018 the General Data Protection Regulation 2016/679;
(ii) Service Users shall mean those who sign up to use the Services.
(iii) ‘Personal data breach’ has the meaning given to it in article 4(12) of the General Data Protection Regulation 2016/679;
(iv) ‘ Personal Data’ shall mean the personal data of the Service Users including their name, contact details, email, address, disability information, gender and employment or education experience.
(v) ‘Privacy Laws’ means the Data Protection Act 1998, Directive 95/46/EC, the General Data Protection Regulation 2016/679 qne the Privacy and Electronic Communications Regulations 2003; and
(vi) ‘Privacy notice’ means a notice providing individuals with information about the purpose for which and manner in which their personal data will be processed and the organisations that will be undertaking that processing.

1.2 With respect to the parties’ rights and obligations under this Contract, it is acknowledged and agreed that the Customer is the Data Controller and the Supplier is the Data Processor in relation to the Personal Data.

1.3 Where processing Personal Data on behalf of the Customer the Supplier agrees to;
(i) provide the Services in compliance with all relevant Privacy Laws;

(ii) not do anything (or permit anything to be done) which would put the Customer in breach of its obligations under Privacy Laws;

(iii) only process the Personal Data in accordance with the Customer’s instructions and only for the purpose of delivering the Services and not for any other purpose;

(iv) only process the Personal Data in such manner as is described in the Contract and, in any event, only process the Personal Data to the extent that is necessary to deliver the Services;

(v) implement and maintain the technological and organisational measures to protect the Personal Data against accidental or unlawful loss, alteration, destruction, or unauthorised disclosure, dissemination or access, or alteration;

(vi) not disclose or transfer the Personal Data to any third party (save where disclosure has been specifically authorised by the Customer under this Contract) and only provide access to the Personal Data to your personnel where such access is necessary for the provision of the Services

(vii) take reasonable steps to ensure the reliability of any of your personnel who have access to the Personal Data, ensure that those personnel are aware of their obligations set out in this clause 1 and have undergone adequate training in the care, use and protection of personal data in compliance with the Privacy Laws.

1.4 Upon the Customer’s request, the Supplier agrees to permit the Customer or its authorised agents to inspect the Supplier’s premises, data processing activities and systems, and/or have access to, and be provided with copies of any information (including without limitation the Personal Data) to enable the Customer to be satisfied the Supplier are complying with the obligations under this Schedule 6.

1.5 The Supplier must not sub-contract or assign any of its right or obligations under this Contract without the Customer’s prior written consent.

1.6 Where the Customer provides written consent to sub-contracting of the Services under clause 1.6, then the Supplier agrees to impose a binding legal obligation on their sub-contractor to comply with the obligations in this Schedule 6 where that subcontractor has access to, or will be otherwise processing, the Personal Data. For the avoidance of doubt, any such subcontract shall not relieve the Supplier of its obligation to comply fully with this Schedule 6 and the Supplier shall remain fully responsible and liable for ensuring full compliance with this Schedule 6 in all respects.

1.7 The Supplier will not transfer any Personal Data processed under or pursuant to this Agreement outside of the European Union without the Customer’s prior written authorisation. Where the Customer authorises the transfer of Personal Data outside of the European Union, the Supplier agrees to comply with any instructions the Customer may issue which are necessary to achieve compliance with the Privacy Laws.

1.8 The Supplier agrees to notify the Customer as soon as practical, and in any event within five working days, if the Supplier receives;

i. a request from an individual to access their Personal Data or to exercise the rights of individuals under Privacy Laws including the rights of rectification, restriction, blocking, data portability and/or erasure;
ii. a complaint relating to the processing of Personal Data under this Agreement;
iii. notification that an individual wishes to withdraw their consent, or otherwise objects, to the processing of their Personal Data under this Agreement; or
iv. any communication from the Information Commissioner or any regulatory authority in connection with the Personal Data.

1.9 The Supplier agrees to comply with our instruction regarding the response to and handling of a complaint, request, notification or communication described in clause 1.9 and provide such reasonable assistance to the Customer as is required to ensure that the Customer can comply with its obligations under the Privacy Laws.

1.10 The Supplier agrees to notify the Customer promptly, and within 24 hours, in the event of an actual or suspected personal data breach involving the Personal Data processed under this Agreement. The Supplier agrees to co-operate with the Customer fully to investigate such a breach by furnishing the Customer with information as may be reasonably required about the breach and the Supplier’s processing activities. The Supplier also agrees to comply with the Customer’s reasonable instructions regarding the management of and response to the breach and any steps necessary to prevent an equivalent breach in the future.

1.11 The Supplier agrees to comply with the Customer’s instructions as to the period for which the Personal Data shall be retained and regarding secure destruction or return of the data to the Customer following expiry of the Term.

1.12 The Supplier agree to indemnify and keep indemnified the Customer against all claims, demands, actions, proceedings, charges, costs and expenses (including legal costs and expenses) which may be brought against us in respect of or in any way arising out of or in connection with;
i. your breach of the obligations in this Schedule 6; or
ii. a claim that we are in breach of our obligations under the Privacy Laws as a result of any of your actions.

Are you ready for GDPR?

A whitepaper to help you get ready for GDPR and find out what it means for your data.

Whitepaper – Are you ready for GDPR – Download the paper here.

What should you be doing now?

If you haven’t started preparing your organisation for compliance then the next 3 months are crucial. If you have started getting ready for the GDPR deadline,  keep going.

Make sure your board is bought in to the importance of the project. Having the support you need from the top is vital to the GDPR compliance process.

ONCE THE GDPR COMES INTO FORCE, YOUR BUSINESS MUST:*

  1. Keep a record of data operations and activities and consider if you have the required data processing agreements in place
  2.  Carry out privacy impact assessments (PIAs) on products and systems
  3.  If applicable to your organisation, designate a data protection officer (DPO)
  4.  Review processes for the collection of personal data
  5.  Be aware of your duty to notify the relevant supervisory authority of a   data breach
  6. Implement “privacy by design” and “privacy by default” in the design   of new products and assess whether existing products meet GDPR standards

 

What are TeamKinetic doing right now

See what we have already put in place, to be ready for 25th May 2018.

https://teamkinetic.co.uk/blog/2018/02/07/teamkinetic-updates-new-eula-and-data-policy/

We continue to work with our customers to ensure compliance and understanding.

Are you ready for GDPR?

Deadline – 25th May 2018

Information sourced from UKFast, Berwin,Leighton,Paisner and Onside Law

Contents

Let’s refresh

Why has the GDPR come about?

What about Brexit?

What should you be doing now?

Data security is EVERY business’s business

Key changes to consent

Key changes to breach notifications

Are the rules different for electronic communications?

What is TeamKinetic doing right now?

Disclaimer: The information in this whitepaper is for your general guidance only and is not and shall not constitute legal advice. If you need advice on your rights or responsibilities or any legal advice around data protection matters, please obtain specific legal advice and contact an adviser or solicitor.

Let’s refresh…

What is the GDPR? The General Data Protection Regulation (GDPR) is a binding legislative act from the European Union for the protection of personal data. The Regulation tackles the inconsistent data protection laws currently existing throughout the EU’s member states and facilitates the secure, free-flow of data.

Why do you need to know about it?

As of April 2016, businesses have been preparing for the legislation coming into effect on 25th May 2018. Although we are in the process of leaving the EU, working towards GDPR compliance remains crucial.

If you fail to comply with the Regulation you could find yourself being fined up to 4% of your company’s global annual turnover and your reputation damaged beyond repair.

That is 4500% increase on current fines that can be issued by the ICO!!

Now that the deadline is just 3 months away, is your organisation ready?

Why has the GDPR come about?

There is a need in Europe and beyond for a standardised data protection framework that addresses the rapid technological advancements that have taken place in recent years, putting the personal data of the masses at risk.

Where do vulnerabilities lie?

Everywhere. All organisations are at risk of a cyber-attack, despite common misconceptions that some industries are more secure than others.

The results of a survey carried out by the Information Commissioner’s Office (ICO) of 173 councils at the end of 2016 reveals that more than 15% of councils do not have data protection training for employees processing personal data and a third do not carry out privacy impact assessments (PIAs) as required by the GDPR.

The survey’s release coincided with the news that the ICO had fined Norfolk Council £60,000 for a data breach in which social work files were discovered in a cabinet bought in a second-hand shop by a member of the public.

Capgemini: The Currency of Trust, February 2017

74% of UK SMEs had a security breach in 2016.

While leaving vulnerable information in a cabinet or on a train may seem like a problem from 1997 rather than 2017 – when cloud technology means physical files never need to leave the office – the overarching security challenge remains.

Professionals across the public and private sectors must be aware of the nature of the data they are accessing from their home networks and ensure they are doing so securely.

Computer Weekly: Many Councils Still Unprepared for GDPR, March 2017

What about Brexit?

Despite the vote to leave the EU, UK businesses must continue to work towards GDPR compliance. Not only has the UK government stated that it is good business practice to do so, but the legislation applies to all businesses working within the EU and with EU data. A failure to comply can lead to significant fines and irreparable damage to a company’s reputation.

The latest thinking is that the UK could replace the 1998 Data Protection Act (DPA) with legislation that mirrors the GDPR, enabling the UK to achieve free data flow with the EU post-Brexit. The government has warned that it may take two to three years for the European Council (EC) to decide that the UK has an adequate data protection regime.

While the impact of the Investigatory Powers Act on the UK’s GDPR compliance has yet to be fully understood, it is possible that the mass surveillance and data retention practices carried out under the Act could cause issues when the EC comes to decide whether the UK’s practices are adequate. The existence of these two extraordinarily contradictory legislations could result in a UK equivalent of the Privacy Shield agreement held between the US and the EU to facilitate secure transatlantic data flow.

If your business activities are contained within the UK or elsewhere within Europe, you will have to observe the protections afforded by the GDPR for citizens.

What happens if my business is not complaint?

The GDPR introduces a two-tier fine system that emphasises just how small a financial deterrent existed under the Data Protection Act (DPA).

As of the 2018 deadline, any data controller or processor that fails to comply with the Regulation will face the following fines:

 

Tier 1

If a data breach occurs that puts highly important data at risj, the data controller/processor will be fined upto €20M (£17.25M) or 4% of the previous year’s global annual turnover, whichever is greater.

Tier 2

Any other data breach could lead to fines of up to €10M (£8.6M) or 2% of the previous year’s global annual turnover, whichever is greater.

 

It is estimated that if breaches remain at the same level as in 2015, the fines given will raise 90 fold from €1.4 billion to €122 billion

Key changes to consent

Do you ask your customers for permission before you use their data? Do you go a step further and tell them what it will be used for? If the answer to either – or both – of these questions is no, you could be in trouble if you don’t start changing your ways before the GDPR deadline.

 

Why is consent important?

Consent enables your business to lawfully process data.

Organisations applying the GDPR’s standards are giving individuals greater control over their information and, in turn, building trusting relationships that ultimately keep customers coming back for more.

Any business found to be misusing personal data will be fined according to the highest level of the two-tier system and – most poignantly – is at serious risk of damaging its own reputation. When is consent required? You must have the data subject’s consent to lawfully process their data. However, just to confuse things, there are instances that will call for consent to be acquired via alternative methods; we’ll clarify this shortly. Consent is also needed under ePrivacy laws if you’re in the business of tracking communications and installing software and apps on devices.

If you want to use someone’s personal data they must give you explicit consent to do so. This means in practise no pre-ticked boxes, a user must always choose to tick the box.

If you want to use an individual’s personal data for multiple purposes, they must give consent for each purpose, separately

 

Who might need an alternative method of gaining consent?

Most commonly, data controllers in a position of power such as public authorities and employers who are likely to find getting valid consent challenging and so must consider the alternative options.

For example, if you are a highly successful eCommerce business is bringing on board a new supplier of garden furniture, you will need a contract with them that clarifies the role of each party and enables you to lawfully process their data.

Whether you are the data controller or processor, you must always record how consent was given, who from, when, how, and what the interested parties were told.

You must not bundle your consent request with your standard terms and conditions.

 

Does your consent process meet GDPR standards?

Carry out a thorough review of existing consent processes and asses whether they meet the Regulation’s requirements. if they do, there is no need to request consent from the subject again.

Key changes to breach notifications

Europe had a phenomenally inconsistent data protection landscape. It meant that when a Switzerland-based business suffered a data breach affecting people in Greece, Italy and Spain, the organisation would need to comply with the breach notification standards of each of the three member states.

This lack of uniformity throughout Europe means that while some member states, such as Spain and Germany, are recognised for their rigorous data breach privacy laws, there are also member states with minimal to no regulations in place.

In this environment, organisations in lax member states have not needed to notify an authority of a breach.

The GDPR smooths all this out with the introduction of a single breach notification requirement.

 

What is a personal data breach?

A personal data breach is not simply the loss of data but a breach of security, resulting in the destruction, loss, alteration, unauthorised disclosure of or access to personal data.

When must the relevant supervisory authority be notified?

The relevant supervisory authority must be informed of any data breach that puts an individual’s rights and freedoms at risk. This includes a loss of confidentiality and financial loss.

Data controllers must inform the supervisory authority without undue delay and within 72 hours of learning of a personal data breach. They must state:

  1. Its nature
  2. The approximate number of people affected
  3. The contact information for the organisation’s DPO (if one has been appointed)

The controller must also pin-point the likely consequences of the breach and the measures taken to reduce further risk to those affected.

Data processors must tell the data controller about a data breach without undue delay after having become aware of it.

If a breach is significant enough that it is in the public interest, those responsible – be that the controller or processor – must do so without undue delay.

The impact of data breaches If we hark back to our real world TalkTalk and Yahoo examples, we can see that the severe consequences each company experienced following their respective breaches were related to how they handled the aftermath of the breach and not simply because the breach happened in the first place.

What should you be doing now?

A personal data breach is not just the loss of that data but a breach of security, resulting in the destruction, loss, alteration, unauthorised disclosure of or access to personal data.

  • Educate your employees about    personal data breaches and how to   spot when one has occurred.
  • Set-up an internal process for reporting   a personal data breach.
  • Make sure you have the internal resources and processes in place to   detect and investigate breaches. Speak to any third-party data processers if they are storing your data.
  • Put an incident response plan in place.

Are the rules different for electronic communications?

No, not really. The EU has introduced a complementary legal framework to the GDPR to clarify exactly what data controllers and processors must be doing to protect individuals’ communications; electronic or otherwise.

  1. New cookies responsibilities   for browser providers Users must be given the choice to consent to cookies as part of the browser software set-up. This should reduce or eliminate cookie banners on websites entirely.
  2. Extra-territoriality and 4% fines The Regulation no longer applies solely to the EU. It applies to anyone in the world that provides publicly-available “electronic communications services” to acquire data from the devices of EU citizens. Any organisation that breaches the Regulation will be subject to the GDPR’s two-tier fine system. That means you should be paying attention even if your business is contained within the UK.
  3. The Regulation application is expanded Unlike its predecessor, the ePrivacy Directive, the ePrivacy Regulation goes beyond the traditional telecommunications organisations and internet service providers. It incorporates messaging apps like WhatsApp, and email providers, amongst other communications suppliers such as Facebook and Snapchat.
  4. New rules for processing communications data The Regulation introduces new rules for handling: what was said, who said it, where and when. This data is confidential; interfering with it could result in a Tier 1 fine.
  5. Exemption analytics cookies Businesses are exempt from the cookie consent requirement when using firstparty analytics. However, using third-party analytics platforms such as Google Analytics requires user consent.

For the non-techy amongst you, ‘party’ refers to the website that places the cookie. So when you visit www.ukfast.co.uk, and you find the domain of the cookie placed on your computer is www.ukfast.co.uk, this is a first-party cookie. If you visit www.ukfast. co.uk and a cookie by a suspiciously dissimilar name appears, this cookie has been placed by a third party.

Like the GDPR, the ePrivacy Regulation will come in to effect on the 25th May 2018.

Source: http://privacylawblog.fieldfisher.com/2017/the-new-e-privacy-regulation-what-you-need-to-know/

Powered by WordPress & Theme by Anders Norén