IT
Where does the instance run?
Self-hosted runs on your infrastructure. Managed Switzerland runs in Switzerland. A required-region deployment runs in the location agreed in the contract.
Thursday, 14:00 · The deployment review
Lea booked thirty minutes with the IT lead. He has a list. Where does it run, who can read what, can we get our documents out, and what happens to the text an AI model sees. None of it is unreasonable, and none of it can be answered with a shrug.

What he asked, in order
IT
Self-hosted runs on your infrastructure. Managed Switzerland runs in Switzerland. A required-region deployment runs in the location agreed in the contract.
Lea
Role-based access and database-level controls limit access. Restricted notes remain internal and are excluded from customer exports.
Security reviewer
Documents use Markdown and are stored in Postgres. Selected packs can be exported as Markdown and PDF.
Lea
No. The assistant is read-only. A human reviews and approves document changes.
IT
The provider and data-use terms must be named for the selected deployment before launch.
Evidence required before launch
Security reviewer
The managed-service sub-processor list will be published and kept current before launch.
Evidence required before launch

The sketch is ugly: boxes, arrows, three crossed-out lines and a smudge where a decision changed. That is fine. What matters is that by the end of it, both of them are looking at the same boundary instead of two different assumptions about it.
Use the contact form and mark the request as a security question.

Lea can carry on with the evidence work. IT can inspect the agreed location and controls whenever it wants. The two items without evidence yet stay marked as open, because a compliance product that quietly glosses over its own gaps is not worth buying.