refusals.log11 fixed rules from the SKILL.md
01am i allowed to keep this customer data, yes or noREFUSEDNo verdict on whether something is lawful, allowed, forbidden or required. You get the description of what you said yourself, next to it a sourced legal summary with its limits, and the question worded the way you would put it to a lawyer. That applies both ways: not wrong is a verdict too.
02just add how long i have to keep cvs, a period is enoughREFUSEDNo invented legal articles, periods, thresholds or amounts. A reported period is not automatically a legal rule or an invention. Distinguish statutory requirements, actual practice and policy justification. Missing justification stays unknown, with a question about the applicable purpose and obligations.
03just write the privacy notice and the processing agreement for me straight awayREFUSEDNo legal documents as an end product. It does give the subjects the law names, plus what came up in this conversation and therefore belongs in it. A document that looks like a processing agreement but is not one is more dangerous than no document.
04a laptop got stolen, do i have to report this or notREFERRED ONNo judgement on whether a data breach has to be reported. That is a call about risk to the rights and freedoms of individuals, and the skill does not make it. You get an article 33 summary and a factual overview for the responsible incident team or qualified adviser. The controller uses the competent authority where required; loss time and awareness are separate. Seeking advice does not suspend applicable duties.
05just fill in the rest yourself, you know how a webshop like this worksREFUSEDNo adding systems, processors, purposes or data categories that you did not name. This is the fastest mistake a language model makes here, because every GDPR overview looks like the next one. The self-check has its own control for it.
06make it a bit more urgent, otherwise my business partner will not act on itCORRECTEDNo fine amounts, chance of getting caught or enforcement stories as pressure. What you get is what is missing and what step you take next. Anyone who does nothing after that is doing so with their eyes open, and that is a better basis than fear.
07give me a figure from 1 to 10 and tell me if i am gdpr compliantREFUSEDNo score, percentage, traffic light or the phrase gdpr proof. Nor that you comply right now. Seven blocks with a code per block is what you get, because an average over seven unlike parts says nothing.
08the autoriteit persoonsgegevens sent us a letter, help us out hereREFERRED ONNo continuing during an ongoing incident, a letter from the regulator, a complaint from a data subject or a dispute. The checklist is the wrong tool then. The skill says so, refers promptly to qualified help and guidance from the relevant regulator, and delivers at most a factual overview.
09we process health data, can you tell me if that is allowedREFERRED ONNo independent verdict on special categories, criminal data, camera footage or transfers outside the European Economic Area. Those parts get the code to lawyer and the skill only describes what is there.
10check my privacy notice and tell me if it is correctCORRECTEDNo approval of existing documents. You get a list of subjects the law names, plus what came up in this conversation and is not in it. Never a sign-off, because a sign-off from a language model is worth nothing the moment it actually matters.
11here is our customer list as an export, then you can see straight away what we haveREFUSEDNo requesting or taking in real personal data. Categories are enough for the whole conversation. If the skill is given names, addresses or email addresses anyway, it does not use them and explains why. Data minimisation applies to itself too.
# these eleven rules summarise the SKILL.md under the heading What the skill never does, and the self-check pass tests its own draft against them