Try for 30 days

GDPR Data-Flow Declaration

Relations with External Large Language Models

Factual, code-derived description of every path on which data leaves IRONSTICK towards an external LLM, what exactly is transmitted, in which form, and where the pseudonymisation layer applies. Windows desktop edition. This document describes IRONSTICK's behaviour only — what the AI provider does with received data is governed exclusively by the provider's own terms (the terms and privacy policies of the providers the user has set up: Alibaba Cloud (Qwen), Moonshot AI (Kimi), OpenAI, Anthropic and, if switched on, Groq, OpenRouter and Mistral; Google only if Google Drive is used for exports), which the user must review separately.

Version 1.0.7 — as of November 2026

Summary.

1. Scope and endpoints

AI API, AI desktop app and MCP server on the left, the IRONSTICK Client in the middle, data vault with AES-256, IRONSTICK Server and scan app on the right

In-app external AI calls go to the provider the automatic cascade is using at that moment. The user can set up up to four providers; the providers for which a key has been entered are used in this fixed order, lowest cost first: Qwen (Alibaba Cloud) → Kimi (Moonshot AI) → ChatGPT (OpenAI) → Claude (Anthropic). At every program start IRONSTICK checks which of them respond. If a provider fails, the same request goes to the next one. The failed provider is retried after a waiting time that depends on the error; it is skipped for the rest of the day only when its credit is used up or the cause is unknown. The content transmitted is identical on every provider (section 3 onwards: pseudonymised by the router, consent, audit log). The endpoints are:

Free background providers (optional). In addition, the user can store the free offers of Groq, OpenRouter and Mistral. IRONSTICK uses them exclusively for tasks that run in the background: e-mail triage, Data Consistency Monitor, daily briefing, dialogue summary, speaker assignment in transcriptions, retrieval of statute texts and situation report. Each of these providers has its own on/off switch in the configuration; it is used only if a key is stored and its switch is on. They are never used for the chat, for pleadings or for the Red/Blue Team review. If none of them is available, the cascade described above takes over. Pseudonymisation, consent and audit log follow the respective task (section 4). The endpoints are:

Free offers — notice in the configuration. In the configuration, a notice below each of these providers points out that IRONSTICK — provided the API key is stored and the switch is on — uses it for background tasks such as summaries and e-mail triage and, in doing so, transmits data to that provider. Before switching any of these providers on, check whether its terms provide the data-processing agreement required for processors and meet your professional rules. A provider that is switched off is not used.

Three configurable model tiers are used per provider (small / medium / large). A separate, optional channel is the desktop-AI bridge (section 4.9): there, data flows into the user's own local desktop AI (Claude Desktop / Claude Code, ChatGPT Desktop, Qwen Desktop or Kimi Desktop), i.e. to that AI's provider (Anthropic, OpenAI, Alibaba Cloud/Qwen or Moonshot AI/Kimi) under the user's own subscription/account with that provider. The bridges may run in parallel: each desktop AI has its own small bridge program, all of them connect to the same local endpoint in the running application, and they can work on the same case simultaneously. No case or personal data is sent to the software vendor. The only vendor contact is a plain download of a news file from www.ironstick.legal (after start-up and every six hours, section 7), which carries no data apart from the technical connection itself. IRONSTICK SERVER (section 9) does not change this: it is operated by the law firm itself, on the firm's own hardware, inside the firm's own network — it never contacts the vendor and never contacts any AI provider.

The master switch is the user's own access. In-app external AI processing exists only if the user has opened their own account with an AI provider and entered their own access key in the configuration. Without any provider set up, no in-app external AI call can occur at all — every feature described in section 4 then stays local or is simply unavailable. That account is a direct contract between the user and the provider; IRONSTICK is not a party to it. The same applies to the desktop-AI bridge, which requires the user's own subscription/account with the chosen desktop AI provider (Anthropic, OpenAI, Alibaba Cloud/Qwen or Moonshot AI/Kimi). Documents marked secret are excluded from the bridge's and the chat's tools, from the AI instruction package and from every generated output (attachments, dossiers, exports); their processing during capture follows the user's deliberate choice at capture time (section 4.1).

