mrerus

Resolved: This was just a CSS conflict.

Thank you very much, obvious once you know!

Hi, Did you do the following for your particular Contact Form?

https://www.dropbox.com/s/p6cocrtd3hv99zl/gdpr-framework-1.0.9-screenshot.PNG?dl=0

@indrek_k

That’s great many thanks for the reply.

I’ve tested your 1.0.9-RC1 version with Flamingo and it appears to work great, brilliant!. One minor bug I found was that if you use an Alias style email address i.e. ‘[email protected]’ then it can’t be found using the ‘Find data subject by email’ as the ‘+’ becomes a ‘ ‘ hence no data found despite it existing, I know this is a very minor/unlikely issue but I thought it worthy of mention.

A quick question: What is the purpose of the ability to withdraw only ‘Consent’? At the present time consent can be withdrawn but the data will remain unless the user specifically selects ‘Delete Data’. I’d assume if ‘Consent’ is withdraw then their data should also removed? (It’s highly likely that I’ve misunderstood something but I’ll ask anyways).
UPDATE: I’d guess consent withdrawal is useful/required for those with more than one ‘Consent type’ (I.e. Subscriptions/Marketing opt-in/opt-out etc.) but if Consent is withdrawn from a ‘consent type’ that’s associated with data such as a Contact Form submission then in my mind the data should also be deleted.

I’m more than happy to test any other releases (I’m about the next couple of days so plenty of time for testing if required.

Huge thanks for all your efforts thus far, greatly appreciated.
Regards,

Mark.

• This reply was modified 6 years, 6 months ago by mrerus.
• This reply was modified 6 years, 6 months ago by mrerus.

Thanks for all the responses to this post.

For clarification purposes am I correct in thinking that that site ‘Visitors’ will have no way request removal of the data (data may not be stored on the website itself but in my case sent to an external email service directly from the Contact Form) or consent prior to the GDPR go live?

I like many have found very contradictory information with regards to GDPR but personally intend to perhaps adopt the safest stance and assume the worst, overdo it rather than under.

Generally, as the plugin doesn’t work for ‘Visitors’ at this time do you think a simple Form for requesting ‘Data Deletion’ and/or ‘Remove Consent’ would be sufficient (I’d just need to delete the associated entries from the db table manually), my concern with this is that anyone can submit a request without checking if they the real users (probably ok short term?).
Alternatively, I could force create a user when Contact Forms are submitted, but I’d rather not take that approach if possible.

Any thoughts?

Kindest regards,
Mark.

• This reply was modified 6 years, 6 months ago by mrerus.
• This reply was modified 6 years, 6 months ago by mrerus.