Old Version 5
changes.mady.by.user Ann Base
New Version Current
changes.mady.by.user Ann Base
- This line was added.
- This line was removed.
- Formatting was changed.
Nexus sees the EU's general data protection regulation (GDPR) as an important step forward in streamlining and unifying data protection requirements across the EU. We also see it as a great opportunity for us to strengthen our clear commitment to data protection principles and practices. It is as well fully in line with our recent ISO 27001 certification in Sweden.
Nexus strives to make it as easy as possible for our customers to comply with the requirements of GDPR, which will begin was introduced on May 25, 2018. We will continuously review the functionality of Nexus Card SDK in terms of GDPR.
The following functionality is implemented in Nexus Card SDK, to help you to be compliant with GDPR:
Card SDK do not store any run-time data in normal operation and therefore only has GDPR-related data temporarily in the memory during card production or capturing operations. The surrounding systems, like Smart ID Identity Manager (PRIME) or 3rd party applications that integrate with Card SDK, are responsible to handle all user data.
Card SDK might write GDPR-related data into error logs, if these logs are activated for debugging or troubleshooting purposes. This logging is deactivated by default and Nexus strongly recommends to only activate the logging functionality on demand (when investigating an issue). Deactivate the log immediately after troubleshooting and delete the log files from the client.
A major part of GDPR is about internal routines. Organizations are responsible for personal data, regardless of whether it is a HR system, CRM system, security system, PACS system, real estate system or other. Each organization must ensure that staff handle personal data properly. This includes, among other things, having a legal basis for processing personal data, keeping track of the personal data being processed and the context in which to handle only the information necessary for the purpose expressed, deleting data when no longer required, and to inform and, where necessary, obtain consent from registered persons.
Please also observe that the GDPR acknowledges that data protection rights are not absolute and must be balanced proportionately with other rights – including the “freedom to conduct a business”. For more information on the ability of EU member states to introduce exemptions, see the section on derogations and special conditions.
As a regulation, the GDPR will be directly effective in EU member states without the need for implementing legislation. However, on numerous occasions, the GDPR does allow member states to legislate on data protection matters. This includes occasions where the processing of personal data is required to comply with a legal obligation, relates to a public interest task or is carried out by a body with official authority. Numerous articles also state that their provisions may be further specified or restricted by member state law. Processing of employee data is another significant area where member states may take divergent approaches. Organizations working in sectors where special rules often apply, for example health and financial services, should: (1) consider if they would benefit from such special rules, which would particularize or liberalize the GDPR; and (2) advocate these accordingly. They should also watch for member states seeking to introduce special rules, which may prove restrictive or inconsistent across member states.