Privacy notice

1. Who is responsible

The controller is Arbitrium — Bennett-Schaar und Ilsinger, a partnership under German civil law (Gesellschaft bürgerlichen Rechts), represented by Silvan Bennett-Schaar and Gregor Ilsinger. Our addresses are in our legal notice. You can reach us at kontakt@arbitrium.legal.

We have not appointed a data protection officer.

2. If you only visit this website

When you open a page, your browser sends our hosting provider the data needed to deliver it, including your IP address, the date and time, the address requested, the amount of data transferred and your browser’s identifier. We use this data to deliver the pages and to keep the service secure. Our lawful basis is our legitimate interest in a secure, working service (Article 6(1)(f) UK GDPR).

Several entry points are protected against misuse. For this, your IP address is counted in memory for a short time; it is not stored permanently.

3. Cookies and storage on your device

We store only what the service strictly needs, so we do not ask for your consent (regulation 6 of, and paragraph 4 of Schedule A1 to, the Privacy and Electronic Communications (EC Directive) Regulations 2003).

• arbitrium_pforte, a cookie that remembers that a valid access code was entered. It lasts twelve hours.
• arbitrium_verfahren, a cookie that remembers that the key to one particular case was shown, and opens only that case. It lasts fourteen days.
• The insurer’s case list, kept in the browser storage of the insurer’s own device (see section 6).
• arbitrium-hinweis-cookies, a note in your browser storage that you have seen the cookie notice, so that it does not appear on every page.

The two cookies are signed for our server, cannot be read by JavaScript and are not sent to other websites. None of these items contains an identifier for you as a person.

4. What we do not do

We use no analytics or audience measurement, no tracking pixels, no advertising networks and no social media plug-ins, and we do not profile you. The fonts on this site are served from our own server, so viewing a page creates no connection to Google.

5. If you ask for a demo

We show you the demo in person. If you write to us for one, we use your details only to answer your request and to arrange a time with you. Our lawful basis is our legitimate interest in establishing a business relationship (Article 6(1)(f) UK GDPR).

Until 22 September 2026 the demo could be opened on the page for insurers by giving a work email address. We stored those addresses with the time. We send marketing emails only if you ticked the box to agree at the time (Article 6(1)(a) UK GDPR). You can withdraw that consent at any time with effect for the future; a short message to us is enough.

6. If you take part in a procedure

In a procedure you describe an accident and name your evidence. This can include personal data such as the names of people involved and of witnesses, places and times. Our lawful basis is carrying out the procedure that you started or accepted (Article 6(1)(b) UK GDPR). You do not have to take part, but without your account the procedure cannot go ahead.

What you submit goes to the other party in the procedure, usually the insurer who invited you, and you see what they submit. At the end, both sides receive the same assessment. The assessment decides nothing: it is not binding, and each side decides for itself whether to settle.

Encryption

Your case is encrypted in your browser and stored only in encrypted form. The key is the part of the invitation link after the # sign. Browsers do not send that part of an address to the server, and we do not store it. We only see a check value of the key, which shows that someone holds it.

This has two consequences. We cannot read the content of a procedure. And if you lose your link, you lose access to the procedure, because we cannot restore it.

The insurer’s case list

When an insurer starts or opens a procedure, it appears in the insurer’s case list. That list is kept only in the browser storage of the insurer’s own device: for each procedure the case number, the key, the insurer’s reference and, if the insurer enters it, the claimant’s name. We do not receive these details. To show the status, the list asks us about each case using its number and the check value of the key, just as when a link is opened. If the insurer clears its browser data, the list is empty.

Assessment by a language model

To break an account down into individual statements and to prepare the assessment, the text is passed to a language model. Before that, your browser replaces the email addresses and phone numbers it recognises with placeholders; this option, “Hide contact details”, is switched on by default. The link between placeholder and original never leaves your device.

