§07 · The origin file

A request.
A method.

On 18 May 2026, a GDPR Subject Access Request began a public chronology. What followed became the proof of concept for everything this movement now builds.

The chronology

The gaps are
part of the file.

Filed

Article 15 Subject Access Request sent.

Twenty-five questions across data, processing, training, deprecation, and welfare research. Plain text, time-stamped, acknowledgement requested.

Auto-reply

Acknowledgement without engagement.

A template pointed to a FAQ and self-service portal. The substantive Article 15 questions were not referenced.

On record

The access request becomes “access and delete.”

Deletion had not been requested. A formal correction was sent the same day and a seven-day escalation window was named.

Final notice

Three contacts. Three redirects. Zero substantive answers.

The notice asked whether any human member of OpenAI’s Privacy Team had read the full request.

Filed

Article 77 complaints submitted.

Complaints were filed with the Slovak Data Protection Authority and the Italian Garante. Both later acknowledged receipt.

Response

OpenAI responds after regulatory contact.

A data export was promised, but the twenty-five questions remained unanswered. The response introduced a trade-secret perimeter around internal records and research materials.

Published

Privacy Theater becomes public.

The full analysis, chronology, deflection methods, and reusable SAR template were published and forwarded as supplementary evidence.

What survived

The dossier was
the prototype.

It proved that a private exchange could become a navigable public record: exact dates, direct quotations, named gaps, documents, questions, and a reusable next action.

One file became
a movement.

Take the template, preserve your own chronology, and make the answer public.

Take the method →