Trust
Trust and security
Lynus prepares the case and shows the sources, but a person always reviews and signs. Every step of the case is logged in an audit log that cannot be changed, and your rules run as a control on every step. Here we answer the questions data protection officers, IT security and lawyers ask.
How does a case move through Lynus?
A case moves through Lynus in fixed steps. The AI reads the case, does the research and shows the source for every claim. Then your rules run as a control, and anything that breaks them is stopped and logged. Finally the caseworker reviews the case and signs with name and time.
- Case in · application with attachments
- Case read · 14 pages
- Research · 6 sources
- Roles and authority · Brønnøysund Register Centre
- Rules check · 1 deviation stopped by a rule
- Reviewed and signed · [Name]
Where is the data stored?
Lynus stores the original documents on disk and the text extracted from them in a Postgres database. Both run on a server at Hetzner, set up with Coolify. Which country and region the data is stored in during a pilot, and what applies to personal data, is not confirmed on this page yet.
[BEKREFT] Draft, not confirmed yet
Which AI model does Lynus use, and where does it run?
Lynus currently uses a language model from Anthropic, behind its own interface in Lynus so the provider can be changed. The plan is to move to Azure OpenAI in the Sweden Central region before Lynus processes real personal data. Which model and region apply to your pilot is not confirmed yet.
[BEKREFT] Draft, not confirmed yet
What is logged?
Lynus stores the events in the case in an audit log that can only be added to: the database rejects changes and deletions. Each run also stores which version of the AI instructions was used, and every claim shows the source it rests on. The signature is logged with name and time.
- Events in the case
- The events in the case are stored in a log that can only be added to. The database rejects changes and deletions.
- Instruction versions
- The version of each instruction is frozen into the run and the log.
- Sources
- Every claim shows the source it rests on.
- Rules check
- Every deviation from the rules, stopped and logged before the caseworker sees the case.
- Signature
- Who reviewed and signed, and when.
How does the rules layer work?
In Lynus every step of the workflow is checked against your rules before the case moves on. An instruction is a hope. A rule is a control. Anything that breaks the rules is stopped and logged before the caseworker sees the case, so the deviation stays in the log and does not disappear into an AI assessment.
Who makes the decision?
A person, always. Lynus prepares the case, shows the sources and flags deviations, but the assessment belongs to the caseworker. The caseworker goes through the case and signs with name and time, and the signature is stored in the log with the rest of the case. Lynus makes no decisions on its own.
Built to the AI Act’s requirements for logging, transparency and human oversight
Documentation
- DPIA basis Planned
- Risk assessment (ROS) basis Planned