Legal documents¶
calServer ships three legal documents that are reachable without signing in: the imprint, the privacy notice and the accessibility statement. They appear in the footer of the sign-in page and of the open portal.
They are maintained under Administration → Basic settings → Legal.
Why before sign-in¶
The same idea applies to all three, for different reasons:
- An imprint behind a sign-in is not a service provider identification. Section 5 DDG requires the details to be "easily recognisable, directly accessible and permanently available".
- A privacy notice has to be available at the moment data is collected — and that is already the sign-in.
- An accessibility statement behind the login misses exactly the people it is written for. Anyone who fails at the sign-in should learn there whom to contact.
What is shipped¶
Every document has a German and an English version. German is authoritative; if the English one stays empty, the application shows the German version to English-speaking users as well, rather than serving an empty page.
What ships are templates, not finished texts. They contain placeholders in
square brackets ([Company name], [Postal code] [City], [date]) that the
operator has to replace.
The templates are publicly visible from the first minute
A fresh installation shows the templates in the footer — placeholders included. That is deliberate: a document that only exists once somebody thinks of it usually does not exist. The "Legal" tab counts on its label how many texts still carry placeholders and lists them above the form. That number belongs at zero before going live.
The accessibility statement template is the only one that is nearly complete in substance: it describes the actual state of the application including its known limitations (charts, dashboard tiles, signature field, uploaded documents) and only leaves the operator and contact details open. Anyone who has customised the interface should check it against their own installation.
Switching a document off¶
If a document is not needed — an internal installation without an imprint obligation, say — delete the German text completely and save. The link then disappears from the footer and the address answers with 404. The German version is the switch here: it decides for English too.
The difference between "never touched" and "deliberately emptied" rests on whether it was saved. As long as nothing is saved, the template applies; a saved empty text switches the document off.
Where the texts live¶
The content sits in the settings store (property, group settings/legal), one
row per document and language:
| Document | Key (German) | Key (English) |
|---|---|---|
| Imprint | legal_imprint_de |
legal_imprint_en |
| Privacy notice | legal_privacy_de |
legal_privacy_en |
| Accessibility statement | legal_accessibility_de |
legal_accessibility_en |
The templates ship as files in the source tree under
laravel/resources/legal/<document>.<language>.html and are updated with the
application. A text that has already been maintained is not overwritten.
Interface¶
Two public endpoints, both without a token:
GET /api/v2/public/legal?lang=en # list for the footer
GET /api/v2/public/legal/{slug}?lang=en # one document with its text
slug is imprint, privacy or accessibility. Besides the text, the
response names the language the text is actually in — the page sets it as the
lang attribute, so a screen reader does not read a German text with English
pronunciation.
Notes on maintenance¶
- No link to the EU dispute resolution platform. The ODR platform was shut down on 20 July 2025; older imprint templates still point at it. The statement under section 36 VSBG (participation in an arbitration procedure) is unaffected.
- Connected services belong in the privacy notice. The template describes a self-hosted installation. Email delivery through a provider, AI features or external interfaces are recipients within the meaning of Article 13 GDPR and have to be added.
- The accessibility statement carries a date. It has to be reviewed regularly, and it belongs updated after any substantial rework of the interface.
Not legal advice
The templates are a scaffold following the customary structure, not a reviewed document for a specific operation. Whether further details are needed in an individual case — regulatory authority, professional law, processing on behalf, special categories of data — is a question for the operator's legal counsel.