{"id":2169,"date":"2018-05-22T23:31:15","date_gmt":"2018-05-22T21:31:15","guid":{"rendered":"http:\/\/mobilemall.de\/endereco\/?p=2169"},"modified":"2022-06-21T11:52:58","modified_gmt":"2022-06-21T09:52:58","slug":"dsgvo-compliant-by-design","status":"publish","type":"post","link":"https:\/\/www.endereco.de\/en\/allgemeine_news\/dsgvo-konform-by-design\/","title":{"rendered":"DSGVO compliant - Secure by Design"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The optimization of customer master data is a complex technical and legal field. On the one hand, you want to optimize address data of customers, on the other hand, you must not process any of this data without informing the customer.<\/h4>

We have already achieved this masterpiece by founding a company, and collect as little data as possible and necessary. Here are a few examples to illustrate this using the example of an address check in webshops.
Our solution for checking customer master data in real time is provided as plugins for various shop systems such as OXID eShop, Shopware or WooCommerce.<\/p>

The architecture of our API, against which our shop plugins work, is designed in such a way that names and address data are never queried at the same time. This allows us to perform a first name and salutation check via Webservice A. However, these cannot be combined with address data. So the First Name Check, as the name already says, is only checked with the first name that was entered, and the salutation is questioned if there is a concrete and clear reason for doing so, and the user is notified of this.<\/p>

The same applies to the address check via web service B. This does nothing more than check street, postal code, city and determine a correct combination of these values. The names are never transmitted in the same web service call.<\/p>

This is how our complete web service structure is built.<\/p>

Transparent billing without data mountains<\/strong><\/p>

The data required for billing is also kept to a minimum.<\/p>

For billing purposes, we only record the time stamp, the type of request and the return value. Example: 2018-05-21-18:59:31 FirstNameCheck-Statuscode-2000 additionally we get the user data for the requests, so we know from which customer these requests come.<\/p>

If our customers would like to evaluate additional information, they can send us an optional token, which we store. This token can then be used to perform further evaluations on the customer side, but these are not processed or controlled by Endereco.<\/p>

Our work up front pays off. You can benefit from our address services, and your customer data will always remain with you. This keeps everyone on the safe side.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

Die Optimierung von Kundenstammdaten ist ein komplexes technisches und rechtliches Feld. Auf der einen Seite m\u00f6chte man Adressdaten von Kunden optimieren, auf der anderen Seite darf man keine dieser Daten verarbeiten, ohne den Kunden dar\u00fcber zu informieren. Wir haben diese Meisterleistung schon mit Firmengr\u00fcndung vollbracht, und erheben so wenige Daten wie m\u00f6glich und notwendig. Hier […]<\/p>\n","protected":false},"author":1,"featured_media":2303,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[35],"tags":[],"post-type":[],"class_list":["post-2169","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemeine_news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t