Guide

Content creation and privacy: what GDPR requires

As soon as personal data is processed in content creation, clear obligations apply. What these are specifically, what is almost always missing in practice and what actually suffices.

Quote on requestongoing, typically 2 to 4 posts per monthStatus 2026
In short

As soon as personal data is processed in content creation, you need a legal basis, purpose limitation, defined deletion periods, information for data subjects and a data processing agreement with every involved service provider. In practice, the same three points are almost always missing: the deletion period, the notice at the point of collection and clarification of whether the provider uses the data for its own training.

01 — Data Protection

What GDPR requires

As soon as personal data is processed — and that happens faster than expected, for instance as soon as someone enters a name or phone number — the usual obligations apply: name the legal basis, define the purpose, maintain data minimization, define retention periods, inform data subjects.

Practically, this means for content creation: a data processing agreement with every involved service provider, checking where processing takes place, a documented deletion period and a clear section in the privacy policy. Three things are almost always missing in practice: the defined deletion period, the notice at the point where the data is collected, and clarification of whether the provider uses the data for its own training.

A data protection impact assessment is only required when there's likely high risk — not for most projects of this type. The review itself should still be documented so that if questions arise, it's clear why it was omitted.

02 — Contract

What needs to be clarified in writing

  • Ownership of data and access. They belong to the client. If a provider won't clearly confirm this, that's the most important information from the conversation.
  • Handover upon termination. In what format, within what timeframe, at what cost.
  • No minimum term without consideration. Lock-in is justifiable if something is delivered in return — otherwise not.
  • What a later change costs. The total cost isn't determined by the project price, but by the hourly rate in year three.
  • Documentation as a deliverable. Not as a promise, but as a line item in the proposal.

03 — Risks

What can go wrong

  • The system answers incorrectly. Containable by having it work exclusively from verified content and escalate when uncertain rather than guess. This is a configuration decision, not a property of the technology.
  • The effort is underestimated. Most common reason: unclear starting situation. An honest assessment of the current state before the proposal prevents this more reliably than any buffer.
  • No one maintains it. The biggest risk of all — and the most easily avoidable.
  • Data protection gaps. Almost always arise from missing deletion deadlines and unclear responsibility, rarely from the technology itself.
  • Vendor lock-in. Avoidable if access credentials, data, and documentation contractually remain with the client.

04 — Questions

Frequently asked questions

What about outdated posts?

Update instead of rewriting. A revised post with existing history is almost always more effective than a new one on the same topic.

Do you write that with AI?

We use AI where it helps — structuring research, drafts, variations. The core of every text comes from a professional conversation with you, and every text is revised and checked by a human. Purely machine-generated texts without original knowledge rank poorly and read even worse.

How many posts do we need?

Better two good ones a month than eight thin ones. Search engines now evaluate more clearly by substance; one page that answers a question completely beats five that say the same thing halfway.

Who decides what to write about?

Together, based on two sources: what search engine users actually ask, and what your sales team constantly has to explain. Both together produce the topic list.

What if our specialist knowledge changes quickly?

Then we mark posts with an update date and agree on the rhythm for reviewing them — that's cheaper than rewriting every time.

How long does it take for content to work?

Three to six months for the first positions, longer for competitive topics. Posts on very specific questions often work faster because there's less competition there.

Do we get the texts as raw files too?

Yes, in a common format that you can reuse or adapt yourself. The content belongs to you, regardless of whether we also integrate the page technically.

Next step

We'll look at your starting position.

Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.