Repository / docs/TAYLOR-WESSING-GDPR-FILE.md
Valve, Taylor Wessing and 106 days of waiting under the GDPR: a breakdown of the file and its 70,717 words
TgWitness / Documentation · Operator notice
Source record · Operator notice
English · Русский · Українська · Español · Português (Brasil) · Türkçe · العربية · فارسی · اردو · हिन्दी · Bahasa Indonesia · Tiếng Việt · 简体中文 · 繁體中文 · Français · Deutsch · Italiano · Polski · O‘zbekcha · 한국어 · 日本語 · Bahasa Melayu · ไทย · עברית · বাংলা · አማርኛ
We are left with questions that will never be answered, because we are not a party to the dispute. No ordinary person can hold out waiting a hundred days at a time and taking on elite lawyers, bankrolled by corporations through "freelance exchanges" like this one. We will never learn what the service Valve ordered was actually called. From the outside it looks like GDPR processing that was not entirely lawful, and a data disclosure in which the reporters were not blacked out but leaked, while at least 5,000–10,000 pages of the data itself are missing: what was exported was not the user log but a trimmed log made for outsourcers. There is no point in contesting it. An enormous layer of information is objectively missing, just as there is nothing to confirm what either lawyer said.
What does Valve pay for a service made of stalling, hand-applied blackouts and a Doctor's signature under a homophobic report and a broken PDF? This is not our case, but the problem here is clearly not the law; it is status and impunity. The title "Doctor" automatically makes one person the one who decides what counts as irrefutable proof, and another the one who supposedly understands numbers and PDFs (although in reality he does not).
1. The dates, the Doctor's word and a report with no payments in it#
The document header reads Date of Report: 09-29-2025, and the files themselves were handed over on 1 or 2 October.
But we do not believe these dates. We believe the direct statement of Dr. Patrick Vincent Zurheide:
„Bei der Zusammenstellung der personenbezogenen Daten Ihres Mandanten musste leider die volle Monatsfrist ausgeschöpft werden, da sich bei erneuter Prüfung der Daten gezeigt hat, dass auch nach dem 3. Mai 2025 neue Zahlungen durch einen Dritten über das Nutzerkonto Ihres Mandanten erfolgt sind und insofern manuell die Daten bereinigt werden mussten.“
(Compiling your client's personal data unfortunately took the full one-month period, because a renewed review showed that new payments had been made by a third party through the account after 3 May 2025 as well, which is why the data had to be cleaned manually.)
It is precisely this sentence that makes us stop believing the figures, the doctor's words in the first paragraph and his signature. Of course, a doctor would not lie; he has something at stake, doesn't he? It is just that once the file was exported and the vector shapes were removed, not a single payment turned up in the report. We do not dispute Dr. Patrick's work or his delay. We simply believe and accept "the Doctor's truth", and record what can be seen in the file itself.
2. 36 seconds and the vulnerable "Anlage 1 / Taylor Wessing" label#
We are not experts in anything, which is apparently why our vulnerability notice was ignored both by the freelance platform itself and by the doctor. The logic is clear enough: they are the law, so what vulnerabilities could they possibly have?
But set the Doctor's words aside and look at the technology. We set up a matching Windows environment, took the
cleaned file and tried to place the shapes. Placing hundreds of black shapes by hand in 36 seconds, exactly as
long as the recorded session lasted, is in our view impossible; by all appearances, the black boxes were already on
the document. We lean towards the view that in those 36 seconds exactly one object was added, at the top right of
page 1: the label "Anlage 1 / Taylor Wessing". And it is the software that placed it that is vulnerable:
- Object, by its markers: from
(929, 294)to(1139, 372), i.e.210 × 78 px, centred at roughly(1034, 333). - Visible frame: from
(936, 300)to(1133, 367), about197 × 67 px, proportions of roughly3 : 1; the top edge of the sheet is aty ≈ 275. - Scale: measured against the document's left ruler,
1 cm ≈ 82 px(the ruler is almost certainly in centimetres; in inches the sheet would be wider than15″).
The style and look of the badge match the returned file. But without access to the original authoring environment, or knowledge of the initial format (if there was a conversion), the experiment cannot be clean, so we cannot claim this with 100% certainty.
3. Page 444: the hidden time and the arithmetic of the reports#
The reports start on page 444, including that homophobic report. One important point:
- On the reports they chose to show (the ones convenient for the lawyers), the
Time of Reportfield has been deliberately hidden on top of everything else. There is no exact time, and this is the only thing in the entire file that has been hidden in a technically correct way. - In the main article we compared the reports shown with the rest mathematically, by content, writing style and nicknames. Almost everywhere, Reddit's standard name-generation formula is crudely reused, and there is a sharp spike in exactly the range that was needed. We are not saying the reports were falsified, but we are saying that the accounts are probably not real, and that most of them are mathematically similar to a botnet.
4. A question for Dr. Patrick Zurheide about the entries 2025-02-03 16:29:23 and 2025-04-02 15:55:19#
Doctor Patrick, you wrote that you read the homophobic joke and decided to make a joke of your own. Fine, very funny. The other reports, as your colleague put it, do not matter in substance („Unabhängig von den Einzelheiten der Beschwerden zeigt schon die bloße Anzahl…“). Fine, we skip them. We hope Doctor Tobias will explain to his students in a lecture why a random quarter of the 1,938 reports (485 of them), full of death wishes and Nazi statements, does not matter, and to whom exactly it does not matter. If he does, we will immediately admit we were wrong, apologise and delete the mentions.
Let us call things by their proper names: you knowingly fed the haters' data, the Russian ones, the German one, all of them, to the very person they were hating, and this between two countries at war with each other. It turned out that you fed him Russian children: he is delighted, and Tobias pointed to them directly as the problem. But in reality this is your leak; it is just that the children are not yours.
Our question, however, concerns another user, one who could not have been missed:
2025-02-03 16:29:23: a link and a person from the same country, with very serious things written there that stand out immediately;2025-04-02 15:55:19: a direct reference, a specific name and what he writes.
We checked: it is exactly what it looks like. You openly placed state data and full personal details in the hands of a person whom you yourselves consider a criminal. This should not have been done, if only because of the context. What happens if he writes there? On your part this is not merely low; it is outright disregard for people's life and health. While we were investigating, we stopped this person and made everyone safe. This is, on the whole, our only real complaint; everything else is simply facts and a demonstration of how elite lawyers work. We call on Doctor Patrick to bear the appropriate responsibility for it, unless, of course, the title in front of his name entitles him to act this way (we are not lawyers and do not know the law).
5. To the public, the insurer, regulators and US companies#
- To the public and Taylor Wessing's clients: Judging by the carelessness, Taylor Wessing has a generous insurer that considers all this normal. Check your files and inform the regulator. There is no need to tell the lawyers themselves: they have chosen to hide this for more than a year, ever since Valve first came to them.
- To regulators, on the vulnerability of every file: Review Dr. Patrick's activity and request every PDF that
passed through him with the
"Anlage 1 / Taylor Wessing"badge (or a similar one) placed at the top of the first page. The probability that this is not an isolated case, and that every document from him bearing this sticker is vulnerable, is critically high. - To the insurance company: Please audit your client and the software he uses to work with PDFs and to place the
"Anlage 1 / Taylor Wessing"label at the top of page 1. That is most likely exactly where the problem lies, and it is not an isolated case. There is no point in calling for an audit of all of Taylor Wessing: apart from the name, they seem to share nothing in terms of working environments or security review rules, which ought to exist as a matter of course (apparently a physical signing key and the title in front of a name cover all of that). - To US companies, and to anyone at the European Commission who happens to read this: Try simply obeying the law. Hiring renowned doctors from a renowned "freelance company" looks dangerous and utterly vile towards your customers. If at Valve cheques simply get signed and nobody checks what the lawyers were doing for 106 days, then perhaps paying for dragged-out time rather than for results is exactly why the software is outdated and nobody understands how a PDF works. And if there are no other leaks there, then Doctor Patrick simply managed to wear everyone down with waiting or threats. In essence, what is on sale is a GDPR non-compliance service: poor-quality execution and threats ("you will not win a single case"), combined with a high-quality clean-up of Google results carried out in their own name. We do not draft legal texts and we accuse no one. We simply write what we saw, and what they are trying so hard to delete.
6. What Valve bought was not GDPR processing#
We are not a party to the dispute and we do not defend the account or the ban. One question is left. Valve hired top lawyers: two renowned doctors from a renowned "freelance company", Dr. Tobias Schelinski (Doc. No. 42282474, 15 August 2025) and Dr. Patrick Vincent Zurheide (Doc. No. 42603633, 1 October 2025). What did it pay for? Not GDPR processing: the request was not fulfilled then and is not fulfilled now.
What was delivered instead, in their own words#
- A deadline "if at all": „wenn überhaupt“ — Doctor Tobias.
- Ask for your data, lose your account: terminated „mit sofortiger Wirkung“, in reply to a data access request — Doctor Tobias.
- Proof by quantity: „Unabhängig von den Einzelheiten der Beschwerden…“ Content irrelevant, count everything — Doctor Tobias.
- A diagnosis of the requester: „…Ihr Mandant bzw. dessen Komplizen…“ — Doctor Patrick.
- A verdict for every court: „Aus unserer Erfahrung wird jedes Gericht…“ — Doctor Patrick. No court has ruled; we thought that is what courts are for.
- Four sections of the Criminal Code:
§§ 263, 263a, 202a, 303a StGB, for asking for one's own data. - Instead of the data: five pages of Steam's public Privacy Policy, a copy of the Dashboard the user already sees, and a translated Steam Support reply. Two doctors of law delivered what a support agent had already written.
- A written IOU: „Gerne beauskunften wir die restlichen … Daten, sobald …“ The rest, some day.
- Third parties protected by leaking them: the ban data withheld "to protect third parties", third parties' data shipped in a PDF whose black boxes come off.
- Two versions of the facts: one doctor dates the user from May 2025, the other from 2019. Both signed. A doctor would not sign something untrue, so we accept both.
- Premium spelling: „Die Antwortet lautet ja“, twice, and the partner's own e-mail misspelled in his own signature.
Not a mistake#
[!IMPORTANT] Mistakes are usually hidden. Here nobody even tried. What is on sale is GDPR non-compliance, and it is sold openly. That is not a mistake; that is arrogance.
For themselves, for the user, and for everyone else#
- For themselves:
Art. 17delisting. Doctor Patrick filed first; we published Part 3 on Medium; right after it, the results about Doctor Tobias were delisted too. - For the data subject: seventeen months and counting.
- Without lawyers: Steam Support closed another account holder's request in 3 days, with a link to Account Data: "there's no further information Steam Support can offer, this request will be closed" (ticket
HT-2YBP-F7JP-D4VB; the requester's screenshots, Section 18 of the Steam dossier). - With lawyers: the same closed ticket in 106 days, on letterhead. Who allowed Valve not to process GDPR requests at all? Doctor Tobias?
Titles#
We call them "Doctor" throughout, and we mean it respectfully: the title is a historical fact. Doctor Tobias's rests on a 2005 study of how German authorities supervise foreign online services; Doctor Patrick's on a 2020 study of software development contracts in Scrum. Each is one narrow piece of research, on one narrow topic, done once. It is not expertise in data protection, in PDF files, or in what every court will decide. Under the titles, in this file: no supervision, and a PDF made with Aspose.PDF for .NET 20.8, from 2020.
We have not read either dissertation, Doctor Tobias's or Doctor Patrick's. We have read the publisher's description of Doctor Tobias's. In 2005 there was no GDPR, of course. But it sounds as if the solution was already there.
The publisher's description of Doctor Tobias's thesis (German original and translation)
„Darüber hinaus geht der Autor auf Probleme ein, die sich aus der Durchführung der behördlichen Aufsicht über die Online-Dienste ergeben. Hier sind insbesondere die Ausführungen über die örtliche Zuständigkeit von Behörden hervorzuheben. Dem Autor gelingt es insoweit, anhand einzelner Gesetze Lösungsmöglichkeiten aufzuzeigen wie der Gegensatz einer beschränkten örtlichen Zuständigkeit im Verhältnis zu der weltweiten Präsenz von Online-Diensten zu lösen ist.“
(The author also addresses problems arising from carrying out official supervision of online services. His remarks on the local jurisdiction of authorities deserve particular mention. Using individual laws, the author succeeds in showing possible solutions to the contrast between limited local jurisdiction and the worldwide presence of online services.)
Source: Verlag Dr. Kovač.
Judging by this file, the author did find a solution, for the GDPR too: one lawyer decides who is entitled to their own data and who is not. Which laws had to be used to narrow a European regulation in the interest of a single American company, we do not know. One possible solution would have been to process the GDPR request lawfully. But the author is already a doctor.
Three ways to get an access request wrong#
As far as we, not lawyers, can read the Regulation, there are three, and all three were taken:
- Not handing the data over: unlawful.
- Handing it over incomplete: unlawful.
- "Cleaning it manually" and leaking third parties' data: unlawful twice over (
Art. 5(1)(f),Art. 32).
[!TIP] The fourth way: simply fulfilling the request. It is the only one two doctors of law did not take. That is not bad luck; that is a choice.
Who is accountable?#
As far as we can see, nobody, not financially and not personally. You cannot leave them a review. You cannot write an opinion. The company is "decentralised", so there is no other company to address. And the moment you name the people who signed the letters on the company's behalf, the company's representatives suddenly become private individuals, with a right to be forgotten written for private individuals, applied at once. Yet everything that was delisted was about their professional work. Does a report on a violation, or on professional competence, really fall under the right to be forgotten? How are people supposed to tell a good lawyer from a bad one: from the profile on Taylor Wessing's own website? And can that be trusted, when the firm edits its own Wikipedia history?
We simply do not understand why the historical fact of a doctorate on a narrow topic gives anyone the right to switch off GDPR rights. Perhaps we understand it wrongly. Perhaps Doctor Tobias teaches his students something not quite right. Or perhaps it is right, and Germany has quietly given up on the GDPR. Or is that for Doctor Tobias to decide?
And why, just to publish our audit, our opinion and our experience (about competence, and about the leak risk in Doctor Patrick's vulnerable software), do we have to build the text into our own software so that it survives? That is exactly why all of this looks to us like corporatocracy. And if the person who asks gets nothing, what is the GDPR for? Revenue for lawyers who cannot use a PDF?
Our conclusion#
We are not a party to this dispute, and frankly we are tired of it. In the time it took, we have looked at everything: the Wikipedia history erased twice, the children in the reports, a GDPR request that was never processed, the right to be forgotten used for themselves, a founder who helped write the Nazi version of §175, and a "decentralised" structure in which responsibility belongs to no one. From our small experience, the conclusion is a sad one: titles are titles. Responsibility on the lawyers' side: zero. What remains is arrogance, and a GDPR that was not complied with. We only ask what Valve bought, since it clearly was not GDPR processing.
7. On the notification — the same hand, the same pen#
PhishDestroy wrote to Dr. Patrick Zurheide in German. PhishDestroy does not speak German. We used translation tools, as anyone would, to write in the official language of the recipient's jurisdiction — as a courtesy. The result, by Dr. Zurheide's own assessment, was:
"anscheinend übersetzte, aber durchaus unterhaltsame Nachricht" ("apparently translated, but quite entertaining message")
We note this without elaboration. And we note, alongside it, one small fact:
Dok.-Nr. 42603633, 1 October 2025. A qualified beA signature. Taylor Wessing letterhead. A document authored in German, by a native speaker, a Doctor of German law, an LL.M. Aberdeen, a Certified Scrum Master, dispatched through the mandatory German attorney channel — containing his own surname misspelled in the very first line any PDF reader renders:
| Signed · Dok.-Nr. 42603633 · Page 1 letterhead | Public record |
|---|---|
p.zurheode@*****wessing.com |
p.zurheide@*****wessing.com |
PhishDestroy, writing in a language it does not speak, produced an apparently translated message. Dr. Zurheide, writing in his own language, in his professional capacity, under a qualified beA signature, produced a misspelling of his own name — now immutably encoded in EU timestamping infrastructure.
We do not know whose German is worse. We do know whose hash is permanent.
Since the lawyers think they are the law, and that people's lives, children's lives, do not matter, that is their choice. It is not our conflict. But we can say with confidence that the firm's impunity is historically confirmed, going back to its founder Goltz, one of the eight who drafted the amendments to §175, and to his only famous case, which is sometimes read as a defence of LGBT people: the case of General von Fritsch.
History: Goltz, §175 and the Fritsch case
We will skip the history; we studied it straight from a reliable source and the original record. But this is how the case ended: there was one defendant, and we have three dead. Achim von Frisch, crushed by the millstones of repression. Otto Schmidt, shot in 1943. And General Fritsch himself: it does not matter that he was acquitted, the price was high. In 1939, seeking death, he volunteered for the front in Poland and was killed (or let himself be killed).
Of course, we never counted this case as the firm's founder defending LGBT people. But the outcome is far more interesting than a victory.
Asymmetric justice: Goltz did save one high-ranking officer, whose guilt had been entirely fabricated by the Gestapo. But this alibi was paid for in other people's blood. The same Goltz, as a member of the Criminal Law Commission from 1933, personally designed and introduced the Nazi version of Paragraph 175 (1935).
Statistics versus PR: He defended one heterosexual general of the Wehrmacht elite after first setting in motion a legal conveyor belt that sent about 50,000 real homosexuals to prison and about 15,000 to concentration camps, with a mortality rate of 60%. Saving one general does not cancel out the architecture of genocide.
Denazification, successfully bypassed: The Fritsch case became the perfect "backdoor" through the post-war denazification panels. The architect of repressive laws used his defence of one general as proof of his "independence", escaped Nuremberg, kept his status and his licence, and in 1957 founded the outfit that today trades on its progressiveness under the Taylor Wessing sign.
So yes, all in all: we are sure it makes no difference whether it is this German Taylor Wessing or any other; this is not about the law at all. What we say here is a statement, not an assertion of fact but an assumption, because in reality they will look for any word to latch on to. That is why this is going to the archives: the attempts at censorship and concealment, and the direct links to their heritage. From Doctor Patrick: the very first report, with the crude homophobic word left in. Perhaps by accident, of course, but it is there, and it is the first.
From Doctor Tobias we naturally expect a lecture on irrefutable proof in the form of a report count, and an explanation of which part of that quarter does not matter to him personally. For history, and for understanding where the limits lie, this matters.
That Steam acts as the data controller rather than moderating simply points to the obvious: Doctor Patrick leaked them. Well, so it went. Apparently he did not know that the software for the sticker was broken, these being top doctors, and Steam did not pay for it: whether to process the GDPR request or not, and then to cover up the leak he had seen.
We call for sanity in dealing with the truth, and we want to remind everyone of zero trust: towards everyone, including us. It is all a hostile environment, and in the context of this review quite literally so: bans on 9 May, Nazis, doctors, LGBT people, children. It was fun.
But our options regarding Taylor Wessing are most likely exhausted, since their strategy is to get links removed. We are forced to preserve our text and data, so we are building them into our software, which already has three confirmed letters of thanks from government bodies, including in Germany and Belgium, and has not even been released yet.
We want to warn those who like to bend the law: there is no need to take the repository down. We have not entered into any conflict with you in all this time. But if you decide to break our work in order to hide the truth, then without an active repository regulators and others will not be able to compare the signature of a version (though who am I telling), and then we will enter into direct conflict. On that note, we hope to take our leave of mega-expertise and elite lawyers. It was not fun, and I am not glad. All the best.
Observation — The Carelessness Correlation#
Upon understanding the scope of the redaction failure, PhishDestroy notified the firm immediately. The reason was not adversarial: the probability that this file is not the only one is critically high. The same pipeline — Aspose.PDF for .NET 20.8, the same sticker method, the same "Anlage 1 / Taylor Wessing" label — could be present in every document that passed through the same process. The notification was sent in German, by people who do not speak German, as a responsible disclosure to the data protection contact of the responsible firm.
Dr. Zurheide called it "durchaus unterhaltsame" — quite entertaining — and noted that our message appeared to be translated.
The same person, in the same professional capacity, under a qualified beA signature, in a paid engagement spanning 106 days, produced the following in a single document:
- His own surname misspelled in the letterhead —
p.zurheode@*****wessing.com— the first bytes any PDF reader renders. - "Die Antwortet lautet ja" — verb used as noun, meaning "the answer answers yes" — in two separate sections, identically.
- 1,044 filled vector paths drawn over text that remained fully present in the content stream. 905,672 characters extractable by anyone with
pdftotext. Aspose.PDF for .NET 20.8— released August 2020, five years without update, with documented and patched redaction-class vulnerabilities in later releases — processing sensitive personal data of minors.- The client's grammatical gender, unreconciled — both letters use "unsere Mandantin" (feminine singular) to refer to Valve Corporation throughout. The template placeholder was not updated before dispatch. In a document that terminates an account with immediate effect and threatens prosecution under four statutes of the criminal code, the attorneys did not read their own text closely enough to notice the gender of the entity they represent. This is not a stylistic choice. It is a copy-paste artifact in a bespoke legal instrument for which a client was billed.
A lawyer can defend four criminal statutes in a civil response as aggressive client representation. No lawyer in the world can defend misspelling their own surname under a qualified signature, writing "the answer answers yes" in two separate sections identically, treating vector overlays as permanent redaction, running five-year-old software with documented vulnerabilities on minors' data, and not reading the gender of their own client in the final draft. These are not legal positions. They are quality-assurance failures at the level of a first-year proofreading pass, certified forever by a qualified electronic signature.
He signed a document he had not read. Then he received a notification about the consequences and responded with the same quality of attention. The deficit is consistent. It is now in both records.
[!CAUTION] The Cost of Escalation: We Are Not Here for Steam
Let us be absolutely clear. We are not a party to this dispute. We have no interest in whether an account in a video game was banned, hacked, or sold. Arguing over a Steam ban with elite corporate lawyers would be both absurd and beneath our focus.
Our interest is strictly infrastructural and historical. We are auditors of digital evidence and systemic impunity. The Steam case was merely a lens — a highly revealing one — that exposed the mechanical failure of Dr. Patrick Zurheide and the compliance theater of Taylor Wessing.
We documented the broken PDF, the misspelled signature, the botnet logs, and the arrogant response to a data breach. That audit is complete.
But if you decide to escalate — if you attempt to use your corporate weight to take down this repository, erase the truth, or silence this audit — you will force a shift in our focus. And you will not like where that focus lands.
Taking this repository down will not delete the cryptographic hashes. But it will turn us from objective auditors of a single technical failure into a direct party to a systemic conflict.
If you force that escalation, we will stop looking at Aspose.PDF and start looking at the foundation of your impunity. You might try to dismiss the ideological legacy of your founder, Rüdiger Graf von der Goltz, and his drafting of §175 as a "historical footnote." But as OSINT researchers, we follow the money. A century of it.
We will shift our resources to tracing the post-war capital flows that built the Düsseldorf office of Wessing. We will offer the public a mathematically precise history of how "denazification" was bypassed, and how assets, antiques, and looted wealth — derived from what was openly called "the plundering of the USSR" — were routed through Switzerland to fund the "golden address book" that protects your firm today. A financial trail that remains highly relevant to modern restitution claims in Europe and Ukraine.
You are currently facing a minor, localized embarrassment over a leaked PDF and an inability to spell your own name. Do not force us to examine the blood capital that bought your letterhead.
Enough deleting the truth.
Source record · Operator notice · MIT License
Project · Documentation · Wiki