Theo Gallagher

Brenneck Pay / BB-Demo – Security Review

Callcompleted

Brenneck Pay: documents logo Brenneck Pay: documents · 2026-08-25 10:30

Third 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 was said

What this says

Current to 11 Oct 26

Third 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.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Security review and Enterprise move
Importance
upsell
Sentiment
positive
Voice
decision-maker

Who 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

  1. Theo Gallagher
    Theo Gallagher None
    Hello, can you hear me all right? I'm just sorting out my headset.
  2. Sabine Kranz
    Sabine Kranz None
    Good morning, Theo. Yes, I hear you clearly.
  3. Theo Gallagher
    Theo Gallagher None
    Good morning. Is Henrik not on yet?
  4. Sabine Kranz
    Sabine Kranz None
    He wrote to say he is finishing another call. He will join in a few minutes.
  5. Theo Gallagher
    Theo Gallagher None
    No problem at all. How's the week been? It's been properly warm here in London.
  6. Sabine Kranz
    Sabine Kranz None
    Warm here also. The air conditioning in our building has failed, so we are all very productive and very uncomfortable.
  7. Theo Gallagher
    Theo Gallagher None
    Ha. 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?
  8. Sabine Kranz
    Sabine Kranz None
    Yes. I have my open questions in front of me, if you would like to begin with yours first.
  9. Theo Gallagher
    Theo Gallagher None
    Sure. 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.
  10. Sabine Kranz
    Sabine Kranz None
    That 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.
  11. Theo Gallagher
    Theo Gallagher None
    Understood, and that distinction is the right one. Can I share my screen? I'd rather show you than tell you.
  12. Sabine Kranz
    Sabine Kranz None
    Please do. And please provide the evidence also in writing afterwards. A verbal explanation is not sufficient for my file.
  13. Theo Gallagher
    Theo Gallagher None
    Of course. That's the plan. Give me a moment, I'm just finding the window. Right. Can you see a configuration export?
  14. Sabine Kranz
    Sabine Kranz None
    I see a text file with a header and a list of settings. It is small. Could you make it larger?
  15. Theo Gallagher
    Theo Gallagher None
    Sorry, yes. Is that better?
  16. Sabine Kranz
    Sabine Kranz None
    Better. Thank you.
  17. Theo Gallagher
    Theo Gallagher None
    So 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.
  18. Sabine Kranz
    Sabine Kranz None
    I 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?
  19. Theo Gallagher
    Theo Gallagher None
    Fair, 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.
  20. Sabine Kranz
    Sabine Kranz None
    Scroll, please. Slowly.
  21. Theo Gallagher
    Theo Gallagher None
    Sure.
  22. Sabine Kranz
    Sabine Kranz None
    Mm. And before the change went live? You have the earlier period in the same log?
  23. Theo Gallagher
    Theo Gallagher None
    I 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.
  24. Sabine Kranz
    Sabine Kranz None
    Thank you for saying it plainly. That is useful. This was a requirement, not a preference. It was a condition of our signature.
  25. Theo Gallagher
    Theo Gallagher None
    Yes. I know. It's in the review notes from the first session.
  26. Sabine Kranz
    Sabine Kranz None
    Next question. The audio and the transcripts that are produced. And any derived data, the indexes, the embeddings. Where do those live?
  27. Theo Gallagher
    Theo Gallagher None
    All 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.
  28. Sabine Kranz
    Sabine Kranz None
    I would like the object list, yes. And I would like it dated.
  29. Theo Gallagher
    Theo Gallagher None
    It'll be dated. I'll include it in the pack.
  30. Sabine Kranz
    Sabine Kranz None
    One more on this point. Temporary files. When a job runs, is there a staging area, and is it in the same region?
  31. Theo Gallagher
    Theo Gallagher None
    Good 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.
  32. Sabine Kranz
    Sabine Kranz None
    Please do. That I would like in writing also.
  33. Theo Gallagher
    Theo Gallagher None
    Noted. I've put it on my list.
  34. Sabine Kranz
    Sabine Kranz None
    Then, subject to the written evidence, I am satisfied with finding one. I will not close it until I have the documents, you understand.
  35. Theo Gallagher
    Theo Gallagher None
    Completely. That's how it should work.
  36. Henrik Lorenz
    Henrik Lorenz None
    Hello, hello. Sorry, so sorry, the previous call overran. Have I missed much?
  37. Sabine Kranz
    Sabine Kranz None
    Good 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.
  38. Henrik Lorenz
    Henrik Lorenz None
    Good, 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.
  39. Theo Gallagher
    Theo Gallagher None
    Ha, no pressure then. Sabine, shall I go on to finding two?
  40. Sabine Kranz
    Sabine Kranz None
    Yes. 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?
  41. Theo Gallagher
    Theo Gallagher None
    Okay, 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.
  42. Sabine Kranz
    Sabine Kranz None
    The approval. Who gives it?
  43. Theo Gallagher
    Theo Gallagher None
    Your 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.
  44. Sabine Kranz
    Sabine Kranz None
    And if the administrator is not available? Is there a route around it?
  45. Theo Gallagher
    Theo Gallagher None
    No. 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.
  46. Sabine Kranz
    Sabine Kranz None
    That 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?
  47. Theo Gallagher
    Theo Gallagher None
    This 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.
  48. Sabine Kranz
    Sabine Kranz None
    Read the last part again, please. About the export.
  49. Theo Gallagher
    Theo Gallagher None
    Your 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.
  50. Sabine Kranz
    Sabine Kranz None
    Good. 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?
  51. Theo Gallagher
    Theo Gallagher None
    Here 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.
  52. Sabine Kranz
    Sabine Kranz None
    Hm. 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?
  53. Theo Gallagher
    Theo Gallagher None
    I 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.
  54. Sabine Kranz
    Sabine Kranz None
    That 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.
  55. Theo Gallagher
    Theo Gallagher None
    Will do. I'll put the control reference next to each statement so you can map them to your questionnaire.
  56. Henrik Lorenz
    Henrik Lorenz None
    Can 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?
  57. Sabine Kranz
    Sabine Kranz None
    That 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.
  58. Henrik Lorenz
    Henrik Lorenz None
    Right. Right, good. That's clear. Thank you.
  59. Sabine Kranz
    Sabine Kranz None
    Theo, one last item on finding two. Retention. How long are session rows kept?
  60. Theo Gallagher
    Theo Gallagher None
    I 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.
  61. Sabine Kranz
    Sabine Kranz None
    Thank you. That is a correct way to handle it. I prefer a missing answer to an invented one.
  62. Sabine Kranz
    Sabine Kranz None
    So. 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?
  63. Theo Gallagher
    Theo Gallagher None
    That's complete, and I agree with every part of it. Nothing I'd add or take away.
  64. Sabine Kranz
    Sabine Kranz None
    Then 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.
  65. Henrik Lorenz
    Henrik Lorenz None
    Brilliant. Thank you, Sabine. Thank you, Theo. That's the answer I wanted.
  66. Theo Gallagher
    Theo Gallagher None
    Thanks, both. And thanks for the patience over three sessions. The questions were the right ones, and the transcription change happened because of them.
  67. Sabine Kranz
    Sabine Kranz None
    That is why we ask them.
  68. Henrik Lorenz
    Henrik Lorenz None
    Can 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.
  69. Sabine Kranz
    Sabine Kranz None
    Thank you, Henrik. I will leave that part of the call to you and to Theo, and I will stay for the next steps.
  70. Henrik Lorenz
    Henrik Lorenz None
    So 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?
  71. Theo Gallagher
    Theo Gallagher None
    On 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.
  72. Henrik Lorenz
    Henrik Lorenz None
    That's fine. I'll message him this afternoon. And Elena? Should she be in the loop?
  73. Theo Gallagher
    Theo Gallagher None
    I'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.
  74. Henrik Lorenz
    Henrik Lorenz None
    Good. 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.
  75. Sabine Kranz
    Sabine Kranz None
    I 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.
  76. Theo Gallagher
    Theo Gallagher None
    Agreed, 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.
  77. Sabine Kranz
    Sabine Kranz None
    Thank you. If they are not happy with it, I would like to know why, in writing.
  78. Theo Gallagher
    Theo Gallagher None
    Understood.
  79. Henrik Lorenz
    Henrik Lorenz None
    Right. Let me make sure I have the actions. Theo sends the pack. Sabine sends the closure note. I talk to Matteo this afternoon.
  80. Theo Gallagher
    Theo Gallagher None
    That'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.
  81. Sabine Kranz
    Sabine Kranz None
    By 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.
  82. Theo Gallagher
    Theo Gallagher None
    Yes. If something is missing, I'll say so at the top of the email.
  83. Sabine Kranz
    Sabine Kranz None
    Good. Then I have no further questions.
  84. Henrik Lorenz
    Henrik Lorenz None
    Nor me. Thank you both. Honestly, that was more straightforward than I feared.
  85. Theo Gallagher
    Theo Gallagher None
    Helps that the questions were so specific. Thanks, Sabine, thanks, Henrik. Speak soon.
  86. Sabine Kranz
    Sabine Kranz None
    Goodbye, Theo. Goodbye, Henrik.
  87. Henrik Lorenz
    Henrik Lorenz None
    Bye, both. Stay cool, Sabine.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only