Expert insights on AI traffic, content monetization, and GDPR compliance for publishers.
robots.txt only ever controlled whether a crawler visits. A newer, separate declaration answers a different question: what may it do with what it reads? Here's the EU copyright mechanism behind it — and why 'declare' is the accurate word, not 'block'.
A crawler-control recommendation that only lists the bots already in your logs is incomplete by design. Here is why we recommend an explicit rule for every AI crawler we track — including the ones that have not visited yet.
Our compliance log that tracks account changes now stores only hashed identifiers. The change advances GDPR Article 5(1)(c) data minimization without compromising row-continuity needed for Polish 5-year tax retention obligations.
Before any destructive change to our compliance trail database, an automated verification pass confirms the operation will not lose audit-trail integrity. The pattern caught a real divergence this session and prevented data loss.
When privacy notices, marketing pages, PDF DPAs, and the live service all reference the same retention periods and processing limits, drift between them is a real misleading-claim risk under EU consumer-protection law. Here is how HumanKey closes that class of drift mechanically.
An operator-side update on the review pattern we use to keep our customer-facing surfaces consistent. We publish the methodology — not the findings — and explain why.
What we learned after 90 days of running an AI-transparency banner under EU AI Act Article 50: what we measured, where the wording was harder than the engineering, and what we'd change.
The EU AI Act becomes fully applicable in August 2026 with strict transparency obligations. Here's what website owners need to understand about AI crawler compliance and content rights.