topic Re: GDPR in GDPR

GDPR

Grovewilks — Wed, 02 Aug 2017 15:47:41 GMT

Could somebody advise on the Hubspot policy in relation GDPR that will be hitting us in May 2018.

How will Hubspot manage opt-in and refresh of opt-in?

How will Hubspot manage the relevant questions to allow someobody to opt-in or download web content

How will the data that Hubspot store be managed in relation GDPR

There are many questions on this topic, where do Hubspot stand in general in realtion to this

Re: GDPR

edjusten — Thu, 03 Aug 2017 03:52:51 GMT

Hi @Grovewilks Find out more about HubSpot GDPR compliance here.

Re: GDPR

jhollidge — Thu, 03 Aug 2017 10:12:34 GMT

GDPR is a really big deal for us so I hope some further thinking on this comes out soon! I know May 2018 might seem like a way off, but it will come round pretty quick and we need to have quite a few issues resolved before then.

Re: GDPR

edjusten — Wed, 11 Oct 2017 14:33:01 GMT

Hi @jhollidge Do you have some specific concerns not addressed by the website linked above?

Re: GDPR

c2b2 — Thu, 19 Oct 2017 08:23:47 GMT

The complete lack of action and undertsanding from HubSpot on GDPR compliance is absolutley shocking - and the inability of anyone to communicate what their plan is to ensure customers can meet GDPR requirements is extremely concerning - to the point where some people may feel that HubSpot isn't going to be an option for their businesses going into 2018.

The fact that they are asking people for 'specific concerns' is a joke - I mean RTFM!!!

The ICO have extensive guidence on GDPR, and whilst there is still some areas of interpretation, the fact that HubSpot hasn't responded to the key issues of consent for marketing communications is desperately ignorant for an inbound marketing company.

Additionally, since GDPR not only affects EU companies, but ANY company trading with or creating contacts in the EU (i.e) the yanks - you'd have thought they be paying attention to the effects GDPR will have on their users and customers (not simply the high-level areas of safe-harbours).

You want issues, here are a few issues:

Issue #1

When a new contact is created in the CRM, they are automatically opted-in to all marketing communications. This will cause comprehensive failure of consent compliance if contacts view their preferences and see that we've pre-populated consent boxes, this in itself could be a cause of complaint or breach, even if we don't actually send out communications.

Development proposal

When creating contacts, all email types should be set to opt-out
Then, one or more email types must have consent applied by one of the following methods:

Forms (and lead flows) should offer the functionality to apply consent to one or more email types
Workflows should have the functionality to apply consent to one or more email types (depending on what form was submitted)

Issue #2

If the contact unsubscribes from all emails and then chooses to re-subscribe, the action results in consent for all marketing communications (rather than giving the option to opt-in to selected communications).

This will potentially cause compliance failure on consent and awareness of consent because:

If we offer different communication types, the contact should be able to opt-in to each individual communication option when re-subscribing
Because clicking the re-subscribe button launches a confirmation page away from the marketing preferences page, the contact may not be aware that they have been opted-in to all communications.

Development proposal

A completely compliant solution is for HubSpot to change the re-subscribe process so that the contact opts-in to each type they wish to receive and then selects re-subscribe. This process will only re-subscribe them to the selection made.

Issue #3

When a new email type is created, the contact's marketing preferences automatically show the contact as having consented to receive the new email type. This will cause comprehensive failure of consent compliance if contacts view their preferences and see that we've pre-populated consent boxes, this in itself could be a cause of complaint or breach, even if we don't actually send out communications.

Development proposal

New email types must automatically have a default value of 'opt-out'

Issue #4

We are obliged to provide evidence of when and how contacts opted-in. This is contained only in contact histories – and so cannot be exported and cannot be migrated.

Development proposal

We should be able to export ANY data from the CRM in a machine readable format – not simply contact properties, but correspondence and actions as well.

Biggest issue for me right now is the lack of movement from HubSpot.

Re: GDPR

c2b2 — Thu, 19 Oct 2017 14:54:49 GMT

Tom - finally!

Thank you for addressing this seriously - I had a fear that no one at HubSpot knew what was going on - but the longer it takes for you to get these implemented - the longer any new contacts go without being compliant - meaning retrospective action by users - we really need action ASAP!!

Re: GDPR

SineadIreland — Wed, 25 Oct 2017 15:24:05 GMT

Good to hear that it is being worked on - my concern is the amount of ground work and preparation we will need to do before the deadline next year. We need to have our own plans in place before May - but it's hard to do this without knowing exactly what Hubspot will be doing as regards compliance and when it will be available to us...???

Re: GDPR

alivia — Tue, 31 Oct 2017 10:23:48 GMT

Specific GDPR concern: how will Hubspot logs fall under the "right to data portability"?

Technically, in Husbpot we store infomration on each page visit and interraction, however this cannot be exported using the API (or exports), so we won't be able to communicate *all* the data relative to a customer.

Correct?

Re: GDPR

shearn — Thu, 02 Nov 2017 11:57:25 GMT

I've brought up the concerns regarding the auto opt-in's before and I've received the same response. As someone who is leading the charge for GDPR for our marketing team, I need to make sure we have things as tight as possible and I have no control over this process.

