Skip navigation

"privacy policy" and "detailed privacy policy" could use a few optimizations for the use in the company context and for the better preparation of the content

score 10
You have not voted. New

At the latest after the many scandals data protection is on everyone's lips. The preparation and display should take this into account.

The two areas "privacy policy" and "detailed privacy policy" could use a few optimizations - for the use in the company context and for the better preparation of the contents.

 

privacy policy

As a large public company, we need to educate our users about data protection. However, the user does not have to agree to this separately.
A personal confirmation is not planned and in the company context usually not helpful, because there is no alternative in case of rejection.

 

Textual adaptation can be important for users. Currently there is no possibility to display the privacy policy again. Once confirmed, the box always remains invisible.

 

  • 1. Optimization: The forced confirmation should be optionally configurable, i.e. with or without force.
  • 2. Optimization: Configurable re-display of the privacy Policy (for admin users)

 

detailed privacy policy

It would be helpful if you could format the detailed information in a RTF field. You are addressing end users and nobody wants to have to read a longer text without optical structuring. Of course, you can fake this with HTML tags, but does an employee responsible for data protection have to be an HTML expert? I think: no. With lots of HTML tags the text becomes unreadable too.

 

The access to the detailed description should be independent of the activation of the privacy policy. Both are not necessarily related (see privacy policy section).

 

  • 3. Optimization: An RTF field would be better than a pure text field
  • 4. Optimization: Offer link to detailed description as soon as it contains text.

 

Comments

Vote history