Customer data in AI systems, a website without a cookie banner, analytics without Google – what works and what to settle first.
When a contact counts as inactive, what a reactivation looks like that does not read as desperation, and when deleting is required.
Three alternatives compared — server logs, consent-free analytics services and self-hosted solutions — with what each one gains and gives up.
The distinction between provider and deployer, which marketing applications fall into which risk class, and the four real obligations.
How duplicates arise, which rules govern merging, what can get lost in the process — and how to stop them coming back.
What belongs in an AI policy, what expressly does not, and why one page achieves more than a twenty-page rulebook — with a complete outline to adopt.
When a consent banner is legally required, what measurement remains possible without consent, and what you actually give up.
Permissions, logging, scope and the handling of injected instructions — the six questions that have to be answered before the first connection.
Three questions decide whether personal data may go into an AI system: contract, place of processing, and use for training.
The differences between the revised Swiss Act and the GDPR, and the six points a Swiss business website has to have settled.
MCP is the open standard through which AI systems access your own data and tools. How it differs from a normal interface, and what to settle first.
