What it says
What this says
Current to 11 Oct 26A completed security questionnaire for Calderbrook Housing Group, written by Hannah Lowe on 14 Jul 2024 for the Growth tier. It is a set of answers, not a contract, and states no availability percentage, P1 response time or price.
What it is: a pre-sale questionnaire marked final, version one, completed on 14 Jul 2024. It says the brain runs "Inside Calderbrook's own Snowflake account" and that BB-Demo does not copy data into a separate store.
Commits: service levels are deferred to the order form, for example "The standard Growth service level, set out in the order form." Credits are stated as "On Growth, credits apply to availability only."
Unusual: nothing off the standard terms. SSO and SCIM, Sandbox, Premium support and dedicated residency are all stated as not included in Growth.
Not settled: penetration testing, the list of excluded or masked fields and any Enterprise feature need are open items to be confirmed in writing. The document is two years old and does not show whether they were closed.
As found in this document
Current to 9 Oct 26- AvailabilityThe standard Growth service level, set out in the order form.The standard Growth service level, set out in the order form. · Source: object_read:doc_007_001
- P1 first responseThe Growth first-response target for a priority-one issue, as set out in the order form.The Growth first-response target for a priority-one issue, as set out in the order form. · Source: object_read:doc_007_001
- Nightly refreshThe nightly refresh is complete by the start of the business day, customer local time, on business days.The nightly refresh is complete by the start of the business day, customer local time, on business days. · Source: object_read:doc_007_001
- Service creditsOn Growth, credits apply to availability only. Data freshness credits are an Enterprise feature.On Growth, credits apply to availability only. Data freshness credits are an Enterprise feature. · Source: object_read:doc_007_001
- Data processing agreementIt sits alongside the main agreement and is agreed before any connector goes live.It sits alongside the main agreement and is agreed before any connector goes live. · Source: object_read:doc_007_001
The document
Body
Calderbrook Housing Group - Security Questionnaire
Prepared for: Calderbrook Housing Group, Leeds Prepared by: Hannah Lowe, Solutions Engineer, BB-Demo Date completed: 14 Jul 2024 Status: Final, version one Tier under discussion: Growth
About these answers
This questionnaire covers the company brain that BB-Demo would build and run for Calderbrook's business-intelligence team. To be precise, BB-Demo is deployed inside the customer's own Snowflake account, so many of the answers below turn on that single design choice. Where a control belongs to Calderbrook rather than to BB-Demo, the answer says so. Where a control is not part of the Growth tier, the answer says that too, rather than implying it is.
If any answer needs more detail for your own review, I'll put that in writing and send it separately.
A. Architecture and data location
Read the whole document (6,216 characters)
| Question | Answer |
|---|---|
| Where does the brain run? | Inside Calderbrook's own Snowflake account. BB-Demo does not copy your data into a separate BB-Demo data store. |
| Who owns the data? | Calderbrook. The data stays in your account and under your ownership throughout. |
| Which sources would be connected? | Only the systems you choose to connect, such as your CRM, your call recorder, your helpdesk, your accounting system and your document stores. Each connector is scoped with your team during implementation. |
| Can data be restricted to certain teams? | Yes. Access to what the brain can see and who can ask about it is set by your administrators, and the scoping is agreed per connector. |
| Is data residency configurable? | The default is your own Snowflake account and the region it sits in. Dedicated EU or US residency is a separate add-on and is not part of the Growth tier as standard. |
| Does BB-Demo train shared models on customer data? | No. Your data is used to answer questions for your own users and for nobody else. |
B. Access control and identity
| Question | Answer |
|---|---|
| How do users sign in? | Growth uses the standard sign-in for the tier. Single sign-on and automated user provisioning (SSO and SCIM) are Enterprise features and are not included in Growth. |
| Are administrator roles separated from ordinary users? | Yes. Administrators manage connectors, access and settings; ordinary users query the brain within the access they are given. |
| Who at BB-Demo can reach customer data? | Only staff working on your implementation or a support case, and only as far as the work needs. To be precise, BB-Demo staff work within the access Calderbrook grants in its Snowflake account, so you can review and withdraw it. |
| Is access reviewed? | Calderbrook reviews its own users and administrators. BB-Demo supports that review on request at the quarterly business review. |
C. Data protection and privacy
| Question | Answer |
|---|---|
| Will personal data be processed? | Very likely, because tenant calls, complaints and repairs records can contain personal data. That processing happens in your Snowflake account on your instructions. |
| Is a data processing agreement available? | Yes. It sits alongside the main agreement and is agreed before any connector goes live. |
| Special category or sensitive data? | The short answer is that it depends on what your sources contain. The longer answer is that we would agree at the scoping stage which fields are excluded or masked, and I would document that decision. |
| How are data subject requests handled? | Because the data remains in your account and in your source systems, requests are actioned by Calderbrook. BB-Demo assists with locating records indexed by the brain. |
| Deletion at the end of the relationship? | The brain's indexes and configuration are removed from your Snowflake account, and the process is confirmed in writing. |
D. Encryption and platform security
| Question | Answer |
|---|---|
| Encryption in transit and at rest? | Data is protected by the controls of the Snowflake platform in your account, and connectors communicate with source systems over encrypted connections. |
| Where are secrets and credentials held? | Connector credentials are held within your Snowflake environment under your administrators' control. |
| Is customer data used in test environments? | Not by default. A Sandbox is an optional add-on and is not part of the Growth tier as standard. |
| Is there penetration testing? | I would rather not summarise this from memory. The current position will be confirmed with our security lead and sent to you in writing. |
E. Availability, resilience and support
| Question | Answer |
|---|---|
| What availability is committed? | The standard Growth service level, set out in the order form. |
| How quickly are serious issues answered? | The Growth first-response target for a priority-one issue, as set out in the order form. |
| Is the nightly refresh time defined? | Yes. The nightly refresh is complete by the start of the business day, customer local time, on business days. |
| Are service credits available? | On Growth, credits apply to availability only. Data freshness credits are an Enterprise feature. |
| Is named-engineer support available? | Premium support is an optional add-on and is not included in Growth as standard. |
F. Incident response and change
| Question | Answer |
|---|---|
| How will you be told about a security incident? | Calderbrook's nominated contact is notified without undue delay, with what is known, what is being done and what we need from you. |
| How are changes to the brain managed? | Changes to connectors and configuration are agreed with your administrators first, and significant changes are noted in the quarterly review. |
| Are subprocessors used? | Snowflake is the platform you already contract with directly. Any further subprocessor would be listed in the data processing agreement before signature. |
G. Items to be confirmed in writing
- Current penetration testing summary, from our security lead.
- Final list of excluded or masked fields, agreed at scoping.
- Whether any Enterprise feature is needed by Calderbrook's own policies, in which case the tier should be reviewed.
Thanks, Hannah