Privacy Policy Kit

The dynamic “Privacy policy kit” function can be used on function detail pages of the “Dataprotection” type. To do this, it must be dragged and dropped from the new dialog to the desired location on the page.

The texts configured in the module are then displayed as a list and can be selected or deselected by the user.

In addition to the predefined texts, containers can also be made available as building blocks at any point in the privacy policy, in which editors can maintain individual content such as the contact details of a data protection officer or additional information. The data protection cookie switch can also be displayed at any point.

This function can also be used to create function detail pages of the “Imprint” or "Accessibility Statement" type. Other text modules with customized content can be used for this purpose.

The text modules for the privacy policy are not part of the installation and must first be provided by the legal department and stored by the administration in OpenCms. 

The text modules and their configuration must be stored and maintained in a central location. This requires a separate subsitemap folder in the /shared/policykit/ directory. The use of a sub-sitemap makes it easier to create and retrieve the text modules in the Explorer app.

To illustrate this function, sample texts may be included in the /shared/policykit folder in new installations. Alkacon accepts no responsibility for their content or legal validity.

A separate content section must be created for each text module that can later be selected in the privacy policy.

A new content section can be created using the “Create resource” dialog in Explorer. Please note that you must be in the desired subsitemap directory - e.g., under /shared/policykit/ - and that the “Use default location” option is activated in the dialog.

First, create a content section for each required block, e.g., in the .content/section-m/ subfolder of the configured subsitemap, and edit its content.

Use of individual content

At certain points in the privacy policy, editors can add and edit individual content, such as the contact details of the data protection officer or other texts.

To do this, a container is displayed in the page editor at the desired location, into which any content can be dragged and dropped. This can be content sections, organizations, people, or other content elements.

Use of links or macros in content sections

It is possible to set links to other pages in the content sections. However, if these links are to lead to other function detail pages of the current (sub)site, the link target must be entered in the form “opencms://function@...”. For example, to set a link to the data protection page, the link target is “opencms://function@Datenschutz”.

Macros can be used to customize text passages, e.g., where the name of the data protection officer must be displayed. These are resolved in such a way that the values are read from sitemap attributes. For example, to set the name of the data protection officer in the text with a macro, enter “%(attribute:policy.dataprotectionofficer.name)” in the text instead of the name.

In order for the macro to be resolved correctly, an attribute with the key “policy.dataprotectionofficer.name” must be configured in the sitemap configuration of the site where the construction kit is used, with the name of the data protection officer as its value.

You can use any macros you like, but you must ensure that values are always stored for them in the sitemap configurations.

Important: Macros are suitable as placeholders for names or other short terms. If longer individual content is to be displayed at specific points, container modules as described above must be used instead of macros.

After creating the content sections, a new file of the type “Configuration for Privacy policy kit” must be created directly in the subsitemap folder. This type can be found in the New dialog under “Configurations.” Name the file, e.g., “privacy.xml.”

Then edit the file. Assign a title for the configuration, e.g., “Data Protection”, "Imprint" or "Accessibility Statement". This title can later be optionally displayed on the page via the dynamic function's element setting.

Then add as many “building block” elements as you like to your configuration in the editor. Each building block has the following fields:

• Type: There are three different types of modules to choose from::
  • Text module: This module type is used to output predefined texts. It outputs the text of a content section referenced in the “Path” field.
  • Container: This type allows you to add and edit individual content via drag & drop. It generates a container in which an editor can insert, for example, the contact details of the data protection officer.
  • Data protection cookie switch: This type displays the data protection cookie switch as generated by the dynamic function of the same name. A building block of this type should only appear once in the entire configuration.
• Title: The title of the module is used by the editor when selecting the modules to be displayed.
• Description: An optional more detailed description of the module. This is displayed like the title when selecting modules.
• Path: The path to a content section that contains the text for the module.
• Mandatory: By checking this box, you can prevent an editor from deselecting this module when selecting modules. It will therefore always be visible.
• ID: Technically required internal field that is set automatically and cannot be edited.

Once configuration is complete, its path must be set for use with the dynamic “Privacy Policy Kit” function either in the Tenants App  or as a sitemap attribute for the sites that are to use this function.

If necessary, configuration paths set for specific subsites in the sitemap configuration can be overwritten with the Tenants App.

For the sitemap configuration, an attribute with the key “policy.config.Datenschutz.file” must be created. The value is the absolute path to the configuration file, e.g., “/shared/policykit/policy.xml.”

If different sites are to have different options, multiple configurations can be created for the privacy policy. In this case, the sitemap attribute “policy.config.Datenschutz.file” can be set to control which configuration is to be used. The different configurations can use the same or different text modules.

The “Privacy Policy Kit” function can also be used to create an imprint from predefined text modules.

To link to the configuration, the sitemap attribute “policy.config.Impressum.file” must be used. The “Privacy Policy Kit” function can then be used on function detail pages of the “Imprint” type.

The configuration is set up and the text modules are created using the same procedure as described above.

The “Privacy Policy Kit” function can also be used to create an accessibility statement from predefined text modules.

The setup is similar to that for the imprint (see above), but “policy.config.Barrierefreiheit.file” has to be used as the sitemap attribute. This allows the “Privacy Policy Kit” to be used on function detail pages of the “Accessibility” type.  

The setup of the configuration and the creation of text modules follow the same procedure as described above.