Gilberdyke Freight - Security Questionnaire
Documentfinal Gilberdyke Freight · security questionnaire · final · 28 Sep 2023
BG-Demo's answers to a customer security questionnaire: data stays in the customer's own Snowflake account, TLS 1.2 or higher in transit, SOC 2 Type II stated. It is a statement of practice, not a contract, and is dated 28 Sep 2023.
What it says
What this says
As at Fri 9 Oct 2026BG-Demo's answers to a customer security questionnaire: data stays in the customer's own Snowflake account, TLS 1.2 or higher in transit, SOC 2 Type II stated. It is a statement of practice, not a contract, and is dated 28 Sep 2023.
What it is: a one-sheet questionnaire completed by BG-Demo for Gilberdyke Freight, filed under the customer's Security folder. The author is not named in the text; the givens link Tobias Renwick, Chief Technology Officer and Co-founder, to the document.
Commits: nothing priced or dated. It states practice, for example "BG-Demo does not store a copy of your data; we read only the data you have explicitly connected." and "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." Customers relying on BG-Demo for recovery should know this. The incident answer gives no figure: "within our defined timeframe".
Not settled: the file is marked final but is a single version from 28 Sep 2023, so it may be stale. It names no signatory, contract or tier commitment, and the subprocessor list is only "available on request". The Growth and Enterprise authentication wording suggests a Growth-tier context, but the text does not say which tier the customer holds.
As found in this document
As at Fri 9 Oct 2026- Data locationYour data layer runs inside your own Snowflake account.Source: the AI read of this record
- Encryption in transitTLS 1.2 or higherSource: 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
- ComplianceBG-Demo is audited to SOC 2 Type II.Source: the AI read of this record
- Incident notificationwithin our defined timeframeSource: 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 separate BG-Demo backups
- Incident notification timeframe not stated