What was said
What this says
Current to 11 Oct 26Third security review session: Sabine Kranz will close both open findings on receipt of written evidence. Henrik Lorenz needs the file closed before taking the £125,000 Enterprise proposal to signature.
What happened: Theo Gallagher took Sabine Kranz, Information Security Officer, through the third security review session, joined late by Henrik Lorenz, Head of Procurement. Sabine will close both open findings on receipt of the written evidence.
Customer view: Transcription for the tenant ran outside the EU before the change, which Theo confirmed plainly. EU residency was a condition of signature and Henrik said it stays one under Enterprise.
Commercial: Henrik described Growth today and an open proposal to move to Enterprise at £125,000. He needs the security file closed first; the working date was Wed 7 Oct 2026, and the call does not show whether it was met.
Watch: Staging clean-up behaviour and platform-side retention are still unconfirmed, and the new connector rule awaits the platform team. Order form timing sits with Matteo.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Theo Gallagher sends the written security evidence by the end of 25 Aug 2026, flagging any missing item at the top.
- Sabine Kranz sends her closure note to Theo and Henrik on receipt of the evidence.
- Henrik Lorenz speaks to Matteo that afternoon about order form terms and timing.
Risks
Current to 9 Oct 26- Closure depends on the written evidence arriving complete, with staging clean-up and platform-side retention still to be confirmed.
- EU residency is a condition of signature, so any new connector or feature must be region-checked before it goes live.
- The call does not show whether the working date of Wed 7 Oct 2026 for the order form was met.
Opportunities
Current to 9 Oct 26- The Enterprise proposal at £125,000 is open and the security file is the stated blocker to signature.
- A standing rule on region checks for new connectors can reassure the customer through the move.
Transcript
- Theo Gallagher NoneHello, can you hear me all right? I'm just sorting out my headset.
- Sabine Kranz NoneGood morning, Theo. Yes, I hear you clearly.
- Theo Gallagher NoneGood morning. Is Henrik not on yet?
- Sabine Kranz NoneHe wrote to say he is finishing another call. He will join in a few minutes.
- Theo Gallagher NoneNo problem at all. How's the week been? It's been properly warm here in London.
- Sabine Kranz NoneWarm here also. The air conditioning in our building has failed, so we are all very productive and very uncomfortable.
- Theo Gallagher NoneHa. Well, I'll try not to keep you in it for long. Shall we make a start and Henrik can catch up when he arrives?
- Sabine Kranz NoneYes. I have my open questions in front of me, if you would like to begin with yours first.
- Theo Gallagher NoneSure. So this is session three of three, and I'll list where we are. Two findings are open. Finding one is where the call transcription is processed. That's with me, with input from the platform team. Finding two is the logging of support access to your environment. That's also with me. The third one, the exit plan, we closed with you last session, so I won't revisit it unless you want to.
- Sabine Kranz NoneThat is correct. The exit plan is closed. Finding one and finding two remain open. For finding one, my question is unchanged: where exactly is the data processed? Not where it is stored. Where it is processed.
- Theo Gallagher NoneUnderstood, and that distinction is the right one. Can I share my screen? I'd rather show you than tell you.
- Sabine Kranz NonePlease do. And please provide the evidence also in writing afterwards. A verbal explanation is not sufficient for my file.
- Theo Gallagher NoneOf course. That's the plan. Give me a moment, I'm just finding the window. Right. Can you see a configuration export?
- Sabine Kranz NoneI see a text file with a header and a list of settings. It is small. Could you make it larger?
- Theo Gallagher NoneSorry, yes. Is that better?
- Sabine Kranz NoneBetter. Thank you.
- Theo Gallagher NoneSo this is the export of the transcription service configuration for your tenant, taken yesterday, and the date is in the header. The line I want you to look at is the processing region. It's pinned to the EU region, the same region as your Snowflake account. Below it is the routing rule, which has no fallback region. If the EU region is unavailable, the job waits. It doesn't run somewhere else.
- Sabine Kranz NoneI see the region line. I see no fallback entry. That is what I would expect to see if the statement is true. But a configuration shows intent. It does not show what actually happened. Where is the evidence of execution?
- Theo Gallagher NoneFair, and that's the next document. Let me switch. This is the job execution log for your tenant. Each transcription job has a start time, the region it ran in and the worker identity. I've filtered it from the day the change went live to yesterday. Every job shows the EU region. There's no other value in that column.
- Sabine Kranz NoneScroll, please. Slowly.
- Theo Gallagher NoneSure.
- Sabine Kranz NoneMm. And before the change went live? You have the earlier period in the same log?
- Theo Gallagher NoneI do, and I'll be straight with you about it. Before the change, transcription for your tenant did run outside the EU. That was your finding and it was right. If I take the filter off, you'll see the earlier jobs with the other region. The change date is where the column flips, and it matches the date in the change record I'll send you.
- Sabine Kranz NoneThank you for saying it plainly. That is useful. This was a requirement, not a preference. It was a condition of our signature.
- Theo Gallagher NoneYes. I know. It's in the review notes from the first session.
- Sabine Kranz NoneNext question. The audio and the transcripts that are produced. And any derived data, the indexes, the embeddings. Where do those live?
- Theo Gallagher NoneAll of it sits inside your own Snowflake account, in the EU region. That's the architecture for every customer: BB-Demo runs inside your account, so there's no separate BB-Demo store holding your content. I can show you the object list for the schema if you want it. It's the same account, same region.
- Sabine Kranz NoneI would like the object list, yes. And I would like it dated.
- Theo Gallagher NoneIt'll be dated. I'll include it in the pack.
- Sabine Kranz NoneOne more on this point. Temporary files. When a job runs, is there a staging area, and is it in the same region?
- Theo Gallagher NoneGood question. Let me check I answer it properly rather than from memory. Hold on. Right, the staging location is an internal stage in your account, so same region. And it's listed in the object list, so you'll see it there. I don't want to say more than that without the platform team confirming the clean-up behaviour, and I'll ask them.
- Sabine Kranz NonePlease do. That I would like in writing also.
- Theo Gallagher NoneNoted. I've put it on my list.
- Sabine Kranz NoneThen, subject to the written evidence, I am satisfied with finding one. I will not close it until I have the documents, you understand.
- Theo Gallagher NoneCompletely. That's how it should work.
- Henrik Lorenz NoneHello, hello. Sorry, so sorry, the previous call overran. Have I missed much?
- Sabine Kranz NoneGood morning, Henrik. We have covered the first finding. Theo has shown the region configuration and the execution log. I am waiting for the written pack.
- Henrik Lorenz NoneGood, good. Carry on, please, I'll listen. I'm only here because I'm told you two decide whether I can go back to the business with a yes.
- Theo Gallagher NoneHa, no pressure then. Sabine, shall I go on to finding two?
- Sabine Kranz NoneYes. Finding two. When a BB-Demo support engineer accesses our environment, I need to know who, when, to what, and on whose approval. Is that logged? Where is the log? Who can alter it?
- Theo Gallagher NoneOkay, I'll take those in order, because I think that's how you've written them. First, is it logged. Yes. Let me show you an extract. This is the support access log for your tenant. Each row is a session. You've got the engineer's identity, the start and end time, the scope of access, and the approval record.
- Sabine Kranz NoneThe approval. Who gives it?
- Theo Gallagher NoneYour own administrator. Support can't open a session on your environment unless one of your admins grants it, and the grant is time-limited. The grant is the row you see in the approval column, with the admin's identity.
- Sabine Kranz NoneAnd if the administrator is not available? Is there a route around it?
- Theo Gallagher NoneNo. There's no break-glass route for BB-Demo staff into your account. If your admin isn't available, support works from the diagnostics you can already see and waits. I'd rather say that than describe an emergency path that doesn't exist.
- Sabine Kranz NoneThat is acceptable. In fact it is better than I expected. Now the question of alteration. Who can change or delete a row in this log?
- Theo Gallagher NoneThis is the part where I'd have to ask, and I did. I asked the platform team yesterday, because I didn't want to answer it from the documentation alone. Let me read you their reply, and then I'll send it to you as it stands. They say the log is written by the platform, not by support, and support roles have no write or delete permission on it. Your own administrators can read it and export it.
- Sabine Kranz NoneRead the last part again, please. About the export.
- Theo Gallagher NoneYour administrators can read the log and export it. So you can take your own copy on whatever schedule you like and hold it independently of us.
- Sabine Kranz NoneGood. That is what I wanted to hear. I have a further question. What does a session row record about what the engineer did? The scope, or the individual actions?
- Theo Gallagher NoneHere is where I need to be careful not to overstate it. The row records the objects touched and the category of action, so read, or configuration change. It doesn't record the full text of every query. I'd rather you hear that from me now than find it later.
- Sabine Kranz NoneHm. For our purposes, objects and category of action is sufficient, provided that the access was granted for a limited time and for a stated scope. Query text would be preferable. Is it possible?
- Theo Gallagher NoneI can't promise that today. What I can say is that the query history sits in your Snowflake account, which you control, so the query text for any session window is available to you from your side. The two together, our session log and your query history, give you the full picture.
- Sabine Kranz NoneThat is a reasonable answer. It is correct that the query history is ours. I will note that this is how we will reconstruct sessions. Please include that statement in the written pack, with the control reference.
- Theo Gallagher NoneWill do. I'll put the control reference next to each statement so you can map them to your questionnaire.
- Henrik Lorenz NoneCan I ask a dumb question, just so I understand? Is this the thing where, if something went wrong, we could show BaFin who touched what and when?
- Sabine Kranz NoneThat is a fair question, Henrik, and not dumb. Yes. That is the purpose. Our outsourcing obligations require that we can show who accessed which system and under whose authority. The log, together with our own query history, is what we would present.
- Henrik Lorenz NoneRight. Right, good. That's clear. Thank you.
- Sabine Kranz NoneTheo, one last item on finding two. Retention. How long are session rows kept?
- Theo Gallagher NoneI don't have a retention period in the documentation I trust enough to quote. I won't guess it. What I can tell you is that you can export on your own schedule, so your retention is whatever you set. I'll ask the platform team for the platform-side figure and put it in the pack as a separate line, marked as theirs.
- Sabine Kranz NoneThank you. That is a correct way to handle it. I prefer a missing answer to an invented one.
- Sabine Kranz NoneSo. Let me summarise, so that we agree. Finding one: processing region is the EU, evidenced by configuration export and execution log, with the object list and the staging confirmation to follow in writing. Finding two: support access is logged, approval is by our administrator, there is no route around it, and the log cannot be altered by support. Retention, platform side, to follow as a separate line. Is that complete?
- Theo Gallagher NoneThat's complete, and I agree with every part of it. Nothing I'd add or take away.
- Sabine Kranz NoneThen I close both findings, on receipt of the pack. I will send a closure note to you and to Henrik, and I will place it in our file for the review.
- Henrik Lorenz NoneBrilliant. Thank you, Sabine. Thank you, Theo. That's the answer I wanted.
- Theo Gallagher NoneThanks, both. And thanks for the patience over three sessions. The questions were the right ones, and the transcription change happened because of them.
- Sabine Kranz NoneThat is why we ask them.
- Henrik Lorenz NoneCan I ask about what happens next, from my side? Sabine, I know you don't do the commercial side, so I'll keep it to the process.
- Sabine Kranz NoneThank you, Henrik. I will leave that part of the call to you and to Theo, and I will stay for the next steps.
- Henrik Lorenz NoneSo we're on Growth today, forty users, fifty thousand a year. The proposal on the table is the move to Enterprise, and the figure in it is £125,000. I need the security file closed before I can take that to signature internally. The date we've been working to is Wednesday 7 October 2026. Is that still realistic from your side, Theo?
- Theo Gallagher NoneOn the security side, yes. With Sabine's closure note, the file is complete for what we've reviewed. On the commercial terms and the timing of the order form, that's Matteo's, so I'd rather you took that with him than have me say something I can't stand behind. I'll tell him today that the findings are closed.
- Henrik Lorenz NoneThat's fine. I'll message him this afternoon. And Elena? Should she be in the loop?
- Theo Gallagher NoneI'll copy Elena on the pack, since she looks after the account day to day. She'll want to know the residency change is settled as well, because it affects how the team uses the transcription.
- Henrik Lorenz NoneGood. One thing I'll flag, because I know Sabine will say it if I don't. If we go to Enterprise, the EU residency stays a condition. Same as now.
- Sabine Kranz NoneI will say it regardless. It is a requirement, not a preference. And any new connector or any new feature that processes data must be checked for region before it is switched on. I would like that agreed as a working rule.
- Theo Gallagher NoneAgreed, and I'd suggest we write it down as a standing item rather than rely on anyone remembering. I'll add a line to the pack: before a new connector or feature goes live for Brenneck Pay, we confirm its processing region in writing to you. I'll check with the platform team that they're happy to commit to that wording, and I'll tell you if they aren't.
- Sabine Kranz NoneThank you. If they are not happy with it, I would like to know why, in writing.
- Theo Gallagher NoneUnderstood.
- Henrik Lorenz NoneRight. Let me make sure I have the actions. Theo sends the pack. Sabine sends the closure note. I talk to Matteo this afternoon.
- Theo Gallagher NoneThat's it. The pack will have: the configuration export, the execution log with the change point marked, the object list for the schema, the staging confirmation, the support access extract with the platform team's statement on write permissions, the platform-side retention figure as its own line, and the standing rule on new connectors. Each with a control reference and a date. I'll send it by the end of today.
- Sabine Kranz NoneBy the end of today is acceptable. If any item is late, please tell me which item and when, rather than sending the pack incomplete without comment.
- Theo Gallagher NoneYes. If something is missing, I'll say so at the top of the email.
- Sabine Kranz NoneGood. Then I have no further questions.
- Henrik Lorenz NoneNor me. Thank you both. Honestly, that was more straightforward than I feared.
- Theo Gallagher NoneHelps that the questions were so specific. Thanks, Sabine, thanks, Henrik. Speak soon.
- Sabine Kranz NoneGoodbye, Theo. Goodbye, Henrik.
- Henrik Lorenz NoneBye, both. Stay cool, Sabine.