Please Log in or Create an account to join the conversation.
This is not correct at all. Compliance does not mean automation. Automation is convenience. The functionality in CB Privacy is not going to cross over into any other plugins. If you want the automated functionality CB Privacy provides you will need to purchase CB Privacy. The alternative is handle deletions and data exports manually or wait for Joomla 3.9 privacy component integration plugin (which will be free).Last question; since this is the only way to be compliant with law, will this become an included part of CB & CBSubs in future releases? Currently there is an additional charge for CB Privacy, but without it CB/CBSubs is not compliant so just wondering if you will update this as an inclusion so your product is fully compliant for us all without additional requirements
Please Log in or Create an account to join the conversation.
Not asking you to. If you read my question carefully you’ll see that I’m asking specifically about CBSubs data which is not clearly answered in your blog, which I already read...krileon wrote: Please everyone I do not want to have to repeat my self a hundred times across the forums. Read the blog very carefully. If you've further questions contact a lawyer.
Let me clear this up for you, basically what you’re saying here is that the expectation is for people to purchase your product which is absolutely not compliant in itself unless your users know how to not only export data via sql or by other means (all require a pretty extensive amount of knowledge that many site owners don’t have) or have a developer do it. So while you can it convenience, I would call it a courtesy for all of your users that continue to pay for your products. To add to that, we purchase your products (have for years) because it is a full component and the expectation would be that it would continue to be that way and not require us to do additional things just to remain lawful.krileon wrote: This is not correct at all. Compliance does not mean automation. Automation is convenience. The functionality in CB Privacy is not going to cross over into any other plugins. If you want the automated functionality CB Privacy provides you will need to purchase CB Privacy. The alternative is handle deletions and data exports manually or wait for Joomla 3.9 privacy component integration plugin (which will be free).
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
We do not have any form of data export functionality. This is clearly stated in the blog. All of that, at this time, must be done manually via phpmyadmin database export. You've 30 days to comply with data export requests, if you should ever get one, so should be ample time to perform a phpmyadmin export of rows attached to their user id.Not asking you to. If you read my question carefully you’ll see that I’m asking specifically about CBSubs data which is not clearly answered in your blog, which I already read...
We will be providing export functionality by integrating directly into Joomla 3.9 privacy component. CB Privacy will also eventually have a data export field for users to do this easily from profile edit themselves, which will include triggers for plugins to extend the export even further. This again is clearly stated in the blog.Furthermore I am well aware that I’d need to contact a lawyer if we have our own internal compliance questions, but we’re already compliant. The only thing that is causing a problem is your component. Every other component we use has already implemented the export button option very easily, from what I’ve read on your forum this seems common.
As stated in my blog..Let me clear this up for you, basically what you’re saying here is that the expectation is for people to purchase your product which is absolutely not compliant in itself unless your users know how to not only export data via sql or by other means (all require a pretty extensive amount of knowledge that many site owners don’t have) or have a developer do it. So while you can it convenience, I would call it a courtesy for all of your users that continue to pay for your products. To add to that, we purchase your products (have for years) because it is a full component and the expectation would be that it would continue to be that way and not require us to do additional things just to remain lawful.
All of our backend table views will eventually have import/export functionality as we simply want that built into our API. That however has nothing to do with GDPR implementation, but I guess it could be used for that. I've no idea when this will be implemented.Please done mistake my message for rudeness, rather being direct as you were. So I’ll ask again regarding the CBSubs information and being exported?
At this time CB Privacy does not export anything as stated in my blog. When it has export functionality it will provide the necessary triggers for plugins to integrate with it to extend the export beyond profile data.In addition to my above reply, I’ll be purchasing the CB Privacy additionally however I still need confirmation that it will export all CB & CBSubs data to be fully compliant, otherwise there wouldn’t be a point in us purchasing.
We do not provide lifetime purchases. All individual plugin subscriptions come with 6 months of support and updates. So if the export functionality is released within those 6 months then no you won't have to renew. I do not know when it will have the export functionality, but I assume within the next 6 months is a reasonable guess that it will be available. Again, we plan to integrate with Joomlas 3.9 privacy component when possible and will be free.Lastly before we purchase the plugin, we’d also like to know if we will need to purchase it multiple times. There is simply no need for us to have an additional subscription with you guys (professional) because we don’t need anything more. So if we purchase the privacy plugin would we be eligible to download it when you add the export data options? Thanks
Please Log in or Create an account to join the conversation.