Documentation / 17
Zero Trust Case Study: Taylor Wessing, Dr. Zurheide & Dr. Schelinski
Live case studyReal documents · real signatures · hashes published below · counts reproducible offline
A case study in why zero trust is necessary. One request for a person's own data under Article 15 GDPR, answered by partners of a leading international law firm under qualified signatures. Every assurance in the answer had to be taken on trust: the signature, the titles, “a month of manual review”, the protection of third parties, “every court will agree”. Checked against the delivered file, none of them holds. This page shows what trust produced, and how a checkable model would have left no room to deceive or to doubt.
Professional roles are taken from the firm's linked profiles. This page does not say whether blocking the Steam account was justified. It shows what the delivered file contains and what the signed letters say about it. Every figure can be checked against the files.
In short. A signature tells you who sent a file. It cannot tell you whether the file is complete, correct or true. Only checks on the bytes can, and anyone can repeat them.
Zero trust: check the file, not the sender
Zero trust means that nobody has to be believed: not a firm, not a title, not a signature, and not us. An answer to an access request should prove itself. It has to answer three questions, and a signature answers none of them.
Most legal disputes in the EU stay closed: settlements under NDA, sealed files, decisions that are never published. We have nothing against that. This case is different, and probably not because what happened in it is rare. It has no NDA and no court decision, so it can be read from end to end: a very simple law, the GDPR; one request for a person's own data; what was actually delivered; and black rectangles that anyone can remove.
What makes it unique is who answered, and how. Dr. Tobias Schelinski and Dr. Patrick Zurheide are partners of Taylor Wessing, in its own words “a European legal services powerhouse”. Both hold doctorates; one is a certified specialist lawyer for IT law, the other holds a Master of Laws from Aberdeen. They took 106 days not to process a lawful access request. Along the way they handed the reported account holder the complaint texts and logins of more than 1,800 other people, some of whom may be minors, under black rectangles that anyone can remove.
PhishDestroy's view. A login, the user name, is highly personal data. It is reused across services, and an account that has lived for years is, in most cases, tied to a real person who can be identified through it. Looking only at the fifty visible fragments, we think any court could indeed be misled. With the full picture, the timeline and the arithmetic on this page make it plain that the GDPR request was not processed. No signature and no misspelled name changes that fact.
What trust produced, and what the model would have done
Each assurance in the answer is set below against the delivered file, and against the checkable model this page proposes. The evidence for every line follows further down.
„Dieses Schreiben ist qualifiziert elektronisch signiert“
It says who sent the letters. Under it, 905,672 characters stay readable beneath black rectangles.
EvidenceThe firm signs a salted hash of every withheld field. The content is checked, not the sender.
Counsel decide what the requester gets to read.
50 complaints left readable, all filed after the block and the request; 43 of them are “Suspected Hijacker”. 1,944 covered over.
EvidenceA rule declared and signed when the copy is made, every withheld record counted, and the choice reviewed by the authority.
„… die volle Monatsfrist ausgeschöpft … manuell die Daten bereinigt …“
An 830-page file made in 36 seconds. Its first readable row is a homophobic slur, and complaints left readable are contradicted by the same file.
EvidenceNobody's word about effort counts. The file proves itself, and anyone can find a contradiction in it.
„soweit keine Rechte Dritter entgegenstehen“
The logins and complaint texts of more than 1,800 other people, delivered under black rectangles that anyone can remove.
EvidenceOther people's data never enters the requester's copy. It travels sealed for the authority's key.
„Auskunft gemäß Art. 15 Abs. 1, Abs. 3 DSGVO“
Payments, support tickets and the records behind the block are absent. Only the complaints appear complete.
EvidenceThe signed manifest lists what is included and counts what is not. No gap can go unnoticed.
„Aus unserer Erfahrung wird jedes Gericht …“
Fifty fragments can mislead. The whole file shows a request that was not processed.
EvidenceThe court or regulator opens the full original and checks every field against what the firm signed.
Every row has the same shape. An assurance that had to be believed, a file that contradicts it, and a check that would have made the assurance unnecessary. With the model there is nothing to deceive with and nothing to doubt: the requester sees what is theirs, the authority sees the rest, and every field is bound to what the firm signed. See the model
The evidence, point by point
Every line of the comparison above rests on the files below: two signed letters and Anlage 1. Page references use PDF page order, and every figure can be repeated offline.
The text remained under the black rectangles.
This is how an answer to a simple access request looks when it comes from the top of the profession. The black rectangles left the underlying text in the file. That made it possible to read and compare both groups: the 50 descriptions left visible and the 1,944 covered over.
“Regardless of the details of the complaints”
The number alone is said to show repeated breaches of the Steam agreement.
Dr. Schelinski · 15 Aug 2025 · p. 2„Unabhängig von den Einzelheiten der Beschwerden …“
August–September 2025
February 2021–July 2025
43 of the 50 visible descriptions are labelled “Suspected Hijacker”. Among the 1,944 covered descriptions, 269 have that label.
Fifty complaints convenient for counsel
The October letter names the ground for the block: the account was blocked as „Used for Hijacking“ (Dr. Zurheide, p. 8). Of the fifty complaints the requester was allowed to read, 43 say the same thing: “Suspected Hijacker”. All fifty were filed months after the account was permanently blocked, after the access request, and after the last logon that the same file records.
Anlage 1, page 1, gives Last Client/Web Logon Time: 2025-05-23 20:48:31 (UTC). The account was blocked on 7 May 2025. On 9 May 2025 Steam Support answered the first ticket: the block was not an error, it was permanent, and the ticket was closed. The access request followed on 17 June. By the letters' own account, a third party had the account by then: Dr. Schelinski writes that it was acquired from a third party after 3 May 2025 (p. 2), and Dr. Zurheide that a third party made payments through it after 3 May, the last on 30 July 2025 (pp. 1–2). The supplied complaint table then records:
Complaint text under a black rectangleComplaint text left readable
- From this date, per the letters: a third partyThe account was “acquired from a third party”: Dr. Schelinski, p. 2 · “payments by a third party”: Dr. Zurheide, p. 1
- Account blockedSteam
- Not an error, permanent; ticket closedSteam Support, first ticket
- Last logonAnlage 1, p. 1
- Access requestDr. Zurheide, p. 1
- The deadline begins, “if at all”Dr. Schelinski, p. 1
- Last “payment by a third party”; data attributed to the requester only from hereDr. Zurheide, p. 2
- 47 complaints, all readableAnlage 1, pp. 444–448
- Termination: 1,938 complaints, “regardless of their details”Dr. Schelinski, p. 2
- 3 complaints, readableAnlage 1, p. 444
- “Date of Report”Anlage 1, p. 1
- The answer: “the full month”, data cleaned “by hand”Dr. Zurheide, p. 1
Dr. Zurheide writes that the full one-month period had to be used and the data cleaned by hand: „musste leider die volle Monatsfrist ausgeschöpft werden … manuell die Daten bereinigt werden mussten“ (p. 1). Three of the readable complaints are dated September 2025, and the report itself is dated 29 September. They were filed in the last weeks before the answer, while, by his account, the data was being cleaned.
“This account just started acting shady overnight”
Suspected Hijacker · August 2025 · p. 446
“Suddenly messaging people weird links probably stolen”
Suspected Hijacker · August 2025 · p. 448
“Friend warned me to report this one”
Suspected Hijacker · August 2025 · p. 446
“Everyone in voice chat agrees it's a stolen account”
Suspected Hijacker · August 2025 · p. 446
The same file contradicts them
Some of the fifty make claims that Anlage 1 can check against itself. The file records the account's logins and its security history. Both are in it; the security history is under a black rectangle.
“My friend can't log in, says someone changed the password”
Not made by the owner, as the same file shows. There is no password change in 2025.
“This account just started acting shady overnight”
“Suddenly messaging people weird links probably stolen”
The login history ends in May 2025. Not one login is recorded in June, July, August or September. The account had been blocked since 7 May 2025; on 9 May Steam Support called the block permanent.
“Real person probably got locked out”
“My friend said they can't get into this account anymore”
The last change the security history records is the password reset of July 2024.
PhishDestroy's reading. The slur on page 444 needed a translation. These complaints are in English, and the answer to them is in the same file. A month of manual review left them readable and put the line that contradicts them under a rectangle.
How the fifty read
Formatting does not prove who wrote a complaint. It is exactly what a court would look at before counting one.
| Check | Left readable · 50 | Covered over · 1,944 |
|---|---|---|
| Period | Aug–Sep 2025 | Feb 2021–Jul 2025 |
| “Suspected Hijacker” category | 86%43 of 50 | 13.8%269 of 1,944 |
| Description contains Cyrillic | 4%2 of 50 | 55.4%1,077 of 1,944 |
| Reporter login: Latin letters + 3–5 digits | 62%31 of 50 | 21.6%420 of 1,944 |
Cyrillic: at least one character from that script. Login pattern: Latin letters followed by 3–5 digits, nothing else. All 1,995 reporter logins, including those beside the 50 visible texts, are covered and remain extractable. No reporter login is reproduced here. Four readable texts repeat word for word across nine records; “Acting way off pretty sure someone else is using it” appears three times (pp. 446, 447).
„Unabhängig von den Einzelheiten der Beschwerden zeigt schon die bloße Anzahl …““Regardless of the details of the complaints, the mere number shows …”
Is the content really irrelevant to a court?„Aus unserer Erfahrung wird jedes Gericht die Sperrung … als rechtmäßig qualifizieren.““In our experience, every court will qualify the block … as lawful.”
Has his experience included every court? And would every court agree, with data processed like this?The two questions are PhishDestroy's. We do not say how a court should rule on the block. We say that a court should be able to read what it is asked to count.
What the black rectangles remove from view
The two letters treat the same complaints in two ways. Dr. Schelinski counted all of them against the requester, „1.938 Mal“, regardless of their details (15 Aug 2025, p. 2). Dr. Zurheide then drew a line at 30 July 2025: only from that date „können wir … davon ausgehen, dass etwaige Daten … sich auf Ihren Mandanten beziehen“ (1 Oct 2025, p. 2). The black rectangles follow that line: every complaint text up to 23 July 2025, the last one before it, is covered; every one from August on is readable.
PhishDestroy's reading. Before 30 July 2025 the complaints count against the requester as a number, and are withheld from him as data that is not his. The October letter itself argues from „zwischen 2019 und 2023“ (p. 7).
p***rA homophobic slur, masked here. It is the first entry the requester could read, after a month of manual review.
What lies under the rectangles
1,148 complaints, more than half of the table, are filed as “Offensive Profile”. Not one was left readable: 1,147 have their text covered and one has no text. Read from under the rectangles, without logins, the covered descriptions keep returning to the same themes:
| Theme | Covered | Readable |
|---|---|---|
| Nazi, Nazism | 110 | 0 |
| Hatred, hate speech | 108 | 0 |
| Racism | 99 | 0 |
| Ukraine, Ukrainians | 90 | 0 |
| Russophobia | 84 | 0 |
| Insulting the nation or Russians | 65 | 0 |
| Propaganda | 64 | 0 |
| An ethnic slur for Ukrainians | 50 | 0 |
| Politics | 46 | 0 |
615 of the 1,944 covered descriptions touch at least one of these themes; none of the fifty readable ones does. Long texts repeat too: 18 texts of eight words or more appear word for word in 48 rows. Two of them, four times each:
“I made this account to report this user because he has stolen my account”
Covered · 4 rows
“I created this account in order to expose this user because he robbed my account.”
Covered · 4 rows
One of the fifty readable texts (p. 448) is a pasted Steam profile page that names other users. It is not reproduced here. The rectangles covered every reporter's login and left that page readable.
The statements and the supplied records
Each statement below is quoted from the signed letters. Each record is in the files they delivered.
“Hundreds” in every year
„In jedem Jahr, bis ins Jahr 2025 hinein, gab es demnach hunderte Beschwerden.“
The annual counts in the supplied complaint table. The full monthly count is under Verify it yourself.
The full month, cleaned by hand
„… die volle Monatsfrist ausgeschöpft … manuell die Daten bereinigt …“
Anlage 1 was created at 19:58:05 and last modified at 19:58:41 for 830 pages. Its first readable complaint is a homophobic slur.
Protection of third-party rights
„soweit keine Rechte Dritter entgegenstehen“
Text is still extractable beneath 1,044 black rectangles that overlap it. The rectangles also cover the account's own security history (p. 830).
“Between 2019 and 2023”
„Über einen Zeitraum von mehreren Jahren, zwischen 2019 und 2023 …“
Anlage 1, page 1, gives the account's creation time: August 2020.
Every court will agree
„jedes Gericht … als rechtmäßig qualifizieren“
The sentence says every court will find blocking the Steam account lawful. It names no court and cites no ruling.
What the signature can and cannot tell you
A qualified electronic signature is strong evidence about the sender. It is not evidence about the content. The two questions have to be checked separately.
A signature can show
- who signed the document
- that the signed bytes have not changed since signing
A signature cannot show
- that the export is complete
- that the redaction removed anything
- that the statements in it are true
- that anyone read it before signing
„qualifiziert elektronisch signiert“Declared by the firm on page 9.2bb927e2…4ff7d6afMatches the recorded hash.pdftotext Anlage1.pdf -905,672 characters readable under 1,044 rectangles.Sender: declared. Integrity: matches. Content: broken. The signature answered the first question and none of the others.
Dr. Patrick Zurheide, LL.M. (Aberdeen)Signatoryp.zurheode@*****wessing.comLetterheadp.zurheide@*****wessing.comPublic recordThe request the export was meant to answer
Behind the signatures is one request for one's own data. The law that governs it is short.
- Art. 15(1)
- “The data subject shall have the right to obtain from the controller confirmation as to whether or not personal data concerning him or her are being processed, and, where that is the case, access to the personal data …”
- Art. 15(3)
- “The controller shall provide a copy of the personal data undergoing processing.”
- Art. 12(3)
- “… without undue delay and in any event within one month of receipt of the request. That period may be extended by two further months where necessary …”
Source: EUR-Lex
The letters know this law. Dr. Zurheide's opens with it: „nachfolgend erteilen wir Namens und in Vollmacht unserer Mandantin Auskunft gemäß Art. 15 Abs. 1, Abs. 3 DSGVO“ (p. 1). Apart from one reference to third-party rights (Dr. Schelinski, p. 3), neither letter cites a provision that allows a controller to restrict access: not Art. 12(5), not Art. 23, not the German BDSG. What the request received instead:
- 15 Aug 2025 · Dr. Schelinski · p. 1The deadline, “if at all”
„Die Frist nach Art. 15 DSGVO hat, wenn überhaupt, erst … am 29. Juli 2025 begonnen“
- 15 Aug 2025 · Dr. Schelinski · p. 2The account terminated
„Hiermit kündigen wir daher Namens und in Vollmacht der Valve Corporation … mit sofortiger Wirkung.“
- 15 Aug 2025 · Dr. Schelinski · p. 2Proof by count: 1,938 complaints, regardless of their details
„Unabhängig von den Einzelheiten der Beschwerden zeigt schon die bloße Anzahl …“
- 1 Oct 2025 · Dr. Zurheide · p. 2Data narrowed to 30 July 2025
„… können wir erst ab diesem Zeitpunkt davon ausgehen, dass etwaige Daten … sich auf Ihren Mandanten beziehen.“
- 1 Oct 2025 · Dr. Zurheide · p. 8The rest, on a condition
„Gerne beauskunften wir die restlichen (bzw. noch weitere) personenbezogene Daten, sobald Ihr Mandant uns nachvollziehbar darstellen kann …“
- 1 Oct 2025 · Dr. Zurheide · p. 8“Accomplices”
„… dass Ihr Mandant bzw. dessen Komplizen seine Phishing-Angriffe … in verschleierter Form fortsetzen will“
- 1 Oct 2025 · Dr. Zurheide · p. 9Four criminal statutes
„… §§ 263, 263a, 202a, 303a StGB) einer strafrechtlichen Verfolgung zuzuführen.“
None of this is a condition in Art. 15. A right of access is not cancelled by a termination, a forecast about courts or a criminal statute. 106 days after the request, it stood exactly as written.
PhishDestroy's reading. The doctors cite the law on page 1 and then write as if there were no such law.
The letter lists what Valve processes. The file leaves most of it out.
On pages 2–6 the October letter quotes the Steam Privacy Policy to describe the personal data Valve processes. Each category it names is compared below with Anlage 1. Anlage 1 has twelve sections: account, profile, name history, logins, product keys, playtime, phone, complaints, chat, Steam Guard devices, friends and security changes.
| Data | Named in the letter | In Anlage 1 |
|---|---|---|
| Transactions and payments | „Transaktions- und Zahlungsdaten“ · p. 2 „… Transaktionsdaten … für einen Zeitraum von bis zu zehn (10) Jahren aufbewahren muss“ · p. 6 | Absent |
| Trades and Community Market | „… Konsistenz des Gameplays oder Steam-Community-Marktes …“ · p. 6 | Absent |
| Achievements, game progress, in-game items | „Ihre erspielten Errungenschaften … Ihren Spielfortschritt … Ihre im Spiel erhaltenen Gegenstände“ · p. 4 | Absent |
| Game ownership | „… mindestens Ihr Eigentum am fraglichen Spiel“ · p. 4 | Absent · playtime and 100 key activations from a single day only |
| Levels, badges, trading cards | „Daten über die Nutzung des Steam-Clients und der Steam-Websites“ · p. 3 · items and market · pp. 4, 6 | Absent |
| Posts, comments, follows | „… veröffentlichen, kommentieren oder denen Benutzer folgen“ · p. 3 „Message Boards, Foren und/oder Chatbereiche“ · p. 5 | Absent |
| Chat | „Informationen, die Benutzer im Chat gesendet haben“ · p. 3 | 2 entries, covered |
| Support tickets | „… wenn Benutzer Informationen oder Support von Valve anfordern“ · p. 3 | Absent · including the May 2025 ticket that confirmed the block |
| Linked third-party accounts | „… mit dem Konto eines Drittanbieters zu verknüpfen“ · p. 5 | Absent |
| Records behind the block | „Zum Entdecken von Verstößen erforderliche Informationen“ · p. 3 „… nach einer manuellen Prüfung durch einen Mitarbeiter der Valve Corporation“ · p. 7 | Absent · no review record, no device link, no phishing report |
The letter describes the data. The attachment does not contain it. Payments are the basis of both lawyers' conclusions about ownership, yet the payment category is the one the file leaves out.
What the file does contain, and for which period
Periods are taken from dates in the file, including dates under the black rectangles.
| Section | In Anlage 1 | Period in the file |
|---|---|---|
| Basic account data · email, country, username, Steam ID | Readable | Current state |
| Logins | Date and type readable; time, IP, hardware ID covered | Oct 2023 – May 2025 · account exists since Aug 2020 |
| Playtime | Games readable; last-use date and time covered | Dec 2020 – May 2025 |
| Chat | 2 entries, covered | Sep 2025 only |
| Complaints against the account | 1,995 rows · 50 descriptions readable | Feb 2021 – Sep 2025 |
| Friends and blocks | 5,789 rows · covered | Feb 2021 – Sep 2025 |
| Steam Guard devices · registered phone · security changes | Covered | Security log: Aug 2020 – Jul 2024 · 4 rows |
| Product key activations | Keys covered | 100 rows, one date: 13 Mar 2025 |
Only the complaints appear to be there in full. Almost nothing else is: logins start in October 2023, friends in February 2021, product keys on a single day, and whole categories that Valve stores are absent. The categories the letter's own decisions depend on, payments and the records behind the block, are not in the file at all.
The friends list has 5,789 rows: 4,410 “Blocked User”, 1,182 “Friend” and 200 “Inviter”, dated 24 February 2021 to 28 September 2025; 74 are dated after the last logon. Whether it is the current list of connections or a full history including removed ones cannot be determined from the file.
The answer to Art. 15(1) raises three further questions. The recipients (point c) and the source of the data (point g) are given only as general policy text, not for this account. The storage period (point d) is a quotation from the policy, without specifics. And the letter sends the data „als Anlage 1 und 2“ (p. 3); only Anlage 1 is examined here.
Valve had already verified who owns the account
The account was registered as a Steamworks partner in order to publish a game. That process involves a Steam Direct fee of USD 100, a tax interview, payout bank details and identity verification carried out by Valve itself. All of it is personal data Valve processes. Art. 15 GDPR covers every category of personal data processed, not only those listed in a privacy policy. None of it appears in Anlage 1.
“Not a single proof of ownership”
„… kein einziger Beleg für die Inhaberschaft (Verfügungsbefugnis) Ihres Mandanten für den Account …“
The partner verification, its documents and the USD 100 payment are held by the client the letter speaks for.
Proof demanded from the requester
„… gefälschten ‚Utility Bill‘ …“ · „… tatsächlich alleiniger Inhaber des Accounts …“
The requester is asked to prove ownership while the ownership records Valve itself verified are left out of his access copy.
The model: nobody decides alone, nothing can be swapped
This is not about one piece of software. It is about who decides. In this case two lawyers decided which fifty complaints mattered and that the rest did not. No court, no regulator.
Some things must stay hidden: the reporters' logins are other people's data. The question is who decides, and whether anyone can check the decision afterwards. A black rectangle answers neither, and anyone can remove it. Two standard tools answer both: a salted hash in the requester's copy, and the original sealed for the public key of a supervisory authority or a court.
c = SHA-256(salt ‖ value)
The salt is 16 random bytes, new for every field. The requester's copy carries c in place of the value, under the firm's signature. The value and its salt travel in an envelope encrypted for the authority's public key, with OpenPGP or with X25519 and AES-GCM. Without the authority's private key nobody can open it, and the firm cannot swap a value without breaking the commitment it signed.
- Step 1 · the requesterHands over the copy and the envelope
The signed copy with its commitments and the sealed envelope go to the supervisory authority or the court.
- Step 2 · the authorityOpens the envelope and recomputes
The inspector decrypts with the authority's private key and recomputes SHA-256(salt ‖ value) for every field. Each result must equal the commitment the firm signed.
- Step 3 · an independent bodyDecides what was really protected
The authority, not the firm, reads everything that was withheld, here 1,944 complaint texts and a security history, and decides whether third-party rights required withholding it.
Black rectangles drawn on top. The text underneath stays in the file.
The copy holds commitments. Values and salts are in the envelope.
- 1The requester hands over the copy and the envelope
- 2The authority opens it and recomputes every commitment
- 3The authority decides what stays withheld
Both panels hide the same two fields. Read the raw bytes, then run the authority's check.
None of this needs new infrastructure. German supervisory authorities already publish OpenPGP keys: the Federal Commissioner for Data Protection lists one for every unit, and the LfDI Baden-Württemberg offers its public key for encrypted e-mail. German courts already receive filings through the EGVP, whose end-to-end encryption is based on the OSCI protocol.
PhishDestroy's position. Who gave counsel the right to decide what is significant and what is not? Lawyers should not make that decision. Everything should be handed over: not under black rectangles that anyone can remove, but sealed for the key of a court or a regulator, so that there is no room for “errors”, for “misunderstandings”, or for showing only what is convenient.
The honest model: full data, a declared rule, the key with the authority
The requester gets everything that is not in dispute, at once. Anything withheld is not covered with a drawing and not kept back in silence. It goes, complete and signed, encrypted to the key of the authority that is entitled to decide on it.
| Question | What happened | Honest model |
|---|---|---|
| Who decides what is withheld | Counsel of the party in the dispute | A rule declared and signed when the copy is made; the authority reviews it |
| What the requester receives | Selected rows; whole categories absent; a cut-off with no record behind it | Every record not in dispute, immediately |
| Third parties' data | Covered with drawings and still in the file | Removed from the requester's copy; kept in the original for the authority |
| Withheld parts | Unknown in number, unknown in content | Counted in the signed manifest; full original encrypted to the authority's key |
| Proof of how the copy was chosen | Exists only because the redaction failed | Built in: rule, count, hash of the original |
| Disputed fields | Decided by the letter: “every court will agree” | Decided by the regulator or court, who can open them |
| Time | 106 days | Export plus delivery |
| Role of counsel | Sets scope, burden of proof and verdict | Argues the dispute in court; does not edit the requester's data |
The authority does not need trust either. Art. 58(1)(e) GDPR already empowers a supervisory authority to obtain access to all personal data a controller processes. The model only hands it over in a form that can be verified on arrival.
The reasons given in the letters, ownership doubts, payments by third parties, complaints, suspected phishing, explain why Art. 15 was not fulfilled. They do not fulfil it. Whatever the basis, the outcome is the same: the requester did not receive his data, other people's data was delivered under drawings, and the selection could be checked only by accident. Data access is a right of the data subject, not a bargaining chip in someone else's dispute.
How TgWitness keeps originals and makes copies checkable
TgWitness exports conversations as evidence. Its design starts from the lesson of this case: an export should not ask to be believed because of who hands it over. The original captured journal is retained. A sharing copy records the selected records and fields, the disclosure rules and the number of excluded records in its signed manifest. Zero trust applies to everyone, including us.
Keep the original
Retain the full captured journal and its signatures. Keep a checkpoint independently so a later replacement or truncation can be checked.
Encrypt the delivery
Encrypt the archive for a recipient key or protect a delivery with a password. Decryption requires the corresponding key or password.
Name the omissions
Put the purpose and rules in the signed manifest. Mark minimised records, count excluded records and retain links to the source journal.
TgWitness already seals complete originals for a recipient key, with the envelope used in the demonstration above, and marks what a disclosure withholds. The verifier checks record signatures and the sharing copy's link to the source journal; checking withheld content against its original hash requires the retained full original. Per-field salted commitments for an authority are the step this case argues for.
| In Anlage 1 | TgWitness feature | Recorded check |
|---|---|---|
| Text under black rectangles | Withheld fields removed from the sharing copy; original retained separately | Named omissions and the original record hash |
| 50 descriptions visible; 1,944 covered | Signed disclosure rules and excluded-record counts | The selected scope and its source-journal reference |
| PDF attachment | Encrypted delivery of the captured archive | Authenticated decryption; archive signatures and hashes |
| File identified by SHA-256 below | Record hashes, signatures and retained checkpoints | Comparison with the previously saved journal |
What the software is built to guarantee
A typo in a name does not change data signed by the software. A month past a deadline does not change the original records. Any change breaks the chain, and the verifier says so. Try both below.
86582990a7b364adbd83071c9edb4774ed6e8ea50b80dca1ae426c3fa679a1d617fae25500c51998112b146c76b21b04bf3d4034407f2f958bced7d6d6e928ba1 character apart60 of 64 hex digits differ128 of 256 bits differ
One character apart. Two unrelated fingerprints.
adc396074b0f04…= saved hash0b8eda5c2f43ae…= saved hashdbe2eef85bfb5a…= saved hashEach record holds the fingerprint of the one before it. Changing record 2 changes its hash and breaks the link from record 3.
How TgWitness sharing copies work · The sealed envelope · Implementation and verification scope
Verify it yourself
Any regulator, court or auditor holding the files can repeat every check on this page offline. Aggregate results only: reporter logins, account identifiers and profile data are not published here.
All months: 2021–2025
| Year | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Total |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2021 | 0 | 2 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 1 | 20 | 25 |
| 2022 | 10 | 7 | 43 | 9 | 2 | 7 | 2 | 11 | 7 | 6 | 5 | 13 | 122 |
| 2023 | 111 | 48 | 156 | 59 | 52 | 53 | 66 | 52 | 73 | 44 | 53 | 58 | 825 |
| 2024 | 69 | 58 | 111 | 36 | 33 | 46 | 83 | 53 | 54 | 70 | 79 | 82 | 774 |
| 2025 | 92 | 32 | 35 | 20 | 12 | 1 | 7 | 47 | 3 | — | — | — | 249 |
0 means no record for that month in this export; — is after its September 2025 cutoff. Total: 1,995.
All report categories in the supplied table
| Recorded report type | All records | Readable descriptions | Covered descriptions |
|---|---|---|---|
| Offensive Profile | 1,148 | 0 | 1,147 |
| Suspected Hijacker | 312 | 43 | 269 |
| Cheating | 290 | 2 | 288 |
| Offensive Persona Name | 87 | 1 | 86 |
| Offensive Avatar | 57 | 3 | 54 |
| Harassment | 46 | 1 | 45 |
| Spamming | 37 | 0 | 37 |
| Spoofing | 16 | 0 | 16 |
| Auto Moderation | 1 | 0 | 1 |
| Trade Scam | 1 | 0 | 1 |
The Offensive Profile total includes the one empty description. Totals: 1,995 records, 50 readable descriptions, 1,944 covered descriptions, 1 empty description.
Logins and security history
Anlage 1, page 1: Last Client/Web Logon Time: 2025-05-23 20:48:31 (UTC) and Date of Report: 09-29-2025. The login history on pages 1–119 lists the most recent logins first; its latest entries are from May 2025, and none is later.
Page 830, “Security History”, is under black rectangles. Its last password change is from July 2024; it records no change in 2025. Dates, addresses and identifiers from those rows are not reproduced.
pdftotext -f 1 -l 1 Anlage1.pdf - # last logon, date of report
pdftotext -f 830 -l 830 Anlage1.pdf - # security history
PDF metadata and signature declarations
PDF metadata: producer Aspose.PDF for .NET 20.8; creation 1 October 2025, 19:58:05; modification 19:58:41, both UTC+02:00. The two timestamps are 36 seconds apart.
Both letters declare a qualified electronic signature on their final page: „Dieses Schreiben ist qualifiziert elektronisch signiert“. Signature validation is a separate check from the content and redaction checks shown here.
Reproduce the counts and compare source hashes
The counting script is pinned to the Anlage 1 hash below. It reconstructs table rows on pages 444–620 and joins 118 cells that continue across page boundaries. Visibility is determined by word-box intersection with opaque black rectangles; the one empty description is recorded separately.
Cyrillic counts use U+0400–U+052F. The login-format comparison uses the full-string pattern [A-Za-z]+[0-9]{3,5}. Repetitions are counted after extraction whitespace is normalised. Word counts in the covered descriptions match word stems in any case. These are descriptive measurements, not an automated finding of common authorship or misconduct.
Optional language estimates in the JSON use Lingua 2.2.0 locally; short and ambiguous texts remain unassigned. The 905,672-character check counts each non-space character whose bounding box intersects a black rectangle once; 1,044 of 1,329 black rectangles overlap such text.
Aggregate counts · JSON · Local counting script · Python
python signed-export-audit.py Anlage1.pdf --output counts.json
sha256sum Anlage1.pdf
pdfinfo Anlage1.pdf | grep -E "Producer|CreationDate|ModDate"
pdftotext -layout Anlage1.pdf - | less
The script requires PyMuPDF and lingua-language-detector. It makes no network requests and outputs aggregates, not complaint texts or logins.
| File | SHA-256 |
|---|---|
| Dok.-Nr. 42603633 (Dr. Zurheide) | de0fdcf6bfaccedc98d1670438bc7ca3330479096875e716dbb9678922b43ab9 |
| Dok.-Nr. 42282474 (Dr. Schelinski) | b48e09c28ee40a46f1d404041751f718fb185d1eb774ddabb4373fdd53bbe2f1 |
| Anlage 1 | 2bb927e2c42fdc2e3ad089ae302dd887c343f6798aba00fcfac279224ff7d6af |
The lesson for any export. Lawyers can sign an export. The signature says who sent it, not what is true in it. Truth is what survives a check that anyone can repeat.
Our position
PhishDestroy's position. We respect the law and the courts. The law is not an opponent of the truth. Those who bend it in order not to comply with it are no allies of a court, and a doctoral prefix cannot be an authority for one.
A doctorate is a historical fact: one piece of research in a narrow theoretical field, defended once. It does not make anyone an IT lawyer.
As far as we can see, nothing in the title answers for the errors: not the arguments written under the signature, not the misspelled name, not the leak of the data the letters themselves claimed to protect.
Both signatories later filed search-delisting requests under Art. 17 (see the operator notice). The right to be forgotten should not erase a professional's professional negligence. And is anyone checking documents that go out under a qualified signature? These letters read like an e-mail to a friend, not like a document of public significance.
Zero trust, towards everyone. Money is good. Selling the laws of one's own country for it is, in our view, not the best use of it. But we are not experts.
PhishDestroy is not a party to the dispute and does not say whether blocking the Steam account was justified. The data subject is not identified on this page; account identifiers, logins, IP addresses and personal data are not reproduced. Complaint texts are quoted without the reporters' logins, including texts under black rectangles, which remain in the file's text layer. Letters: Dok.-Nr. 42282474, 15 August 2025 (3 pages); Dok.-Nr. 42603633, 1 October 2025 (9 pages). Attachment: Anlage 1 (830 pages). Page references use PDF page order. English renderings of German quotations are ours. Wider case dossier · The 106-day GDPR file.