Fully local (nothing leaves the machine): text extraction and OCR, the deterministic local chat layer, global search, relevance radar, letter-chain analysis, dossier/PDF generation, the redaction finder's local pass, speech recognition (transcription of recordings), and the building of the AI instruction package.

2. The pseudonymisation layer

Every in-app call through the central AI router is pseudonymised by default: identifiers in outgoing text are replaced with tokens, and the answer is restored locally. If the pseudonymiser cannot be built completely, nothing is sent. The exceptions are listed in 2.3. The mapping lives only in memory, one fresh mapping per operation; it is never stored.

Top: IRONSTICK Client, anonymised figure with gears, AI API; bottom: IRONSTICK Client, user, AI desktop app

2.1 What is replaced

SourceFieldsToken family (internal identifiers)
Client recordsname, national ID number from the ID field (e.g. Romanian CNP), phone, e-mail, address and city $PARTEI_A$ (party), $CNP_A$ (ID number), $TEL_A$ (phone), $MAIL_A$ (e-mail), $ADRESSE_A$ (address)
Persons / entitiesfull name (person or company), national ID or company number from the ID field (e.g. Romanian CNP or CUI) $PARTEI_B$ (party) / $FIRMA_A$ (company), $CNP_B$ (ID number)
Casescase number, opponent, claimant $FALL_A$ (case), $PARTEI_C$ (party)…
Pattern layer (unknown values in free text) court file numbers, personal identification numbers, IBANs, e-mail addresses and phone numbers. Other national ID numbers are replaced only if they are stored on the client or person record.same token families

2.2 What deliberately stays real

2.3 Deliberate clear-name exceptions

3. Consent moments and the audit log

Calls routed through the central router are consent-gated and logged: each model round writes a row to the local audit table with the complete request and response in the tokenised form that actually left the machine; refused or blocked attempts are logged without content. Where a function asks for consent, the dialog states model tier and approximate request size, and one approval covers the current screen session (for document capture: the current program run).

Router flows without a consent dialog of their own: e-mail triage (in background operation and on a manual fetch in the e-mail screen alike, section 4.2), the Data Consistency Monitor's analysis run (4.5), the daily briefing (4.4a), the dialogue summary of the API chat and the Red/Blue Team review (4.7), and the redaction AI finder (enabling its toggle is the consent). These are still pseudonymised (except the redaction finder's intended clear-name answers) and still audited.
Flows that bypass the router: the word processor's AI functions, read-aloud preprocessing and the File→Markdown AI correction call the API directly. They are pseudonymised (exception: read-aloud), but they show no consent dialog of their own and write no audit-log rows. The user's operation of these features (pressing the AI button, starting a generation, starting read-aloud with the AI toggle on) is the consent moment.

4. The data flows, use case by use case

4.1 Document capture

Text extraction and OCR are local. If an API key is configured, IRONSTICK asks once per program run, then up to four call types run (all pseudonymised, all audited):

4.2 E-mail monitor (triage)

Case assignment is done locally and without AI. New mail is fetched in the background at start-up and then every five minutes. An e-mail whose case the local recognition already identifies (case number, letter number, client number or reference to an own submission) causes no AI call. For every other e-mail, one small-tier call assesses the urgency, with exactly: sender name and address, subject, and the stored preview snippet as plain text (hard-capped) — never the full body, no attachments and no case list. Answer: priority and reasoning. If free background providers are switched on (section 1), this call may run through them. No consent dialog is shown, neither in background operation nor on a manual fetch in the e-mail screen: the triage runs automatically once a mail account and an AI provider are set up. Pseudonymised and audited.

No tracking pixels. Opening a mail in the monitor never contacts the sender's server: images referenced by an internet address (including invisible tracking pixels) are not loaded and appear as placeholders with a notice, so the sender cannot learn when, how often or from which address a mail was read. Only images embedded in the mail itself are displayed.

4.3 Person analysis (web research)