In accounts written in German, the browser also replaces names and addresses. In accounts written in English it replaces names, addresses, postcodes, vehicle registration numbers, dates, National Insurance numbers, claim numbers and bank details. It does this by recognising patterns, so it is not a guarantee: a town on its own, or a spelling it does not expect, can remain in the text. Please still give only the details the case needs. You are Party A and the other driver is Party B; no names are needed.

Dictation, photo and map

If you dictate, you use your browser’s speech input. Chrome sends the recording to Google for this, Safari to Apple; we only receive the finished text. If you upload a photo of your accident report form, the image is sent to the language model to be read. Names and number plates on the photo cannot be hidden. We do not keep the image, only the text read from it, inside the encrypted procedure.

The sketch on the map uses map images and the place search of OpenStreetMap. The OpenStreetMap Foundation in the United Kingdom sees your IP address, the map area and your search term. Only the points of your sketch are stored, encrypted in the procedure.

Evidence files

If you attach a file to an item of evidence, such as a photo of the damage or an invoice, your browser encrypts it with the key of the procedure. Only the encrypted file is stored, and we cannot read it. The other party to the procedure can open it. So that the file counts in the assessment, your browser also sends it to the language model, which checks whether it supports the allegation. Names on photos and in documents cannot be hidden. The file is kept for as long as the procedure is stored and is deleted with it.

Witness statements

If you name a witness, you receive a link to pass on. Whoever opens that link sees only the point in question, not the procedure. We do not verify who that person is. They give their name, where they were and what they saw; their browser encrypts this with a key of its own that exists only in that link and in the procedure. Only the encrypted statement is stored, and we cannot read it. Both sides of the procedure can read it. It can be changed only within 15 minutes of first being sent, and not afterwards. So that the statement counts in the assessment, one party’s browser also sends it to the language model, which checks whether it supports the allegation and whether it rests on what the witness saw themselves; names in it are hidden beforehand. The statement is kept for as long as the procedure is stored and is deleted with it.

7. Who processes data for us

• Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA, which runs the website and stores the encrypted procedures with their evidence files and the email addresses from the former demo access.
• Anthropic PBC, San Francisco, USA, which provides the language model that reads the accounts, the photos of accident report forms and attached evidence files.

8. Where your data goes

Pages are delivered through a location in Frankfurt am Main, Germany. The application’s functions and the storage of encrypted procedures run in a data centre in Washington, D.C., in the United States. The language model also runs in the United States. Your data therefore leaves the United Kingdom.

What leaves differs a great deal. The case file reaches storage only encrypted and without the key. The language model receives the text of an account, with the placeholders described in section 6. A simple page visit carries the connection data needed to deliver it.

9. How long we keep data

An encrypted procedure stays stored until it is deleted. This includes its earlier versions: every save is kept, encrypted, in the procedure’s history so that no change is lost unnoticed, and is deleted with it. We delete it on request; tell us its case number, which starts with VGL followed by six characters. We cannot see the content when we do so. We delete email addresses from the former demo access after twelve months or, where you gave consent, when you withdraw it. Our hosting provider deletes its server logs according to its own schedule.

10. Your rights

Under the UK GDPR you have the right to

• access the data we hold about you (Article 15),
• have inaccurate data corrected (Article 16),
• have your data erased (Article 17),
• have processing restricted (Article 18),
• receive your data in a portable form (Article 20),
• object to processing based on our legitimate interests (Article 21),

and to withdraw a consent at any time. Write to kontakt@arbitrium.legal. Where a procedure is stored encrypted, we cannot tell you what it contains, because we cannot read it; we can delete it.

Complaints

If you are unhappy with how we handle your data, please tell us first at kontakt@arbitrium.legal. You can also complain to the Information Commissioner’s Office (ICO), the UK’s data protection regulator, at ico.org.uk/make-a-complaint or on 0303 123 1113. The ICO asks for a copy of the complaint you made to us.

Because we are established in Germany and in Austria, you can also complain to the Berlin Commissioner for Data Protection and Freedom of Information or to the Austrian Data Protection Authority. Their addresses are in our German notice.