Brenneck Pay / BB-Demo – Onboarding
Callcompleted
Brenneck Pay: documents · 2026-02-12 09:30
Onboarding call: Brenneck Pay's security officer asked for proof of EU residency and access controls. The database was created in their own account with no connectors on. The telemetry statement and connector review remain open.
What was said
What this says
Current to 11 Oct 26Onboarding call: Brenneck Pay's security officer asked for proof of EU residency and access controls. The database was created in their own account with no connectors on. The telemetry statement and connector review remain open.
What happened: On 12 Feb 2026 Jonas Albrecht ran the region check live and created the brain role, warehouse, database and three schemas in Brenneck Pay's own Snowflake account. No connectors are on.
Customer view: Sabine Kranz wants evidence, not assurance. She accepts residency for the database once the exports arrive, but the telemetry statement and connector review stay open.
Commercial: The forty Growth users wait behind her sign-off, so adoption depends on closing her points. Elena Novak has no date yet for the telemetry statement and promised one by the end of the week.
Watch: Jonas will not change production on a Friday, so connectors go live on a Tuesday at the earliest. Any addition to the first connector group goes to Sabine before it is switched on.
Themes
Current to 9 Oct 26Theme
EU residency and access evidence
Importance
neutral
Sentiment
mixed
Voice
unknown
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Elena Novak confirms the date for the telemetry statement by the end of the week.
- Jonas Albrecht sends the region export and the empty share list after the call.
- Laura Penhaligon sends the connector plan for the first group once Sabine Kranz has signed off.
Risks
Current to 9 Oct 26- The written statement on operational telemetry does not yet exist and BB-Demo has no date for it.
- No connector goes live until Sabine Kranz has reviewed it, which delays first value for the forty Growth users.
- Jonas Albrecht will not change production on a Friday, so go-live is a Tuesday at the earliest.
Opportunities
Current to 9 Oct 26- A second review of grants and access history after the first load gives a documented route to full sign-off.
- Forty Growth users can be mapped to roles once the two team groups are named.
Transcript
Laura Penhaligon NoneHello, can you hear me all right? I think I'm coming through, the little bar is moving anyway.
Jonas Albrecht NoneYes. Loud and clear.
Elena Novak NoneGood morning, Laura, good morning, Jonas. I can hear you both. Sabine, I see you have just joined, good morning.
Sabine Kranz NoneGood morning. Sorry, I was finishing something with the audit team. I am here now.- Laura Penhaligon NoneNo problem at all. It's properly grey over here, I don't know what it's doing where you are.
- Jonas Albrecht NoneGrey. Also wet. Frankfurt has committed to the theme.
- Elena Novak NoneAmsterdam is the same, so we are all in agreement. Shall we begin? As I wrote in the agenda yesterday, there are four items. To confirm: first, the region the brain will live in. Second, creating the database in Brenneck's own Snowflake account. Third, the roles and access, least privilege. Fourth, the evidence Sabine needs, and then the written actions.
- Sabine Kranz NoneBefore we start, I have my open questions, and I would like them on the record. One: where exactly is the data processed? Two: does anything leave the account, including the embeddings and any logs? Three: who at BB-Demo can see what, and where is that logged? I need these answered with evidence, please. This is a requirement, not a preference.
- Laura Penhaligon NoneThat's fair, and they're the right three. So the short version of how this works, and then we'll show it rather than just say it. The brain isn't a service in London that your data gets sent to. It's built and run inside your Snowflake account. The database, the tables, the compute, all of it sits in your account, in whichever region your account is in.
- Sabine Kranz NoneWhich is why I ask where the account is. I have the contract wording, I do not yet have the technical proof.
- Jonas Albrecht NoneI can answer that one. I checked the account when we signed. It is an EU region. But you said you don't accept verbal assurance, so let me run it live.
- Sabine Kranz NoneThank you. That is the correct approach.
- Jonas Albrecht NoneSharing my screen. You see the worksheet? Plain query for the current region and the account identifier. Running it now.
- Laura Penhaligon NoneYep, we can see it. Take your time.
- Jonas Albrecht NoneResult is back. Region is the EU region we agreed, in Frankfurt. Cloud region field, one row, no surprises. I'll export the output and the query text so it can go in the file.
- Sabine Kranz NonePlease include the timestamp on the export. And the account name, not only the identifier.
- Jonas Albrecht NoneIt has both. I'll check before I send.
- Elena Novak NoneAs agreed, I will make sure that the export is attached to the written summary, so the evidence and the actions sit in one place. Jonas, can I note that as an action for you?
- Jonas Albrecht NoneYes. After this call.
- Laura Penhaligon NoneGreat. So that settles the where. Now the what, which is the actual set-up. What I'd like to do today is create the brain's database in your account, in that region, with an empty schema and nothing loaded. No connectors yet, no customer data. Just the container, and the roles around it. Jonas, you'd run the statements, I'll talk you through them, and Sabine can watch each one.
- Jonas Albrecht NoneGood. I prefer it that way round. I run, you narrate. Which role has access to create databases at the moment?
- Laura Penhaligon NoneOnly whichever role you pick. We don't need your account admin role to be shared with us at any point. What we need is one dedicated role for the brain that owns the database and nothing else.
- Sabine Kranz NonePlease explain what nothing else means. Which objects, specifically?
- Laura Penhaligon NoneSpecifically: that one database, the schemas inside it, and a small warehouse for the brain's own queries. It has no rights on your payments data, none on your other databases. If we want it to read something later, say a merchant table, you grant that explicitly and it's visible in the grants list.
- Jonas Albrecht NoneGood. That is what I wanted to hear. So, new role first. I'll create it and give it a name that says what it is. Then the warehouse, extra small, auto suspend short.
- Laura Penhaligon NoneExtra small is plenty for set-up. We can revisit once data is flowing.
- Jonas Albrecht NoneRole created. Warehouse created. Now the database. Same region by definition, since it's in this account. Creating it.
- Sabine Kranz NoneI would like to see that the database exists in the account, in the catalogue, and not only that the statement returned successfully.
- Jonas Albrecht NoneFair. Listing databases. There. Owner is the new role, created a moment ago, the comment field says it is the brain. And no, it is not shared outside the account. I checked the share list as well, it is empty.
- Sabine Kranz NoneGood. Please keep that in the evidence too. The share list, empty, with the date.
- Elena Novak NoneI have noted it. That is item two done, to confirm, the database is created in Brenneck's own account in the EU region, and the share list is empty. Laura, you wanted to say something about the schemas?
- Laura Penhaligon NoneYes. Three schemas to begin with: one for the raw loads from each connector, one for the cleaned and joined layer, and one for what the brain serves to users. Keeping them apart means Jonas can tell at a glance what's raw and what's derived, and Sabine can scope access per layer.
- Jonas Albrecht NoneSensible. That is a schema change on my side but a clean one. Creating them.
- Jonas Albrecht NoneDone. Three schemas, all owned by the brain role. Nothing in them.
- Sabine Kranz NoneQuestion four. Who at BB-Demo will be able to log in to this account, and how? Please be precise.
- Laura Penhaligon NoneHonestly, nobody logs in as a person with standing access. For the set-up work I'll need a user in your account, and I'd suggest it's created by Jonas, time-limited, with only the brain role, and removed when the implementation is finished. Everything I do is then in your own query history.
- Jonas Albrecht NoneI do not grant access by email. If you want a user, we agree it in a ticket on our side, I create it here, and I set the expiry myself.
- Laura Penhaligon NoneThat works for us. Elena, can you raise that so it's written?
- Elena Novak NoneYes. I will make sure that the request is sent to Jonas in writing today, with the role name, the purpose and a proposed expiry, and he will approve or change it.
- Sabine Kranz NoneI would like multi-factor authentication enforced on that user. And the network policy applied. Please confirm both, in writing.
- Jonas Albrecht NoneBoth are account policy already. Any user I create inherits them. I will screenshot the policy settings. I would not tell you it is so without looking, so give me a moment.
- Sabine Kranz NoneOf course.
- Jonas Albrecht NoneLooked. Multi-factor is required for all users, network policy is attached at account level. One exception exists, a service user for our pipeline tooling, not related to this. I will mention it in the note so nobody is surprised.
- Sabine Kranz NoneThank you for volunteering it. I will want to see that exception documented. That is a finding I can close once I have the evidence.
- Laura Penhaligon NonePerfect. Can I take a few minutes on the end-user side, because that's the bit your merchant teams will care about? You've got forty users on the Growth licence, merchant account managers and merchant risk. At the moment only a couple of you are in, which is exactly what we'd expect at this stage.
- Jonas Albrecht NoneYes. Just me and a colleague who was testing login. The rest are waiting.
- Laura Penhaligon NoneRight, and they should wait. Nothing for them to ask until there's data. The order is: access model signed off by Sabine, then the first connectors, then a test with a small group, then the wider forty.
- Sabine Kranz NoneWhich connectors, and which systems do they read? I will need to know which personal data categories enter the brain. Merchant data is one thing, cardholder data is another.
- Elena Novak NoneTo confirm, that list is in the implementation plan I sent. The first group is the CRM, the helpdesk and the accounting system. Nothing that touches card data is in the first group. I will make sure that any addition goes to Sabine for review before it is switched on.
- Sabine Kranz NoneBefore it is switched on, not after. That is important to me.
- Elena Novak NoneUnderstood, and I will write it as a rule in the summary.
- Jonas Albrecht NoneOne thing from my side, timing. I do not change production on a Friday. So if the connectors go live, it is early in the week. Tuesday at the earliest, and only if Sabine has closed her points.
- Laura Penhaligon NoneThat suits us completely. We'd rather go on a Tuesday with a full week to watch the first nightly refresh than squeeze it in before a weekend.
- Sabine Kranz NoneNow the logs. Question three from my list. Where will I see what the brain role did, and for how long is it retained?
- Jonas Albrecht NoneAccount usage views. Query history and access history, both in your account, both readable by you. Retention is whatever the account has. I can show the access history view now, filtered on the new role. It will be thin, we only just made it.
- Sabine Kranz NonePlease show it. Thin is acceptable. Empty is acceptable. I want to know that the mechanism works.
- Jonas Albrecht NoneThere. Role creation, warehouse, database, three schemas, each with a timestamp and the user that ran it. That was me. And the empty share list check. All visible.
- Sabine Kranz NoneGood. That is what I wanted to see. I will ask for that query saved, so I can run it myself every month.
- Jonas Albrecht NoneI will put it in the documentation. It is the sort of thing I would hand to an auditor anyway.
- Laura Penhaligon NoneAnd from our side we'll write the same into the handover document, so it's not only in Jonas's head. Sabine, one thing I'd want to be careful about: you asked whether anything leaves the account.
- Sabine Kranz NoneYes. Embeddings, logs, telemetry. Everything.
- Laura Penhaligon NoneRight. The embeddings and the index are stored in the brain database, so they're in your account like everything else. What we do see on our side is operational information about the service itself, whether a job ran, whether it failed, how long it took. I don't want to overclaim, though, so I'll write that down precisely with our engineering team rather than paraphrase from memory.
- Sabine Kranz NoneThat is the correct answer. A precise written statement, signed by someone who is responsible for it. Not a general description.
- Elena Novak NoneAs agreed, I will make sure that a written statement on operational telemetry reaches you, Sabine, with the owner named. I would like to say, so it is clear, that we do not have the statement today, and I do not want to give you a date I cannot keep. I will come back to you with the date by the end of this week.
- Sabine Kranz NoneI accept that. A real date is better than a quick one.
- Jonas Albrecht NoneWhile you talk, I'm checking the grants on the new role. If it shows anything I did not intend, better now.
- Jonas Albrecht NoneGrants list is clean. Ownership on the database and schemas, usage on the warehouse, and the role is granted to one user, mine, for now. Nothing on any other database. No grant option either.
- Laura Penhaligon NoneThat's exactly the shape we want. Honestly, I wish every set-up looked that tidy at this point.
- Jonas Albrecht NoneIt is empty. Tidy is easy when it is empty.
- Laura Penhaligon NoneFair point, and that's why we'll look again after the first load.
- Sabine Kranz NoneThat is a good idea. I would like a second review after the first load, with the same evidence. Please add it to the plan.
- Elena Novak NoneAdded. I am writing it now as a numbered action: review of grants and access history after the first load, owner Sabine for the review, Jonas for the export, Laura for the plan.
- Laura Penhaligon NoneCan I add a small practical one? Jonas, when you're ready we'll need a short list of who the forty users are, by team, so we can map them to roles in the brain. Merchant account managers in one group, merchant risk in another.
- Jonas Albrecht NoneThat comes from the business side, not from me. I can export from the identity provider if someone tells me the groups. Which role has access to that list on your side?
- Laura Penhaligon NoneFair, that's a question for the heads of those two teams. Elena, could you ask them?
- Elena Novak NoneYes. I will write to both team leads this afternoon, copying you, Jonas. To confirm, I need the two group names and an owner for each.
- Sabine Kranz NoneI also need to know that the people in the risk team may see merchant records at that level of detail. That is an internal decision, but I would like it documented before they are given access.
- Elena Novak NoneI will include the question in the same message, and I will ask for the answer in writing.
- Jonas Albrecht NoneOne more technical point, since we are here. The nightly refresh. When it runs, it uses the warehouse we just made. I want a resource monitor on it, so a runaway query cannot burn credits at three in the morning.
- Laura Penhaligon NonePlease do. That's your call entirely, it's your account and your credits. We'd just ask that the limit isn't so tight that the refresh gets cut off before it completes. The target is that it's finished by 07:00 your time on business days.
- Jonas Albrecht None07:00. Noted. I will set it generous for the first weeks and tighten when I have seen the real load.
- Sabine Kranz NoneDoes the refresh time have any bearing on the residency question? I want to be sure there is no step that runs elsewhere.
- Laura Penhaligon NoneNo, the refresh runs on your warehouse in your account. I'd put that in the written note as well, so it's one of the things you can point to.
- Sabine Kranz NoneYes, please. And a diagram, if you have one. Auditors respond well to a diagram.
- Jonas Albrecht NoneThey do. Mostly because it has fewer words.
- Laura Penhaligon NoneHa. Yes, we have one, I'll tidy it so it shows your account boundary clearly, with the region labelled.
- Elena Novak NoneLet me summarise where we are, and please correct me. To confirm: the account region has been shown live and is an EU region. The brain database, three schemas, one role and one warehouse exist in Brenneck's account. The share list is empty. Multi-factor and the network policy are enforced. No connectors are on. Is that right?
- Jonas Albrecht NoneThat is right. Add: the service user exception, documented.
- Elena Novak NoneThank you, yes, I will add it as a note.
- Sabine Kranz NoneFrom my side: the residency point is satisfied for the database, on the evidence shown today, once I have the exports. The telemetry statement is open. The connector review is open. I will not close the finding until the documents are in my hands.
- Elena Novak NoneUnderstood, and that is how I will mark it. Open until evidence, closed after.
- Laura Penhaligon NoneFrom my side, what I need to get going on the connectors is the sign-off from Sabine and the list of groups. Once I have both, I'll draft the connector plan for the first group and send it to Jonas for the grants.
- Jonas Albrecht NoneSend me the grants as a list, in a ticket. I will review each one. I do not run a statement I have not read.
- Laura Penhaligon NoneWouldn't expect otherwise.
- Sabine Kranz NoneOne last question, and it is not on my list, so forgive me. If the brain role were removed from the account tomorrow, what remains?
- Laura Penhaligon NoneGood question. The data is yours, it's in your account, so everything stays until you drop it. The role is just how the brain gets to it. Jonas could drop the role and the brain would stop, but nothing would have left.
- Sabine Kranz NonePlease put that in the exit section of the document. Auditors ask this.
- Elena Novak NoneI will make sure that it is included, under exit and removal. That is action number eight, I believe. Let me read them all back, so that nothing is lost.
- Elena Novak NoneOne: Jonas sends the region export, with timestamp and account name, and the empty share list. Two: Jonas documents the service user exception and sends the policy screenshots. Three: Elena sends the time-limited user request in writing, with role, purpose and expiry. Four: Elena writes to the two team leads for the group names and the decision on access for risk. Five: Laura sends the connector plan for the first group, and no connector goes live before Sabine has reviewed it. Six: Laura sends the diagram with the account boundary. Seven: BB-Demo sends the written statement on operational telemetry, owner named, and Elena confirms the date by the end of the week. Eight: Laura adds the exit and removal section. Nine: a second review of grants and access history after the first load.
- Jonas Albrecht NoneThat matches my notes. Nine items. I have two of them.
- Sabine Kranz NoneMine matches as well. Please send them in the order you read them, numbered.
- Elena Novak NoneYes. I will send the written summary today, with the evidence attached as it arrives. I will say plainly which items are open.
- Laura Penhaligon NoneThanks everyone. That was properly productive. I know it's a lot of paperwork for an empty database, but it's the right order of things for a payment institution.
- Sabine Kranz NoneIt is the right order, yes. Thank you for showing it and not only describing it. That made a difference.
- Jonas Albrecht NoneAgreed. I will send the exports within the hour. Then I go back to the thing that was actually on fire this morning.
- Laura Penhaligon NoneHa, go on, off you go. Good luck with it.
- Elena Novak NoneThank you, Laura, thank you, Jonas, thank you, Sabine. Kind regards, and I will write this afternoon.
- Sabine Kranz NoneThank you. Goodbye.
- Jonas Albrecht NoneBye.
- Laura Penhaligon NoneBye all, speak soon. Enjoy the grey.
Callsmade from