Data Protection & Data Sovereignty
Clearly explained: where your data lives, who can access it, and what choice organisations really have when it comes to software.
Your Server, Your Data: Why the Hosting Location Is a Question of Principle
Where software runs determines who can access data and how easily you can leave again. What data sovereignty means in practice — and why "self-hosting" does not have to mean a server in the basement.
Your Own Instance Instead of a Big Platform: Run Separately, Stay Separate
Whether a thousand organisations share one installation or each gets its own is invisible — until something goes wrong. Why this architecture question is a question of trust.
The Data Processing Agreement: Who Processes Data for Whom — and When You Need One
Hardly any contract is demanded so often and understood so rarely. The roles behind Art. 28 GDPR sorted out properly — including the special case in which no DPA is needed at all.
Why "No US Cloud" Is More Than a Marketing Promise
A Frankfurt location sounds reassuring — what matters is whose law the operator is subject to. The CLOUD Act, Schrems II, and the services running along in the background, soberly assessed.
Rent, Buy, or Have It Built? What Software Models Cost in the Long Run
A small subscription looks harmless, a purchase price looks big — over five years, the picture often flips. Subscription, one-off licence, and custom development honestly compared.
Website or Web App? The Difference — and When You Need Which
One shows, the other works: what separates website and web app, when a website is entirely sufficient, and how organisations know it is time for a tool in the browser.
Why Software Needs Care — and What Happens Otherwise
Software does not wear out like a machine — and it ages nonetheless. Security gaps, shifting technology, and legal changes explained, with a realistic scope of maintenance and its costs.
GDPR for Practices, Associations and Law Firms: The Five Duties That Apply to Everyone
The GDPR does not kick in above a certain size. Responsibility, legal bases, information duties, data subject rights, and technology — the core in five understandable points.
Write to me.
I read every message personally and usually reply within 24 hours.
Message received.
Thank you – I will take care of it personally.
- 1
I read your message personally
No queue, no agency in between.
- 2
Reply by email – usually within 24 h
On weekdays usually much faster.
- 3
If you need one of my services
I will suggest concrete next steps by email.
Your reference no.: —