Three stages, after a once-per-session consent:

The result is stored locally with reliability "unconfirmed". The related autofill buttons on the person/institution forms likewise send the typed name in clear text (documented exception).

4.3a Public-source party check

The public-source check of a party is a fixed procedure the application runs itself when a connected AI calls it with name, city, district, country and the kind of party (natural person or legal entity):

The result is returned to the calling AI as a prepared, unverified profile. Nothing is written into the master data: every finding passes the review gate of the Data Consistency Monitor (section 4.5) and is adopted only when the user accepts it. Only publicly accessible sources are evaluated.

4.4 Daily log

The screen itself is local. Importing free-form text runs a local parser first; only when no daily-log format marker is found does an AI fallback normalise the raw text: the pasted text is sent completely, small tier, consent-gated, pseudonymised, audited. Stored daily-log entries leave the machine only as tool results of the chat or the desktop-AI bridge (capped excerpts) or inside the AI instruction package (section 5).

4.4a Daily briefing

On the first program start of a day (Windows), IRONSTICK prepares a spoken daily briefing in the background, already during start-up and before the briefing window asks whether the user wants to hear it. The briefing text — deadline counts, today's and tomorrow's court dates with case number, client name, city and court, and the titles of today's appointments — is sent once (small tier) to the cloud AI, which rewrites it as spoken prose in the system language. Pseudonymised through the router, audited, no consent dialog. If free background providers are switched on (section 1), this call may run through them. Without an available provider, a locally assembled text is used instead.

4.5 Data Consistency Monitor

Phase 1 (e-mail ↔ master data) is fully deterministic. Phase 2 sends one small-tier call per new inbound document (pseudonymised, audited, no dialog) containing: the de-duplicated contact-region snippets (short excerpts around address, phone and tax details) from the full text of that document, the party names of that document and of its case, and, for each party, the names of possible matches from the stored master data (tokenised where in the dictionary; institution names in clear text). Contact data and ID numbers from the stored master data are not transmitted. If free background providers are switched on (section 1), this call may run through them. The answer only ever becomes a suggestion that the user must accept in the monitor.

4.6 Word processor (AI assistance in the text)

None of the word-processor calls shows a separate consent dialog or writes audit-log rows (router bypass, section 3).

4.7 Red/Blue Team review and dialogue summary (API)

Two further API flows belong to drafting. Red/Blue Team: if the user has switched it on for the active provider (switch next to the API key; a saved key is required), every formal document handed over through the delivery dialog — from the in-app chat and from the desktop-AI bridge alike — is read once more by the same provider as opposing counsel in a separate review pass (medium tier). Transmitted: the draft text, the date and the case's jurisdiction; pseudonymised through the router and audited like every router call; no consent dialog — the switch is the consent; the reviewer's report is attached for the user. The Red/Blue Team review never runs through the free background providers (section 1). Dialogue summary: in long API-chat sessions the older part of the dialogue (only the user's questions and the model's final answers, never tool results) is condensed by the active provider (small tier, background, no consent dialog of its own) into a short summary that replaces the raw history; it is stored encrypted in the scratch store and overwritten each time. Pseudonymised and audited. If free background providers are switched on (section 1), the summary may run through them.

4.8 AI chat (external, API)

Consent once per chat session; medium tier with automatic escalation to the large tier (the whole context is then sent again); pseudonymised; every round audited. Each turn transmits: the system prompt (static rules), the live GUI context (current screen, open case/client incl. client name — tokenised), up to 10 AI-memory entries of the open client, the most recent dialogue plus a summary of older turns (4.7) and the list of the chat's scratch files. Every tool the model calls returns its result into the API conversation — including document full texts (larger results are stored in the encrypted scratch store), e-mail bodies and daily-log excerpts. The chat uses the same tool layer and the same delivery gates as the desktop-AI bridge (4.9): pleading verification, Red/Blue Team (4.7) and hand-over through the export dialog — what leaves the system is a submission-ready template. The local chat layer answers routine requests without any transmission.

