Skip to content
CTG GmbH
A person behind a screen representing privacy

Privacy: protect personal space deliberately

Privacy creates room for personal decisions, confidential communication and private life. It matters at work too. An employee, customer or applicant should be able to understand what becomes known about them and how personal information is used.

Protection starts when a process is designed. What information is genuinely needed? Who can see it? Could the task be completed with less insight into someone’s life? These questions connect personal space, data handling and technical choices.

More than individual data records

Privacy and data protection are closely related but have different perspectives. Privacy includes personal life, communication and the ability to withdraw. Data protection governs the handling of information about people. The Charter of Fundamental Rights of the European Union addresses private and family life in Article 7 and personal data in Article 8. Article 7, Article 8.

Both perspectives arise in everyday meetings and digital tools. Screen sharing can unintentionally reveal a private message. A shared calendar can expose more personal detail than scheduling needs. Settings and habits that appear minor therefore deserve attention.

What we examine

The purpose of processing, necessary information and recipients are central. Retention periods, access rights and external suppliers matter too. Linking data can produce additional insights: one entry may reveal little, while many combined entries create a detailed picture of a person.

The General Data Protection Regulation (GDPR) provides useful principles. Personal data should serve clear purposes, be limited to what is necessary and be retained only as long as needed. Understandable information and appropriate safeguards are also required. The European Data Protection Board (EDPB) explains these connections in its small-business guide.

The correct legal basis must also be identified. Performance of a contract or a legal obligation may apply, depending on the processing. Where consent is used, it must meet the relevant requirements; a notice or preselected checkbox alone is insufficient. EDPB: lawful processing and consent

Current framework

Data protection by design and by default forms part of the GDPR. An EDPB summary published in February 2026 explains that appropriate safeguards should be planned when selecting a method and reviewed throughout its use. Design and defaults

In Germany, section 25 of the Telecommunications Digital Services Data Protection Act (TDDDG) also protects privacy on terminal equipment. Storing information on a device or accessing information already stored there generally requires informed consent. The Act provides narrowly defined exceptions, including certain operations strictly necessary for a digital service explicitly requested by the user. Websites and applications therefore need an accurate understanding of what their technology actually does. TDDDG, section 25

Applying privacy in practice

Before introducing a meeting service, establish what information participation requires, what records are produced and who can start a recording. Privacy-friendly defaults can avoid unnecessary recordings and limit access. Clear information should then explain the actual arrangements.

A contact form is another example. An initial enquiry often needs fewer details than subsequent contract processing. Separating those stages makes the first step simpler and explains why more information may be needed later.

A practical starting point

Choose an everyday process involving personal information. Describe what information arises, who receives it and when it is removed. Check which details can be omitted, which access rights are necessary and whether the people concerned can understand the process.

Privacy adds the consequences for individuals to legal and technical assessments. Explore data protection, security and regulation.

Information date: 6 November 2026.

Knowledge and practice overview