QuoteAre there any exact guidelines how to make shop GDPR compliant , like a final list with rules 1,2,3 etc.. ?
difficult to answer in a foreign language...
Checklist: The most important points for GDPR compliance at a glance (
source)
- #1: Draw up a privacy policy or adapt it if necessary
- #2: Adapt forms so that customers are adequately informed about data processing and only data that is actually required is requested
- #3: Ensure sufficient encryption - in some contexts, a more specialised SSL certificate or deeper encryption may be appropriate.
- #4: Scrutinise analysis tools and adapt the way they are used if necessary - clear information about the use of data, consent options and anonymised IP addresses should be guaranteed.
- #5: Customise cookie banners so that users can specifically consent to the use of relevant information or not, depending on the purpose.
- #6: Adapt newsletters or correctly organise address data used for email marketing - consent by recipient, documentation of sources, data protection notice, etc.
- #7: Create or adapt general data protection documentation - according to the GDPR, e-commerce companies are obliged to be able to prove compliance with all legal regulations.
- #8: Create or adapt protection for minors if data of underage visitors is processed - i.e. provide an explicit consent option for legal guardians
- to #1: best solution for WB and a new shop module in my eyes: a own part for a special shop privacy police in the shop administration and add this via droplet or section picker to the general privacy police of this website. What ever you do, it is (in my eyes) not possible, to build a shop system, working without cookies or session datas from the customer. it is important, that a customer say YES to cookies and you have to check this every time in every form, especially before the purchase is finalised. WB has some good helper-functions to include the data protection pages, see form and news-module
- to #2: means: a good text in your privacy police to give a description, what are you doing with the customer datas
- to #3 && #4: in my eyes, SSL is absolutely essential, never use a real ip-adress from a customer somewhere in the shop administration or database
if you work on your website with customer datas and you've a bigger company or shop (more the 9 People) or if you send's customer datas to another company (outsourcing), maybe for newsletter or invoice- && shipping-service, you need a special "data protection officer", declared in your privacy police.
some other important things:
there are also some other rule: every customer has the right, to see a order status and a order history and he can say everytime: pls delete my personal datas and delete my account, but you cannot delete the datas, if the tax office requires a complete presentation. The same for canceled orders. the old bakery works with the payment status: if the status say "cancelled", the script delete all datas from this invoice, but the (german) tax office dont accept this, you have to anonymised this datas)
The old bakery save the complete invoice with text, adress, prices etc. split this datas and use a separat customer adress database table and the order datas in another database table, seperated by customer-id. if now a customer say's delete my personal datas, change this datas, but dont delete it. All this is part of the customer account administration in the module
the old bakery add at first, if you add something to the basket, a data sheet with a invoice-id. if another customer come's in the same minute, he get the next id-number, but if somebody cancel his order, you've no order for this invoice-id and the script delete a empty order in the next 24 hours. Here you need a new method for identification, set the invoice-id as the last step in the order.
and some private words...
if you ask me, dont use the old code or parts from old bakery, separate code and output. it works fine with twig and templates. i add in my modules a template editor (edit area) and store the results in the database. i know, it is difficult, to change something in the module, if you use it also in a online store. i'm working since 2018 on a rebuild of the OneForAll-Module. OFA is a (code-)Mix between Bakery and News with some additional functions. I use the idea of OFA, but no part from the old code, i used this module online since 2018 to build lists with Time-controlled output in some projects, but it is not complete finish yet, maybe to 90%, there are only some small functions in the field type definition left, but it works for my projects and you've no pressure, to work on it

The same for a Bakery-Rebuild: there is no request for a minimized shop, everybody wants a "real shop system". So i use Wordpress && WooCommerce. Its a good working system and a good example for a own shop, but you spend a lot of time in this kind of module. I like to build something like this and i'm happy, to see, that its work and get bigger and bigger, but then, after a couple of mounths, i lost the interest. In the past I had a lot of health problems with numerous operations after an accident and every time afterwards you are out of the matter and lack the drive to carry on.
I hope you have more patience