Here we would like to show you which personal data is processed directly in Shopware 6. As an eCommerce system, it is of course absolutely necessary to process customer data in order to record delivery addresses, for example. It's important to note that not only the software itself is involved in the processing, but also the hardware behind it. Since the setup of your hoster is highly individual, you should clarify with your hoster to what extent the communication takes place there (e.g. with a disjointed database server, where the application communicates with the database over a network). We will only focus on the software-sided processing of this data in Shopware 6.
This is intentionally kept very general for now. Shopware 6 itself stores a wide variety of data, which either have a direct reference (= personal) or no direct reference (= anonymized) to the user. Anonymized data is not personal data and does not fall under the GDPR, so no special measures need to be taken.
Pseudonymized data, which can be assigned to a person e.g. by means of a code number (e.g. bank details, a customer number or an order number) are again personal data, even if it is not instantly recognizable who the person is.
Personal data is always required when Shopware 6 accepts a customer input or when the store operator has to work with this data. This can be the registration or review function in the front end, but also the processing of orders through the back end. Of course personal data can also be retrieved over the RestAPI with authorization. In addition, anonymized data is also collected in order to be able to play out article recommendations ("customers also bought", "customers also looked at", ...) and statistics in the backend. Since you can easily lose track of the countless functions of Shopware 6, we hereby list the data that is stored in Shopware.
This list may be incomplete. Plugins are able to extend the data storage and Shopware 6 extensively. You must evaluate whether you process further personal data individually in your Shop!
The European Commission defines personal data as:
Personal data is any information that relates to an identified or identifiable living individual. Different pieces of information, which collected together can lead to the identification of a particular person, also constitute personal data.
Personal data that has been de-identified, encrypted or pseudonymised but can be used to re-identify a person remains personal data and falls within the scope of the GDPR.
Personal data that has been rendered anonymous in such a way that the individual is not or no longer identifiable is no longer considered personal data. For data to be truly anonymised, the anonymisation must be irreversible.
The GDPR protects personal data regardless of the technology used for processing that data – it’s technology neutral and applies to both automated and manual processing, provided the data is organised in accordance with pre-defined criteria (for example alphabetical order). It also doesn’t matter how the data is stored – in an IT system, through video surveillance, or on paper; in all cases, personal data is subject to the protection requirements set out in the GDPR.
The customer can setup a customer account in order to use more functions than just placing a order. This contains, among other things, the address , but also other personal information, depending on what you have configured in your settings. It's possible to request the date of birth, as well as the company name. Here you should specifically check the registration of your store to get an overview of the data you collect from the customer. In the database of Shopware 6 all tables containing customer data start with the abbreviation "customer*". But you can also view this data in the admin, by opening the respective customer under Customers > Overview.
The heart of every online store is of course the checkout. To place an order in Shopware, has the option to register a customer account, or to continue without one. In both ways the customer will hand out the billing information. All this information is being stored combined in the order. In addition, the products that the customer purchases in your store and the customer's IP address are stored. In addition, the referrer - the source through which the customer reached your store - is also stored. You can view all relevant information in the admin under Orders > Overview and in the database in the tables with the abbreviation "order*"
As mentioned above, IP addresses are stored for individual orders. In addition, you will find a list of areas where an IP address is stored in this document: Which IP addresses are stored?
Like many other systems, Shopware 6 offers a newsletter registration function. Here, for example, the form can be found in the footer of the store or in the user account of the customer. A documentation of the newsletter and which data is collected here can be found here: Newsletter
All information that the customer deposits in the frontend can be found in the Shopware Admin in the area "Marketing > Newsletter Recipients. In the database the table newsletter_recipient is used to store the data.
On the article detail page Shopware provides the possibility to give a product review. A review can only be submitted when the customer is logged in, and is therefore linked to the customer account. You can view, delete or release the given reviews in the backend under Catalogs > Reviews. Here you can find a documentation about the rating function in Shopware: Reviews
The admin interface is special this area. Here you can not only view and create customer records, but also administration users, which are linked to an e-mail address. So the admin does not only process the data of the customers in your store, but also to a certain extent the data of your employees. You can configure the user management of the backend under Settings > User Management. There is also the possibility to restrict individual areas of the backend or to allow read-only access. A documentation about rights and roles in the backend can be found here: User administration
If you have connected further systems, such as an ERP, it will communicate with the store. This happens either through an installed plugin or the API. The users of the API are usually created in the administration. Here you will find a list of data that you can get using the Rest-API: API
The encrypted transmission of data is usually done using the HTTPs protocol. To use this in your store, you first need a valid SSL certificate, which has to be installed on your server. Afterwards you can use the SSL encryption for your store by assigning an HTTPS domain to the sales channel.
Here you have to differentiate between encrypted data transfer and encrypted storage. We generally recommend to operate the store using HTTPs, so that all personal data is transmitted encrypted over HTTPs. The storage of this data is then done in the respective database tables. The data itself is only encrypted if this is necessary, e.g. the user password.
Whether or not the setting of cookies, which are not technically necessary for the operation of the store, requires an opt-in is a matter of dispute between lawyers. We recommend implementing at least one of the established solutions for data protection information on cookies. You can find more information about this at www.cookiechoices.org; please consult your legal advisor.
Shopware itself provides the possibility to activate the cookie hint by default.
Shopware stores cookies in the visitor's browser to ensure the basic functions of the store. The cookies are used, for example, to determine the contents of the shopping cart, the login status and also the CSRF protection. Without having enabled cookies in the browser, Shopware cannot be used. IMPORTANT: Shopware always stores only IDs in the customer's browser, the assignment to the respective information is done in the application area.
Based on the session cookie, Shopware decides whether the respective user has an active shopping cart and whether the user is logged in. It serves as identification between browser and server. No further information except the session ID is stored in the browser. The handling of sessions is controlled by PHP on the server side and can be viewed independently of Shopware.
On top of that, Shopware generates an individual CSRF cookie when the customer visits the store, so that the customer can access the individual areas of the store. Here you can find information about CSRF protection: CSRF-Protection
IP addresses are stored in the Shopware by default. This serves for the unique identification of the user in the store. Shopware stores the IP addresses by default in four places.
In every order the IP address of the customer is stored. By default this is not displayed or used in the admin. It's stored in the database table order_customer.
The IP address of the last order is stored in the customer table. By default this is not displayed or used in the admin.
In the table log_entry all activities of backend users are stored. With the help of this table it is possible to track when changes have been made, for example. You can then assign them to a person based on their IP address.
The database table version_commit_data stores data about the current usage. Here, for example, necessary data is stored that is needed while an order is being processed. The IP address of visitors and customers is also stored here.
Here you can find the documentation for the shopping experience in Shopware: Shopping experience
By default, Shopware does not transfer information to third parties. Extensions can of course change this. For example, if you use PayPal in your store, data from the store (the delivery address, the order amount and the shopping cart) will be transferred to PayPal. There are of course many other service providers that process data from Shopware, if you use such an extension in your store. Prominent examples are payment providers, ERP systems and also newsletter service providers. To find out which data is transferred to third parties, please ask the manufacturer of the respective extension.
The GDPR stipulates that a customer is provided with structured data concerning him/her by the store operator upon request. For this purpose Shopware offers the import/export function which allows you to export all relevant data of a customer. Please note that depending on the registration of the customer (quick order or customer account) more than one customer account may exist. A documentation about the export options (CSV and XML) can be found here: Import / Export
The database also offers the possibility of outputting information about a customer by using an SQL-Query. All customer-specific data is located in the tables that begin with customer*.
All data defined in this document can usually be deleted comfortably through the Shopware Admin. If a customer wants you to delete all personal data, you can delete this data by using the customer module in the admin. The respective links are automatically removed. You can also remove the recipient from the recipient list using the newsletter module. Shopware offers the possibility to remove all personal data through the admin on customer request. Whether and when you are obliged to delete customer data is a legal question that you should clarify with your legal counsel. Unfortunately, it is not possible to make general statements about this.
For some time now, we at Shopware have been working with the well-known certification bodies to ensure that the system meets the requirements of the GDPR. In the process, it has turned out that, according to our current state of knowledge, Shopware provides store operators with the functions they need to make the necessary settings required by the rules of the GDPR. For example, Shopware already provides all necessary tools in the regular end-user documentation, e.g. also to remove personal data from the system, which is a core requirement of the new basic data protection regulation. A special plugin/update is not planned with regard to the GDPR.
Should the need arise to adapt our software, we will of course provide an appropriate adaptation per update.
The Footer Navigation shows the categories you select in the sales channel configuration for this purpose.
Under Catalogs > Categories you can add a sub category below the category you have chosen as entry point for the footer navigation. Below that, you add another sub category and name it Privacy, for example.
In the category configuration of the category Privacy you then select the layout Privacy from the Shopping experience in the Layout assignment section. If you now activate the Privacy category and all categories above this category, the menu item Privacy will be displayed in the footer menu.