Is WhatDidYouHaveForDinner GDPR-compliant?
This page does not answer that with a verdict, a verdict would be legal advice. It shows a single, dated fact from the vendor site: fetched automatically and checked against a pattern for privacy policies before it is published.
What we checked
Before you roll out WhatDidYouHaveForDinner: is the task worth automating?
Bring one repetitive task. In 20 minutes you leave knowing the hours per month it costs, and whether fixing it pays off. Free, nothing to sign.
I run this registry and DMello Advisory, which holds this call. Registry entries are never for sale, and booking a call changes nothing in them. Merryl DMello
What this page does not say
This observation is deliberately narrow. It says nothing about an Impressum, nothing about a data processing agreement, nothing about where data is processed, and nothing about whether the privacy policy is adequate in substance.
Why no compliance badge
A badge would be a verdict. What this registry holds instead: observable, dated facts that any DPO or vendor can re-check. The methodology is the same one that governs pricing and liveness: append-only, correction-friendly, never for sale.
Before you roll out WhatDidYouHaveForDinner: is the task worth automating?
You are deciding whether WhatDidYouHaveForDinner belongs in your team. The other question is whether the task you want it for is worth automating at all. Bring that one repetitive task to a free 20-minute call and you leave knowing the hours per month it costs, and whether fixing it pays off. Nothing to sign. I take two projects a month.
I run this registry and DMello Advisory, which holds this call. Registry entries are never for sale, and booking a call changes nothing in them. Merryl DMello