Sensitive data
What is stored, what is not, and what you can switch off.
A Swiss company, a stated list of who processes what and where, and a model that is built to say when it does not know. That last part is not marketing: in administrative work, a confident wrong answer costs more than a slow one.
Submissions, reports, a consultation with forty responses.
Grouped by what people actually argued, with the sentence each grouping rests on.
Every claim carries where it came from, so the next person can check it without asking you.

A Swiss deployment exists and serves business accounts - own server, own contract, nothing leaving the country. The standard plans do not run there: the application server is in New York and the models run in the EU and the United States. We name both rather than letting the first imply the second.
Summarise these forty submissions to the consultation by position, and quote the sentence each summary rests on.
Medium or Large, depending on how much of the answer has to hold up in writing.
Compare the sizesOn a business account, in Switzerland - own server, own contract. On the standard plans, in New York and the EU, named by country on the imprint page.
No. Not on any plan, and not by the companies that operate the models - they process on our instructions and for no purpose of their own.
Conversations stay until you delete them. Payment records are kept ten years, because Swiss accounting law requires it.
What is stored, what is not, and what you can switch off.
Looks things up, and names what it read.
Counts the rows instead of describing them.