I've just received our first 'request for data' and the need to export contacts full profile has never been more crucial. I literally have to copy and paste each line of data from a contact profile into an excel sheet so I have full documentation...If someone has any suggestions on how to document/export a full profile it would be greatly appreciated.

Re: GDPR

jhollidge — Thu, 02 Nov 2017 12:26:33 GMT

Not that I have done this in the past, but off the top of my head:

Create a new list and put the single contact into the list
Then go into the list (of one contact) and export the list
When given the option of what fields to export, select all of them.

Not ideal by a long shot.... but better than copying and pasting a few hundred times!

Re: GDPR

shearn — Thu, 02 Nov 2017 12:38:42 GMT

Thanks @jhollidge,

I've done it the way you've mentioned as well, but I would still feel safer if we could get an entire log of a contact. For example, timestamps on their various actions overtime, or in my recent case a list of all of the communications we've sent the contact over time.

I'm probably going a bit overboard with what we would need to present, but I just want to cover all my bases.

Re: GDPR

ojobson — Tue, 07 Nov 2017 16:26:54 GMT

Alivia / Shearn,

I was under the impression that, when answering a 'Subject Access Request you only need to provide their Personally Identifiable Information, the source of that information and any recipients of it. I'm not sure that one single page view could be counted as PII.. so you are not obliged to provide this?

Have I got it wrong?

Re: GDPR

halvork — Thu, 07 Dec 2017 16:29:27 GMT

You had good issues 🙂

You refer to Tom's respons - Is that available ? Did not see anything in the community.

Best regards

Halvor K

Re: GDPR

c2b2 — Thu, 07 Dec 2017 16:35:39 GMT

Hi Halvor,

Tom did reply and did make a committment to having solutions to these specific issues in place by May.

However...

His post was then withdrawn by HubSpot a day later on the advice of their legal team.

Make of that what you will 🙂

Re: GDPR

jm — Tue, 19 Dec 2017 09:27:47 GMT

Great. So Hubspot's legal team won't commit to the one thing they're are supposed to commit to.

Re: GDPR

jm — Tue, 19 Dec 2017 09:57:35 GMT

There is also a thread here concerning Canada's anti-spam laws though I posted my GDPR concerns regarding subscriptions and consent as they are pretty much the same.

In short, HubSpot’s consent management is definitely way below par and probably broken in light of GDPR (if you have more than one option for your visitors to sign up for).

I understand the legal team don't want to say anything but it's reflecting poorly on Hubspot now. They've had 2 years to get this in order. Considering the cost of Hubspot, this lack of clarity is simply not acceptable.

Re: GDPR

ojobson — Tue, 19 Dec 2017 13:58:12 GMT

Yeah, this is a massive concern for us. My organisation is fairly risk averse and I may end up having to throw the system out, as being not fit for purpose, if it can't be said to be GDPR compliant.

Re: GDPR

edjusten — Tue, 19 Dec 2017 16:30:44 GMT

HI @ojobson and @jm. Our Product and Security teams are working on the GDPR plan. We'll have updates in the coming months. Please refer to our GDPR website for the most current information. You can also reach out to your account managers, who can pass further queries on to the GDPR team.

Thank you,

Ed Justen

Re: GDPR

nknoop — Thu, 28 Dec 2017 19:51:03 GMT

Hi everyone,

I work on the legal team at HubSpot and help run our GDPR compliance project. I’ll try to address some of the concerns raised above, and give everyone some insight into the status of the internal project and what our plans are for 2018.

We are fully committed to enhancing the HubSpot platform to enable customer/partner compliance with the GDPR. We appreciate that there may be current gaps in how our product interacts with some of the key GDPR requirements; we are actively working with our Product teams to address those areas, as well as introduce new product functionality that will help you comply.

For example, we are working on improving the way the CRM and Email product handles and tracks consent. As a previous post on this thread has recognized, this is a huge part of the regulation and is of particular significance to marketing and sales teams. Especially considering the recent Article 29 Working Party guidance on this point, we know we need to do a better job off helping customers manage and track consent.

The other areas we are working on improving include the Subscription Preference Pages, notice and consent in forms/CTAs, cookie management and preferences, double opt-in improvements, and tools to help our customers comply with data subject access/modification/deletion requests. We'll be announcing these changes on a rolling basis leading up to the GDPR's enforcement date of May 25, 2018.

The regulatory guidance helps shape the solutions we are crafting, and that’s part of the reason we are not immediately releasing product changes. Rather than releasing new functionality now that will later have to be modified based on new interpretations of the GDPR, we want to be sure our product aligns with the groups like the Working Party before changes are finalized.

Apart from improvements to the product itself, we are working around the clock on how the GDPR effects other parts of HubSpot. For example, we’re digging into how integrations/Connect partners fit in a GDPR world. Further, we have involved key members of every department within HubSpot to help on this project (mainly IT, Security, Product/Engineering) to drive towards compliance by this coming May.

We’ll be communicating out project updates to our customers and partners starting in late January 2018.

I'm happy to chat with anyone, so if you have specific questions or concerns, feel free to reach out via direct message and include your email address.

Nick

Re: GDPR

jm — Tue, 02 Jan 2018 10:25:30 GMT

Appreciate this Nick, @nknoop . That gives me a lot more comfort and something I can communicate to my team. Looking forward to regular updates to help with some forward planning especially if there is work to be done as a result of consent/subscription mechanism changes.