Data residency and where your work runs
Teams with regional or regulatory requirements ask three questions early, and they deserve straight answers before anything else: where does our data sit, where does the processing happen, and what copies do you keep. Here is how Lyrion is built to answer them.
The short version is that your data stays yours, and we keep as little as possible.
Your systems stay the system of record
Lyrion works against the tools you already have. The account lives in your CRM, the conversation in your inbox, the invoice in your billing system. The agent reaches into those, acts, and writes back. It does not require you to move your data into ours to be useful.
That is a deliberate architectural choice, not just a compliance convenience. The whole product is designed to make your existing systems do more, which means your data does not have to relocate for the agents to work.
Processing and where it happens
The reasoning an agent does has to happen somewhere, and for teams with residency requirements, where is not a detail. Lyrion is built so that the processing location is a configuration you set to match your obligations, not a default you have to accept and hope is acceptable.
When a review asks where processing occurs, the answer is a setting you chose and can point to, not an assurance about someone else's infrastructure you have to take on faith.
We keep no copy we do not need
The most reassuring answer to “what do you retain” is “as little as possible.” Lyrion keeps the audit trail that makes it safe and does not hoard copies of your customer data beyond what the work requires. The record of what an agent did is not the same as a warehouse of your data, and we keep the former, not the latter.
Retention is configurable and inspectable. You can see what is kept and for how long, and the honest default is that the answer is small.
Answers you can show, not assurances
The theme across all three questions is the same: the answers are configuration and record, not promises. Where data sits, where it is processed, and what is retained are all things you set and can demonstrate in a review, rather than things you have to trust a vendor about.
That is the standard a regulated team should hold any agent product to. If the answers to residency questions are marketing sentences rather than settings you control, that is the problem to solve before anything else.
How we would start
One queue, approvals on, one week of reading the log every morning. If reading the log starts to feel like a formality, widen the scope a notch. If it does not, the log will point at the exact place the agent needs better instructions or a tighter set of tools.