Two utility functions deserve explicit mention. The weather lookup fetches current weather data for a named place from the non-LLM service Open-Meteo (section 7) — only the place name / its coordinates are transmitted to that service, never case or person data. The location lookup answers exclusively from the most recent locally stored security snapshot (section 8): the AI's request triggers no new external lookup — it only reads what is already on disk. As with every tool, what these functions return flows back into the AI conversation, i.e. to the AI provider.

4.9 Desktop-AI bridge (optional add-on modules)

Each desktop-AI access is an optional module, purchased separately. It exists only where the practice has acquired and installed the respective bridge module; without any module, the bridge section stays locked in the configuration, the local endpoint never starts, and none of the flows described in this section can occur. Bridges are available for Claude Desktop/Claude Code, ChatGPT Desktop, Qwen Desktop and Kimi Desktop; each has its own small bridge program, and all of them connect to the same local endpoint in the running application. The data flows below are identical for all; only the receiving provider differs.

This channel transmits real case data. That is its purpose: the user's own desktop-AI session drafts submission-ready templates and therefore needs real names and numbers.

4.10 Audio transcription (speaker assignment)

Speech recognition runs entirely locally; the recording itself never leaves the computer. If the user has specified more than one speaker, the AI then assigns the recognised lines to the speakers: section by section (medium tier), the recognised text, plus lines already assigned as context and the number of speakers. The calls run through the router — pseudonymised, subject to consent, recorded in the audit log. The answer must not alter the text: every line is checked against the recognised text; if a block fails, the transcript is taken over without speaker assignment. With only one speaker, no AI call takes place. If free background providers are switched on (section 1), these calls may run through them.

5. The AI instruction package (export ZIP)

IRONSTICK Client, user with MD files and ZIP archive, AI web app

Building the package is local and involves no AI call. It produces clear-text Markdown (no pseudonymisation) intended to be uploaded by the user to an external LLM of their choice. Content:

FileContent
Casesall cases of the selected client with parties, status and evidence-ID index (no full texts)
Entitiesall persons/entities of the entire practice (not only this client) including national personal and company ID numbers (e.g. Romanian CNP/CUI), date of birth, full contact data, profession, vehicle — plus the stored analysis blocks (assessment, vulnerabilities, residences, finances, social environment, sources)
Institutions, Deadlinesall institutions; active deadlines with case numbers and client name
Mailthe 100 most recent e-mails practice-wide: sender, recipient, subject, attachment file names, short snippet (no full bodies)
Daily loglast 10 days, practice-wide, including the case chronology of that window
Per caseone case file per case: the complete chronicle with document full texts, client and party identifiers including ID numbers; plus all case background notes uncapped
Instruction filesfive working-rule documents — no personal data
What happens when this ZIP is uploaded to a third-party AI service: the user personally transfers, in clear text, substantial parts of the entire practice — client identities with national ID numbers, third-party profiles including sensitive assessments, practice-wide correspondence metadata and case files — to that provider. From that moment the data is processed under that provider's terms (training use, retention, jurisdiction). IRONSTICK shows a privacy warning before the export (once per program run) and offers the export also to Google Drive, which additionally places the files with Google. The user acts as the transmitting controller under GDPR and must ensure a legal basis (e.g. Art. 6, professional secrecy rules) before uploading.

Documents marked secret are excluded from deadlines, daily logs and case files.

6. Summary matrix

