Fenmoor demo follow-up and your questions on data and security

Hi Callum, Thanks for your time on the demo today. It was good to see the brain working against a slice of your own submissions and bordereaux queries, and your underwriters' questions were exactly the ones that will make the difference. A quick recap of where we stand and what happens next: - You saw questions answered across submissions, claims tickets and CRM activity from one place. - You asked about how nightly data is refreshed and where the data physically lives. I've copied Tobias, our CTO and co-founder, because he is the right person to answer that properly rather than me paraphrasing him. - The expected decision date on our side is still 17 Jun 2024, so there is time to do this carefully. Could you send me the list of what your security and compliance colleagues will want to see? If Tobias has it early, he can answer in one go. To keep momentum, I'd like to get a working session in the diary with him this week or next. Best, Priya

Priya, What I need is three things answered in writing. 1. Dashboards must be right at 07:00. If the overnight refresh isn't finished, my team is quoting stale numbers to a capacity provider. By when is it complete, every business day? 2. Where does the data sit, and who can see it? That's a capacity-provider question and they will ask. 3. What happens when one of our source systems changes? We reshape bordereaux templates more often than I'd like. Please don't send me a general reassurance. I need specifics I can show my compliance people. Callum

Callum, Thank you - clear and fair. Taking your three in order, with Tobias adding the technical precision where it matters: 1. Refresh: the nightly refresh is complete by 07:00 your local time on business days. That applies on every tier, Growth included. 2. Data location: the brain is built and run inside your own Snowflake account, so your data stays within your own controls rather than being copied to us. Tobias will confirm exactly who has access and how, and I'd rather he put that in his own words. 3. Source changes: a connector that stops loading is the thing we watch for, and we'd want you to tell us ahead of any template change so we can plan around it. Tobias can cover how we handle it in practice. Tobias, would you reply to Callum directly on points two and three? I'd be grateful if you could include what the security team would need to see. Callum, once you have that, the next step is a short call with Richard so the commercials go to the board without surprises. Happy to make this easy. Best, Priya

Priya, Tobias's answer covers the data location and access. That's enough for my compliance people to start on. The source-change point is still thin. "We watch for it" isn't a process. I need to know who tells whom, and by when, if a bordereaux template changes. Come back to me with that in writing and I'll take it to Richard. Callum