we will use deepl autotranslate. But we need a GDPR ready solution for a german costumer. Is the solution GDPR ready? Or if not, how can we block the connection to deepl wile using borlabs cookies?
before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.
The translation is a process done in the Backend, this is nothing you can block with a consent tool such as Borlabs, as this is not handled via a Frontend cookie (like YouTube or any social media embed). The translation is already done, saved, reviewed by you and published before the client can see the translation.
No data is loaded directly from a DeepL server once the request was made. It's always loaded like any other post content, directly from your own database.
Best Regards
Marcel
The topic ‘[Closed] WPML Deepl Autotranslate GDPR ready?’ is closed to new replies.