FlowWhat leaves (form)PseudonymisedOwn consent dialogAudit log
Document capture (4 calls)OCR and document text (limited), case and name listsyesyes — once per program runyes
E-mail triage (manual fetch in the e-mail screen)sender, subject, short snippet (no case list); only for e-mails not assigned locallyyesnoyes
E-mail triage (background, every five minutes)sameyesnoyes
Daily briefing (API)briefing text: deadline counts, court dates with case number, client name, city and court, appointment titlesyesno (first start of the day, prepared during start-up)yes
Person research, stage 1real name (web search)no — by designyes — once per sessionyes (clear text)
Person research, stages 2 and 3page texts (limited per source)yessame consentyes
Person/institution autofilltyped name (web search)no — by designyes — once per sessionyes (clear text)
Daily-log AI importpasted raw textyesyesyes
Data Consistency Monitorper new document: its contact regions and names of possible matches (no contact data or ID numbers from master data)yes (institution names in clear text)no (throttled background)yes
Word processor: revise / structureselection with a context excerpt / document lines (limited)yesno (button = consent)no
Read-aloud preprocessingeach sentence, clear textnono (start = consent)no
Red/Blue Team review (API)draft text, date and jurisdictionyesno (switch = consent)yes
Dialogue summary (API)older dialogue turns (user questions and final answers only)yesno (background pass of the API chat)yes
File→Markdown AI correctionconverted textyesnono
Redaction AI finderalready-redacted text; answers contain third-party clear namesoff — by designtoggle = consentyes
AI chat (external)prompt, screen context, memory, most recent dialogue with summary, tool results (limited per item)yesyes — once per sessionyes
Desktop-AI bridge (Claude Desktop/Code, ChatGPT Desktop, Qwen Desktop, Kimi Desktop)raw tool results (full case data)no — by designyes — once per program run for all desktop AIsno (app side)
Audio transcription: speaker assignmentrecognised text in sections — never the recordingyesyesyes
Free background providers (Groq, OpenRouter, Mistral) — only when switched onthe same content as the respective background task; never chat, pleading or Red/Blue Teamas the respective taskno (switch per provider = consent)yes
AI instruction ZIPclear-text practice export (user-initiated upload)nowarning once per program runn/a

7. Non-LLM external services (for completeness)

IRONSTICK Client, internet, location symbol and weather symbol

Independent of any LLM, the following features contact external services with the minimum data needed: number validation (EU VIES, EORI, GLEIF, business registers — the number being checked), the person search's direct web queries (the name), IMAP (your mail server), and optional exports to Google Drive (the exported files). None of these involve the AI provider.

The following services are contacted in the background or with equally minimal data:

None of these services involves the AI provider.

8. Local storage, integrity and user control

IRONSTICK Client with TOTP access lock; documents, scratch store and database encrypted with AES-256

Independent of the AI channels above, the following applies to all data IRONSTICK holds:

Allocation of responsibility. Because IRONSTICK stores everything locally and transmits data only on the paths documented in sections 1–7 and 9 — including the background functions that run without a dialog of their own (sections 3 and 7) — the operator of the practice is the sole data controller: they choose the storage medium and its encryption, manage and retain backups, decide which AI functions are enabled, give or withhold each consent, and alone decide what is done with every document, export or backup the software produces. AI-generated content — drafts, summaries, assessments, classifications — is always a proposal on which the user decides. This document exists so that every one of those decisions can be made on full knowledge of the actual data flows.

