Gilberdyke Freight - Security Questionnaire
Documentfinal Gilberdyke Freight · security questionnaire · final · 28 Sep 2023
BG-Demo's answers to Gilberdyke Freight's security questionnaire, stored as final. Data stays in the customer's Snowflake account, transit encryption is TLS 1.2 or higher, and BG-Demo states it is audited to SOC 2 Type II. It is not a contract and states no price or service levels.
What it says
What this says
As at Fri 9 Oct 2026BG-Demo's answers to Gilberdyke Freight's security questionnaire, stored as final. Data stays in the customer's Snowflake account, transit encryption is TLS 1.2 or higher, and BG-Demo states it is audited to SOC 2 Type II. It is not a contract and states no price or service levels.
What it is: a one-sheet security and infrastructure questionnaire answered by BG-Demo, created and last modified on 2023-09-28. It has not been updated since, so treat the answers as a point-in-time statement.
Commits: it describes practice rather than binding terms. It says "BG-Demo does not store a copy of your data" and that encryption in transit is "TLS 1.2 or higher". It also says "BG-Demo is audited to SOC 2 Type II."
Unusual: "BG-Demo does not maintain separate backups; your Snowflake retention and recovery settings apply to all data." Single sign-on and SCIM are tied to the Enterprise tier, while Growth uses standard authentication.
Not settled: incident notification is promised "within our defined timeframe" with no figure. The document gives no availability, response time, price, signatory or renewal term, and does not show whether the SOC 2 claim is still current.
As found in this document
As at Fri 9 Oct 2026- Encryption in transitTLS 1.2 or higherSource: the AI read of this record
- ComplianceBG-Demo is audited to SOC 2 Type II.Source: the AI read of this record
- Backup and disaster recoveryBG-Demo does not maintain separate backups; your Snowflake retention and recovery settings apply to all data.Source: the AI read of this record
The document
Body
Gilberdyke Freight, Security Questionnaire
BG-Demo Security and Infrastructure
| Question | Answer |
|---|---|
| Data location | Your data layer runs inside your own Snowflake account. BG-Demo does not store a copy of your data; we read only the data you have explicitly connected. |
| Data encryption in transit | All communication between your systems and BG-Demo uses TLS 1.2 or higher. To be precise, we enforce modern cipher suites and disable legacy protocols. |
| Data encryption at rest | Encryption of data at rest follows your Snowflake account's encryption settings. BG-Demo does not hold encryption keys. |
| User access and authentication | Access to your data layer is controlled through your Snowflake identity provider. Growth tier uses standard authentication; single sign-on and SCIM provisioning are available in the Enterprise tier. |
| Audit trails | Every query to the data layer is logged within your Snowflake account and available for your compliance and security teams to review. |
| Backup and disaster recovery | BG-Demo does not maintain separate backups; your Snowflake retention and recovery settings apply to all data. |
| ** |
Read the whole document (1,762 characters)
Vulnerability and patch management | We conduct regular security testing and maintain a vulnerability disclosure programme. Patches are applied according to severity and risk. | | Compliance | BG-Demo is audited to SOC 2 Type II. | | Incident response | We maintain a formal incident response process and will notify you of any incident affecting your data within our defined timeframe. | | Third-party services and subprocessors** | We use Snowflake and standard cloud infrastructure services. A full list of subprocessors is available on request. |
Unusual terms
As at Fri 9 Oct 2026- No BG-Demo backups; relies on Snowflake retention
- SSO and SCIM only on Enterprise tier
- Incident notice timeframe not quantified