Kallang Reach Payments - Security Questionnaire
Documentfinal Kallang Reach Payments · security questionnaire · final · 6 Jan 2026
A final version 1 security questionnaire for Kallang Reach Payments, created 6 Jan 2026. It states TLS 1.2 or higher in transit and a P1 first response of 1 business hour (Growth tier). It is an information document, not a contract.
What it says
What this says
As at Fri 9 Oct 2026A final version 1 security questionnaire for Kallang Reach Payments, created 6 Jan 2026. It states TLS 1.2 or higher in transit and a P1 first response of 1 business hour (Growth tier). It is an information document, not a contract.
What it is: a BG-Demo answer sheet on encryption, access control, isolation, incident response and data handling. Hannah Lowe, Solutions Engineer, is the BG-Demo person named for it.
Commits: it states "For P1 issues, our first response is 1 business hour (Growth tier)." It also says data stays in the customer's own Snowflake account and BG-Demo does not manage encryption keys.
Unusual: the SOC 2 wording is only "designed to support SOC 2 Type II readiness" and certifications are deferred. Incident details and liability insurance are pushed to the security addendum and the master service agreement.
Not settled: the document states no price, signatories, term or renewal date. It does not show who at Kallang Reach Payments received it, and it is not an executed order form.
As found in this document
As at Fri 9 Oct 2026- P1 first response1 business hour (Growth tier)Source: the AI read of this record
- Data in transit encryptionTLS 1.2 or higherSource: the AI read of this record
- Encryption keys at restcustomer's Snowflake-managed encryption keys; BG-Demo does not manage encryption keysSource: the AI read of this record
The document
Body
Kallang Reach Payments - Security Questionnaire
Version 1, Final
Information security and data protection
| Question | Answer |
|---|---|
| How is data encrypted in transit? | Data is transmitted using TLS 1.2 or higher to the customer's Snowflake account and between system connectors. |
| How is data encrypted at rest? | Data at rest in the customer's Snowflake account is encrypted using the customer's Snowflake-managed encryption keys. BG-Demo does not manage encryption keys. |
| What access controls are in place? | Role-based access control. Users are assigned to teams within the brain; team admins can add, remove and change permissions. Enterprise tier includes SSO and SCIM for centralised identity management. |
| How is customer data isolated? | Each customer's brain is a separate Snowflake database in their own Snowflake account. No cross-customer access. |
| What is your incident response process? | We monitor for security events. For P1 issues, our first response is 1 business hour (Growth tier). We will notify the customer within this window. Full incident details are available in our security addendum. |
| Do you carry liability insurance? | Yes. Details are i |
Read the whole document (1,687 characters)
n the master service agreement. |
Data handling
All customer data remains in the customer's own Snowflake account. BG-Demo runs queries and manages the interface but does not store or backup customer data outside that account.
Audit and compliance
B-Glass is designed to support SOC 2 Type II readiness for Growth and Enterprise customers. Specific controls and compliance certifications will be confirmed during the sales cycle and documented in the data processing agreement.
Unusual terms
As at Fri 9 Oct 2026- SOC 2 Type II readiness only, certifications to be confirmed
- incident details deferred to security addendum