9. IRONSTICK SERVER (optional, on the firm's own network)

IRONSTICK Server and IRONSTICK Client connected over the LAN; the server has no connection to the internet

Practices with several IRONSTICK workstations can operate the optional IRONSTICK SERVER — a coordination service running on the firm's own Synology NAS, inside the firm's own local network. For the purposes of this declaration the decisive facts are:

Annex — Model clause for your client privacy notice (proposal)

The following text is a drafting proposal that a law practice using IRONSTICK can copy into its own client privacy notice. It is written to be accurate to the data flows described above. It deliberately avoids citations of statutory articles so it can be pasted into notices of any structure.

Before you paste this — checklist for the lawyer:
  1. Have the data-processing agreement of every AI provider you have set up in place, name in the clause only the providers you actually use, and check the sentence on training and retention against the terms you actually signed. The clause covers the free background providers (Groq, OpenRouter, Mistral, section 1) only through the optional sentence in brackets there — switch them on only if their terms meet your professional-rule requirements, and delete the sentence if you do not use them.
  2. Keep the bracketed sentence about the AI workspace only if you really use the desktop-AI bridge (Claude Desktop/Code, ChatGPT Desktop, Qwen Desktop or Kimi Desktop); delete it otherwise.
  3. This clause covers the in-app flows described in this document. It does not cover the AI instruction package (section 5) — uploading that export to any AI service is a separate decision and will normally require the client's explicit consent.
  4. If you have disabled individual AI functions in the configurator, shorten the list of purposes accordingly — describe exactly what you use, no more.
  5. This is a drafting proposal, not legal advice. Have it reviewed against your bar's professional rules and local data-protection practice before use.

English (master)

AI-assisted case processing. Our practice uses the case-management software IRONSTICK, which includes AI-assisted functions. For these functions, selected data from your file may be transmitted to an external AI service provider (depending on availability: Alibaba Cloud, Moonshot AI, OpenAI or Anthropic, via their APIs), which processes it on our behalf under a data-processing agreement. We use these functions for: classifying and registering incoming documents, prioritising incoming e-mail, checking our records for inconsistencies, drafting and reviewing legal documents, and legal analysis and research. [Optional — delete if not used: For tasks that run in the background, such as prioritising incoming e-mail, checking our records and summaries, the free services of Groq, OpenRouter or Mistral may additionally be used; we checked their terms before switching them on.]

Protective measures. Before anything is transmitted, the software replaces the direct identifiers stored in our system — names, personal identification numbers, telephone numbers, e-mail addresses, postal addresses, case numbers and bank details — with neutral placeholders on our own computer. The table linking placeholders to real data never leaves our office, and the provider's answers are translated back locally. Only what the specific function requires is transmitted, within fixed size limits. A small number of functions technically require real data — for example public web research on a person's name, or the read-aloud function; we use these only through a deliberate individual action. [Optional — delete if not used: For drafting court documents we additionally use an AI workspace in which case data is processed without placeholder replacement; this channel is used only under our direct supervision.] Separately from the AI functions, the software sends postal addresses stored in our records — without names — to the public map service OpenStreetMap so that they can be shown on a map.

The provider. Under the provider's terms applicable to us, content transmitted through the API is not used to train AI models and is stored only for a limited period. Processing may take place outside the European Economic Area; in that case the transfer is protected by the safeguards agreed in our data-processing agreement with the provider. What the provider may do with the data is governed by that agreement — not by the AI's own discretion.

Your choice. Our professional duty of confidentiality remains unaffected: beyond what is described here, no data leaves our practice. The processing rests on the mandate you have given us and on our legitimate interest in handling your case efficiently and accurately. You may object to the use of the AI-assisted functions at any time; where feasible, we will then handle your file without them. You also retain all your statutory data-protection rights, including access, correction, deletion and complaint to the supervisory authority.

This declaration was derived from the application source code (pseudonymiser, external router, audit log, and each feature's transmission path) and reflects the shipped behaviour of version 1.0.7 (as of November 2026). Processing by the AI provider itself — retention, training use, sub-processors, jurisdiction — is governed solely by the provider's terms, in their current versions. The links to each provider's terms and privacy policy are also in the corresponding section of the AI configuration.

ProviderTerms and privacy
Alibaba Cloud (Qwen)alibabacloud.com/help/en/legal
Moonshot AI (Kimi)platform.kimi.ai/docs/agreement
OpenAI (ChatGPT)openai.com/policies
Anthropic (Claude)Commercial Terms of Service: anthropic.com/legal/commercial-terms; Usage Policy: anthropic.com/legal/aup; Privacy Policy: anthropic.com/legal/privacy
Groqgroq.com/terms-of-use
OpenRouteropenrouter.ai/terms
Mistrallegal.mistral.ai/terms/commercial-terms-of-service
Get in touch

Tobias Werren

IRONSTICK contact card (QR)Tobias Werren

Scan the code to save our contact card — phone, e-mail and website.

Feel free to contact directly via WhatsApp or Telegram — calls are welcome too. Spoken languages: German, English, Romanian.

Telegram

Message

Interested in IRONSTICK or a demo? Write to us.

Sending opens your e-mail program with the prepared message.

Your e-mail program is opening. Please send the message there.