Bullhorn steps for GDPR (General Data Protection Regulation)

Forum for users and developers of Bullhorn's new REST API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
ashishM
User
Posts: 28
Joined: Tue May 03, 2016 2:28 am

Bullhorn steps for GDPR (General Data Protection Regulation)

Post by ashishM » Thu Mar 15, 2018 9:55 am

Hi,

GDPR is a regulation by which the European Parliament, the European Council, and the European Commission intend to strengthen and unify data protection for all individuals within the European Union (EU). GDPR stands for General Data Protection Regulation effective from 18th May 2018.

My question is, to compliant with GDPR what steps Bullhorn has taken so that customers can make the data secure.

ColinC
User
Posts: 67
Joined: Fri Apr 08, 2016 4:54 pm

Re: Bullhorn steps for GDPR (General Data Protection Regulation)

Post by ColinC » Fri Mar 16, 2018 4:38 pm

Hello,

Bullhorn has a commitment statement about this here:
https://www.bullhorn.com/uk/gdpr-commitment-statement/
Colin Coffman
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
617-478-9126 (US Support)
+44 800 032 2848 ext. 9131 (UK Support)

ashishM
User
Posts: 28
Joined: Tue May 03, 2016 2:28 am

Re: Bullhorn steps for GDPR (General Data Protection Regulation)

Post by ashishM » Wed Mar 28, 2018 11:04 am

Thank you ColinC for your reply.

I have gone through the link but I didn't find any specific information I need. Actually, I need the way how Bullhorn is implementing to comply GDPR.
e.g As per GDPR, let's say any one candidate requested his information for any two fields in BH need to be forgotten. How do Bullhorn will handle this situation?

I am using REST API in my C# for syncing BH entity records in my application both ways - retrieving from and inserting/updating to Bullhorn.
I want to implement it in my application as well so that I can also handle the two fields (need to be forgotten in the above example) information.

Please let me know what way you are handling the above situation, eventually, it will impact the way I am fetching and updating records in Bullhorn.

For your ref, Sugar CRM is handling by the below way -
https://community.sugarcrm.com/docs/DOC ... pabilities

Post Reply