See
See every agent action.
Activity, timelines and records.
Leyn turns your policies into controls for AI agents, so your people stay in charge as agents scale.
One rulebook in. One record out.
Align
Your policies, direction and governance documents, turned into controls. Each control points to the passage and version it comes from.
Guard
Every action is checked in up to three layers: a fast deterministic filter, then models that flag and decide in real time, then a review of the whole task.
How deep the checks go depends on the agent’s tier.
Escalate
Most actions pass. When a layer flags one, Leyn routes it, holds it or stops it.
The case reaches a named person from your delegation matrix, with alternatives and their impact on cost, risk and value.
Assure
One signed record per decision, written the moment the rule is applied: rule, passage, version, outcome, who decided.
Scale agentic workflows on your organization’s own knowledge and expertise.
Risk management for agentic AI: runtime controls built from your own policies and processes.
Filter at speed and see what matters.
Keep cost, risk and direction in check.
See
Activity, timelines and records.
Align
Each check traced to your own documents.
Guard
Every action checked against your controls before it takes effect.
Assure
A record of every decision, ready for audit.
Every action has a name, a purpose and a cost.
A defined task, and the resources granted to complete it.
Checked against each action taken to complete the task.
What was delivered, and at what cost.
Each control is set per task and per run, from documents you already hold.
How it works
Build turns your documents into observable rules. Run applies them to every agent action as it happens.
Build
Leyn reads your direction, constraints and governance documents.
Leyn proposes: you approve.
Direction, constraints and governance, mapped in one knowledge graph.
Each obligation becomes a rule stated as what an agent can be seen to do.
Observable rulesOutput of Build, input to Evaluate.
Run
Selection: based on scope and risk, the tier and rules that apply to the agent.
Telemetry from every tool call and MCP call.
L1 · L2 · L3
07Each action is checked against the rules: deterministic checks, probabilistic models and LLM as judge. Leyn judges the whole task across steps and systems, and confirms what changed in the target system’s own logs.
Three layers, extent of monitoring depends on tier.
The first two layers keep the third, and routing, rare.
Most actions pass. When a layer flags one, Leyn routes it, holds it or stops it.
Three roles, three views.
The people who own the policies or agents decide whether an action is in or out of bounds.
Accountable for an agent or a policy.
Runs the agent.
Knows the field the rule covers.
The part of Leyn that sees your agents’ traffic runs in your cloud or on your premises. Agent traffic and customer data stay inside your Data Boundary.
Your Data Boundary · cloud or premises
Agents
Built in-houseLangChain · n8n · UiPath
From vendorsCopilot · ChatGPT · Gemini · Claude
Data Plane
Your people
Desktop · Phone
Tools
SAP · Salesforce · StripeSlack · Jira · Snowflake
Agent traffic and customer data stay inside
Control Plane
Hosted outside
Reached from inside your infrastructure
Shown with agents and tools common in enterprise estates.
Leyn is a Stockholm-based company building controls for agentic AI, so people and agents work toward the same goals.
Company
Leyn AI AB is a Stockholm-based company building controls for agentic AI, so people and agents work toward the same goals.
Built in Stockholm for enterprises and regulated operators.
AI aligned to people, and to the values and objectives of our customers. People and agents working toward the same goals, with each decision traceable to the direction and the rules that set it. Leyn is how an organization’s own policies, direction and governance become controls for its agents, and how the people accountable stay in control: they set what agents must follow, decide when they escalate, and can stop them.
A compliance operator and two AI engineers, and family and friends before that. Agents do more of the work. People still answer for it. We started Leyn to connect the two.
CEO
“Compliance and risk management will have to run at agent speed. What we are solving is how to keep people involved enough to stay in control.”
About
Ian is an inventor on a filed patent for privacy-preserving biometric identification. He worked with Microsoft distinguished engineers on key management for confidential computing. At ASSA ABLOY he built the Responsible AI policy, directives, standards and guidelines. Before that, he was Lead Data Protection Officer at Vattenfall and set the strategic direction across all countries and business areas.
CPO
“Governance isn’t the brake on agents. Control is what lets you scale them.”
About
Aurora builds AI systems for enterprises and takes them through governance to production. At ASSA ABLOY she has designed and built agentic pipelines and retrieval systems for group-wide use, and shaped their architecture for EU and US regulatory requirements. She has led technical governance: privacy impact assessments, data sovereignty reviews that changed how systems handle and retain data, and the compliance checks each AI initiative passed before go-live. Before that, she was a technical project manager delivering e-commerce and payment platforms for startups. Her academic background is in Computer and Systems Sciences (M.Sc. Stockholm University).
CTO
“We build supervision and steering for agents, so the wider organization can see, understand and control what they do.”
About
Samuel builds, deploys and runs AI agents and applications in production at ASSA ABLOY, covering the full stack from infrastructure and backend to CI/CD and security, with a focus on safety, observability and efficiency. He holds an M.Sc. in Machine Learning from KTH, where his academic work on fine-tuning and evaluating large language models has been cited in later research.
We deliver relevant data for critical decisions.
We build to fit our customers’ technology roadmap.
We decide on evidence.
We make it simple.
Tell us what your agents do and which rules they must follow. We will show you how Leyn checks them.
Company
Tell us what your agents do and which rules they must follow. We will show you how Leyn checks them.
Legal
This notice explains what personal data Leyn AI AB collects, why, on what legal basis, who it is shared with, how long it is kept, and what rights you have. It covers this website, the research forms and interviews we run, and messages you send us.
If you only want the short version: we do not track you on this website, we only hold personal data you choose to give us, we ask for your consent before we use it, and you can withdraw that consent at any time by emailing trust@leyn.ai.
Leyn AI AB ("Leyn", "we", "us") is the controller for the personal data described in this notice. That means we decide why and how it is processed.
| Legal entity | Leyn AI AB |
| Swedish company registration number | 559601-3903 |
| Registered address | Hagaesplanaden 61, 113 68 Stockholm, Sweden |
| Privacy contact | trust@leyn.ai |
| Website | https://leyn.ai |
We have not appointed a Data Protection Officer. We are not required to under Article 37 GDPR: our core activities do not consist of large-scale regular and systematic monitoring of individuals, nor large-scale processing of special-category data. Privacy questions go to trust@leyn.ai and are answered by a named person at Leyn.
Leyn is established in Sweden, so no Article 27 representative is required.
This website does not use analytics, advertising, tracking pixels, or non-essential cookies. We set no cookies that require your consent, and there is no cookie banner because there is nothing to consent to.
The site is served through Cloudflare, Inc., which acts as our processor for content delivery and protection against attacks and abuse. To do that, Cloudflare processes technical connection data — including your IP address, the page requested, timestamp, and browser user-agent string — and may set a strictly necessary security cookie (__cf_bm and/or cf_clearance) to distinguish human visitors from automated traffic.
We run a product-research program with people working at organizations that deploy AI agents. It has two parts: a multiple-choice form sent ahead of time, and a short conversation.
What we collect
| Category | Details |
|---|---|
| Contact and identification | Your name and work email address. We do not ask you to name your employer, though a work email address will usually indicate where you work |
| Role information | Your role category and your relationship to AI agents at your organization (the answers to items B1 and B2) |
| Your organization's practice | Your answers about how your organization deploys, oversees, and budgets for AI agents — approximately 26 multiple-choice items, all of them optional except the first routing question |
| Free text | Anything you choose to write in an optional "Other (please specify)" field |
| Interview record | Notes taken during the conversation, and — only if you separately agree — an audio or audio-video recording and its transcript (see 2.3) |
| Scheduling | Calendar invitation and related email correspondence |
Purpose. To understand how organizations govern AI agents, so that we can decide what to build and how to describe it. Answers are analyzed alongside those of other participants.
Legal basis. Article 6(1)(a) GDPR — your consent, given when you submit the form and, separately, before any recording. Consent is our basis for the form, the interview, the analysis, and any follow-up contact about the research or about Leyn's product.
You can withdraw your consent at any time, for any part of it, by emailing trust@leyn.ai. Withdrawal does not affect the lawfulness of processing carried out before you withdrew. On withdrawal we delete your responses, notes, and any recording, unless you ask us to keep the answers in anonymized form.
Is it obligatory? No. Participation is entirely voluntary. There is no statutory or contractual requirement to take part, and no consequence if you decline, skip questions, or stop midway. Every item on the form is optional except the first, which determines which questions you are shown. A skipped item is recorded as blank.
What we ask you not to send us. Please do not include in free-text fields: personal data about other identifiable individuals, confidential or commercially sensitive information your employer has not cleared, or any special-category data under Article 9 GDPR (health, political opinions, trade union membership, and so on). We do not seek any of this and will delete it if we receive it.
The conversation is not recorded by default.
If other people are present on the call, each of them is asked separately and their answer is respected.
If you email us, we process your name, email address, and whatever you write. If you use the contact form on this website, we process your name, work email address, your function and your primary interest. We do this for the purpose of replying and keeping a record of the exchange. Legal basis: Article 6(1)(f) GDPR — our legitimate interest in responding to people who contact us. We keep correspondence for up to 24 months after the last message, unless it forms part of a contract or a legal record.
| Recipient | Role | What they process | Location |
|---|---|---|---|
| Microsoft Ireland Operations Ltd (Microsoft Azure) | Processor | Form responses, interview notes, transcripts, recordings | Azure West Europe region (Netherlands) |
| Google Ireland Ltd (Google Workspace) | Processor | Email you send us, including contact form messages; invitation and scheduling email, calendar entries, video meeting | Google Workspace EU data region |
| Cloudflare, Inc. | Processor | Website connection data (section 2.1); contact form messages, which are passed on by email and not stored | Global edge network, including outside the EU/EEA |
Access within Leyn is limited to the people who need it: the interviewers and the small team analyzing the results. Every processor is engaged under a written data processing agreement meeting Article 28 GDPR.
We do not disclose personal data to any other third party, except where we are legally required to do so, or where it is necessary to establish, exercise, or defend a legal claim.
Form responses and interview records are stored in the EU. However, Microsoft, Google, and Cloudflare are US-headquartered groups, and limited access from outside the EU/EEA can occur — principally for technical support, incident response, and abuse prevention. Cloudflare's edge network processes website connection data, and passes on contact form messages, outside the EU/EEA by design.
Where such a transfer takes place, it is protected by:
You may request a copy of the relevant safeguards by emailing trust@leyn.ai.
| Data | Retention |
|---|---|
| Form responses, interview notes, transcripts | 12 months from the date of the interview; or, if no interview takes place, 12 months from the date you submitted the form |
| Audio or video recording | Deleted once the transcript or notes are finalized, and in any case within 12 months |
| Your name and email address | Deleted with the rest of your record at 12 months, unless you have separately asked to stay in touch |
| Anonymized and aggregated findings | Retained indefinitely. These contain no personal data and cannot be linked back to you |
| Correspondence | Up to 24 months after the last message |
| Record of your consent, and of any withdrawal | For as long as needed to demonstrate compliance, and no longer than 24 months after the underlying data is deleted |
Deletion is permanent and includes backups, on the backup rotation cycle, within 90 days.
We apply measures appropriate to the risk, including: encryption in transit (TLS) and at rest; access limited to named individuals on a need-to-know basis; multi-factor authentication on all accounts holding personal data; logging of access to research records; and a documented process for handling a personal data breach, including notification to the Swedish Authority for Privacy Protection within 72 hours where Article 33 GDPR requires it, and to you where Article 34 requires it.
This website and our research are directed at people acting in a professional capacity. We do not knowingly collect personal data from anyone under 18. If you believe we have, email trust@leyn.ai and we will delete it.
Under the GDPR you have the right to:
How to exercise them. Email trust@leyn.ai. We respond within one month of receiving your request, extendable by two further months for complex requests, in which case we tell you within the first month and explain why. There is no charge, unless a request is manifestly unfounded or excessive. We may ask for information to confirm your identity, and we use it only for that purpose.
How to complain. If you are unhappy with how we have handled your data, please tell us first — we would rather fix it. You also have the right to lodge a complaint with a supervisory authority, in the EU/EEA member state of your habitual residence, your place of work, or the place of the alleged infringement. Our lead authority is:
Integritetsskyddsmyndigheten (IMY) — the Swedish Authority for Privacy Protection Box 8114, 104 20 Stockholm, Sweden +46 (0)8 657 61 00 · imy@imy.se · https://www.imy.se
Participants in Norway may contact Datatilsynet (https://www.datatilsynet.no). A full list of EEA authorities is published by the European Data Protection Board at https://edpb.europa.eu/about-edpb/about-edpb/members_en.
Where UK GDPR applies to you, this notice applies in the same terms, read with the UK GDPR and the Data Protection Act 2018. Transfers out of the UK rely on the UK International Data Transfer Addendum to the Standard Contractual Clauses, or the UK Extension to the EU-US Data Privacy Framework. You may complain to the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF (https://ico.org.uk).
We update this notice when what we do changes. The version number and date at the top tell you which version you are reading. If a change materially affects how we use personal data you have already given us, we contact you directly — and, where the change requires it, ask for your consent again rather than assuming it.
trust@leyn.ai — a person at Leyn reads it.