Lyvor›Operations
Operations & accountability
Control is not a feature. It is the contract.
This page answers the questions that come up before every rollout — from management, from the IT provider, and from the person who is responsible for the inbox each morning. No absolutes — and the limits are stated plainly.
Data protection
Three facts your IT provider will check first.
Germany, DPA, full list of service providers
Lyvor’s system components run on servers in Germany; only pseudonymized content is sent for AI analysis. Which service providers are involved is set out in the data processing agreement (DPA) — disclosed in full.
Pseudonymized before analysis
Names, addresses, and contact details are pseudonymized using a substitution method before the AI analysis begins; its effectiveness is checked on an ongoing basis.
Your data stays in your system
The inbox remains in your own Microsoft 365 tenant. Lyvor works in draft-only mode inside the existing inbox — with no new software for your team and no externally exposed interface.
Roles & approvals
Who decides what.
Your team
Reviews, corrects, approves, sends. Every draft waits for human approval — the last click stays with your team.
Lyvor (system)
Sorts, prepares, follows up. Triggers no payments, makes no commitments, changes no inbox rules. Anything unclear stays visibly open.
Lyvor (operator)
Builds, runs, and takes personal responsibility for the system. Corrections from day-to-day operation are fed back in — usually the same day. No call center, no ticket system.
Outage & continuity
“What happens if Lyvor is gone tomorrow?”
It is a fair question — Lyvor is a founder-run business. The answer is architecture, not reassurance:
Your mail never depends on us
Your emails arrive unchanged in your own inbox — with or without Lyvor. If the system goes down, you lose the sorting — not your mail.
No data held hostage
The system runs in your own Microsoft 365 account; the data stays with you. There is nothing Lyvor could hold back.
Documented handover
At the end of the contract: full return of data and a documented handover within 14 days — contractually agreed on request. You can cancel at any time.
Open operational questions? Ask the person who builds it.
DPA, permissions, review paths — bring your IT team into the conversation. Technical details on the integration are on the Microsoft 365 page.