Brenneck Pay / BG-Demo – Security Review
Callcompleted
Brenneck Pay · 25 Aug 2026 10:30
Brenneck Pay's security officer accepted EU transcription for the current setup, with two conditions open. Procurement asked what is needed to take the Enterprise order form forward, with signature pencilled for 7 Oct 2026.
What was said
What this says
As at Fri 9 Oct 2026Brenneck Pay's security officer accepted EU transcription for the current setup, with two conditions open. Procurement asked what is needed to take the Enterprise order form forward, with signature pencilled for 7 Oct 2026.
What happened: Theo Gallagher held the third security review with Sabine Kranz and Henrik Lorenz on 25 Aug 2026. Finding one was closed for the current configuration, finding two on the access history extract, and finding three as a Brenneck setting.
Customer view: Sabine accepts evidence, not assurances, and must show transcription stays in the EU under BaFin outsourcing rules. The export showed the EU region throughout since the change, but earlier jobs ran outside it.
Commercial: Henrik asked what he needs to take the Enterprise order form forward. The open proposal is £125k in total against £50k a year on Growth today, with signature pencilled for 7 Oct 2026.
Watch: Platform team confirmation and the data protection officer's review are both open. The evidence does not show whether the order form was signed.
Themes
As at Fri 9 Oct 2026Theme
Security review, Enterprise expansion
Importance
upsell
Sentiment
mixed
Voice
decision-maker
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Theo to get written confirmation from the platform team by Friday, naming the confirming role.
- Theo to send Sabine the draft summary first, with the two conditions marked as open.
- Matteo Ricci to take the order form date and terms up with Henrik.
Risks
As at Fri 9 Oct 2026- Earlier transcription jobs ran outside the EU region, and the data protection officer has yet to review that file.
- The platform team's written confirmation on enforced two-person approval is still outstanding.
- Sabine will object to any summary that says more than the evidence does, so open conditions must stay marked open.
Opportunities
As at Fri 9 Oct 2026- The Enterprise expansion proposal could move Brenneck Pay from Growth once the residency condition is met.
- A notification on the region setting, proposed to Sabine, would support her audit cycle and the account.
Transcript
Theo GallagherMorning, Sabine. Can you hear me all right? I've got you on the recording, so I think we're live.
Sabine KranzGood morning, Theo. Yes, I can hear you. Is Henrik joining? I saw he accepted the invitation.- Theo GallagherHe did, but he's not in the room yet. Shall we give him a couple of minutes, or would you rather start with the open items?
- Sabine KranzLet us begin. Henrik can catch up. I have a short list of open questions, as you know, and I would like to go through them in order.
- Theo GallagherOf course. Let me just say how I've got it on my side, so we're looking at the same page. This is the third and last session. There were three open findings at the end of the second session. Finding one is where call transcription is processed. Finding two is logging of BG-Demo support access to your environment. Finding three is how long those logs are kept and who can read them. The owner for one is our platform team, and I've been chasing them. Two and three are mine.
- Sabine KranzThat matches my register. Thank you. Then my first question is the one I have asked twice already. Where exactly is the data processed when a call recording is transcribed? This is a requirement, not a preference. Under the outsourcing rules BaFin applies to us, I must be able to show it stays in the EU.
Henrik LorenzSorry, sorry, I'm here. Morning both. My previous call overran. Please carry on, I'll keep my camera off and my ears on.- Theo GallagherMorning, Henrik. No problem at all, we've literally just started. Sabine, to answer you directly: transcription now runs in the EU region, inside your own Snowflake account, and I'd rather show you than tell you.
- Sabine KranzPlease do. I do not accept a verbal assurance, and you know that.
- Theo GallagherUnderstood, and I wouldn't want you to. I sent two exports to you yesterday afternoon. One is the region configuration for the transcription service, and the other is the processing log for your last batch of recordings. The export is dated 25 Aug 2026, so it's from this morning's run. Do you have both open?
- Sabine KranzOne moment. I have the first. The second is still in my quarantine folder, I think. Our mail filter does not like attachments from outside.
- Theo GallagherThat's fair. While you dig it out, I'll share my screen and walk through the same file. Can you see it?
- Sabine KranzYes. It is small, but I can read it.
- Theo GallagherI'll make it bigger. Right. Top block is the region setting. You'll see the processing region is set to the EU region, and the fallback behaviour is set to fail, not to reroute. That second point matters. If the EU region were unavailable, the job stops and waits. It does not quietly run somewhere else.
- Sabine KranzMm. That is the part I wanted. In the earlier session you said the fallback was under review. Is this the changed setting, or was it always so?
- Theo GallagherIt's the changed setting. Before the change, transcription could be routed outside the region under load. That was the substance of finding one, and I'd rather say it plainly than dress it up. The change went in after the second session, and the config history in the export shows the date of the change and who approved it.
- Sabine KranzWhere in the file is that?
- Theo GallagherScroll to the bottom block, the change history. Three entries. The last one is the fail setting. The approver is named by role, platform engineering lead, and there's a second approval from our security function.
- Sabine KranzI see it. This is helpful. But a configuration file shows intent. It does not show behaviour. Now the second export, please. I have found it.
- Theo GallagherYes. That's the processing log. Each line is one recording batch: the job identifier, the region it ran in, start and finish. Have a look at the region column all the way down.
- Sabine KranzGive me a moment. I am reading it properly, not skimming.
- Sabine KranzAll entries show the EU region. No exceptions in this export. But the export covers only the period since the change. What about before?
- Theo GallagherGood question, and I'd rather not oversell it. The log for the earlier period exists, and it does show some jobs that ran outside the region. I've included that in a separate file so you have the full picture and can decide what, if anything, you need to notify. I can't make that call for you.
- Sabine KranzThat is correct, and I appreciate that you volunteered it. I will need that file reviewed by our data protection officer. It does not change the finding for the present configuration, but it must be on record.
- Henrik LorenzCan I just check something, for my own understanding? Does that earlier period affect the contract? I don't want to be surprised later.
- Sabine KranzHenrik, I will keep to the security side. Contractual consequences are yours. I will tell you what my officer concludes.
- Henrik LorenzFine. Understood. I'll hold the question until she has done that.
- Theo GallagherThat's sensible, and if it helps, Henrik, I'll flag it to Matteo on our side so it's not sitting only with the technical team. He owns the commercial relationship.
- Sabine KranzThen on finding one. For the present configuration, I have evidence of the setting and evidence of behaviour. I would like one more thing: a statement, signed, that the setting cannot be changed by support staff without a second approval.
- Theo GallagherLet me be careful here. The change history shows two approvals were required for this change. Whether the platform tooling enforces two approvals on every future change is a question for our platform team, and I won't answer for them from memory. I'll get it in writing from them. Can I commit to that by end of the week?
- Sabine KranzYes. Please state it as a dated commitment, in the email, with the name of the role that confirms it.
- Theo GallagherHere is the dated commitment, then: by Friday, written confirmation from the platform team on whether two approvals are enforced by the tooling, with the confirming role named. If the answer is that it's process only, not enforced, I'll say so, and we'll talk about what that means.
- Sabine KranzGood. Then finding one: closed for the current configuration, with the earlier-period file going to my data protection officer, and the approval statement outstanding as a condition. I will write that in the register exactly like that.
- Theo GallagherThat's a fair record of it. Shall we move on to finding two, the support access logging?
- Sabine KranzYes. My question: when a BG-Demo engineer accesses our environment to resolve a ticket, is each access logged, with who, when, why, and what was touched?
- Theo GallagherYes, and again I'll show you. This is the support access log extract, taken from your Snowflake account's access history, so it isn't a BG-Demo-held record that we could tidy. It's yours, and we simply read it. Every row has the user, the role they assumed, a timestamp, the ticket reference and the objects queried.
- Sabine KranzHow many support accesses have there been in the period?
- Theo GallagherIn the window covered by the extract there was a single support session. It matches the one ticket you raised in the last month, the sync question. I can show you the row. Ticket reference, engineer, start, end, objects touched.
- Sabine KranzPlease do.
- Theo GallagherThere. The engineer used the support role, read access only, and touched the connector status tables and nothing in the merchant data schemas. The session closed about twenty minutes after it opened.
- Sabine KranzAnd if the engineer had needed merchant data? What would the log show?
- Theo GallagherIt would show a different role, and that role needs a grant from your side. We don't hold standing access to the merchant schemas. So an access like that would have two traces: your grant and the access row. I can evidence that in the role definitions, which are in the third file.
- Sabine KranzI see the role definitions. Standing access is none. Time-boxed grant only. This is acceptable. Now, finding three. Retention of these logs, and who can read them. Where are the logs stored, and for how long?
- Theo GallagherThey sit in your account, so retention follows your own Snowflake settings, not ours. We don't copy them out. Our side only reads, and only the people holding the support role can do so. If you want a longer retention than the default, that's a setting you control, and I'd suggest you align it with whatever your own regulator expects.
- Sabine KranzThat is the correct answer. It is also the answer I hoped for. We keep these for the period our policy requires, and I will confirm the setting myself. Then that finding is not a BG-Demo finding but a Brenneck task. I will close it on your side with a note.
- Theo GallagherThank you. Can I ask that the note says the evidence was the role definitions and the access history extract, so anyone reading the register later knows what it rested on?
- Sabine KranzThat is how I write all of them. A finding without its evidence is not closed.
- Henrik LorenzCan I come in now, or shall I wait? It's only a process question.
- Sabine KranzPlease. I have completed my list, apart from the confirmation from the platform team.
- Henrik LorenzRight. So from where I sit, what do I need before I can take the Enterprise order form forward? We're on Growth today, forty users, fifty thousand a year. The proposal in front of me is the expansion, one hundred and twenty-five thousand in total. We had pencilled 7 October 2026 for signature. I want to know if that date is still realistic from the security side.
- Sabine KranzFrom the security side, if the approval statement arrives this week and my data protection officer has no objection to the earlier-period file, I will recommend that the residency condition is met. I will put that in writing to you, Henrik. The rest is yours.
- Henrik LorenzThat's all I need. Theo, anything on your side that would stop us hitting that date?
- Theo GallagherOn the security evidence, no. The date for the order form and its terms is something Matteo will pick up with you, and Elena will be on the adoption side once it's signed. I'll give both of them a summary today, so nobody has to re-ask Sabine anything.
- Henrik LorenzGood. I'd rather not put Sabine through another round of the same questions.
- Sabine KranzI would not object. But I would object to a summary that says more than the evidence does.
- Theo GallagherUnderstood. I'll send you the draft summary first, Sabine, before it goes anywhere else, so you can correct it. And I'll mark the two conditions as open conditions, not as done.
- Sabine KranzThat will be satisfactory.
- Theo GallagherLet me read back what I have, so we leave with the same notes. One: finding one is closed for the present configuration, with two conditions, the signed approval statement from the platform team by Friday, and your data protection officer reviewing the earlier-period file. Two: finding two is closed on the strength of the access history extract and the role definitions. Three: finding three is closed as a Brenneck setting, which you'll confirm on your side. Have I missed anything?
- Sabine KranzNo. That is accurate. I would add that the closure is recorded as of today, with today's evidence, and I will review the transcription region again at the next audit cycle.
- Theo GallagherFair, and we'd expect that. Is there a way you'd like to be told, between now and then, if the region setting ever changed? We can set a notification on the config.
- Sabine KranzYes. That would be useful. Please include that in your email as a proposal, and I will tell you which mailbox.
- Theo GallagherWill do. I'll put it in as a proposal and not as something already in place.
- Henrik LorenzThanks both. That was less painful than I expected, if I'm honest.
- Sabine KranzIt was the third session, Henrik. The painful part was the first.
- Theo GallagherFair point, and thank you for the patience over the three sessions, Sabine. I know it took more of your time than either of us planned.
- Sabine KranzThat is what the review is for. Please send the files again from a source my filter accepts. Use the shared secure folder rather than attachments.
- Theo GallagherI'll put everything in the shared folder this afternoon, with a short index so each file maps to a finding. Thanks, both. Speak soon.
- Henrik LorenzCheers. Goodbye.
- Sabine KranzGoodbye.
Callsmade from