Designed by data industry veterans, Gable was built with security and privacy in mind from day one.

​
Resource Isolation

Gable employs a single tenant architecture using AWS Organizations, meaning each customer is provisioned their own AWS Account, which serves as the fundamental security boundary in AWS. Gable follows the latest best practices for structuring a secure AWS Organization. Separating internal and customer resources into isolated AWS accounts provides the following benefits:
  • Uniform Policy Enforcement: Gable uses AWS Organizations policies to uniformly enforce security and compliance requirements for all AWS accounts managed by Gable.
  • Security Controls: AWS accounts act as an identity and access management isolation boundary. Customer accounts have specific role based control policies and mechanisms, enforced at the AWS Organization level, which limits access to a customer’s infrastructure and data.
  • Network & Data Isolation: In addition to acting as an access boundary, AWS accounts provide network and storage isolation by default.
  • Many Teams: Separating customer infrastructure from internal infrastructure allows only specific roles within Gable, like the incident response team, controlled access to customer infrastructure.
  • Auditability: Following AWS Organizations best practices, Gable maintains an isolated and restricted Security Logs account that stores the AWS CloudTrail logs enabled at the Organization level.

​
Compliance

SOC2 Badge
  • Gable completed our most recent annual SOC 2 Type 2 audit in June of 2025, you can request access to the report at https://trust.gable.ai/.
  • Gable collects metadata, logs, and metrics for the purpose of identifying data reliability issues. However, we acknowledge that the service may collect and process personal data as part of query logs or through other functionality that you initiate within the Gable platform. If any such data is passed to Gable, it is used for the sole purpose of identifying data reliability issues. See our privacy policy for more details.

​
Privacy

​
Privacy Policy

Gable’s team implements industry best practices across the board to protect the security of its infrastructure & services, and the data privacy of its customers. The following are only some of the elements of our security program and system architecture:
  • Gable will only collect metadata, logs, and metrics for the sole purpose of identifying data reliability issues. Your information will only be used to generate your own reports and will not be shared with any external parties.
  • Access to production systems is tightly controlled, and routinely audited. In cases where debugging or maintenance work is required, a minimal number of on-call engineers will be permitted to access the data necessary for this purpose. All data stored at rest, including on engineers laptops for debugging purposes, is encrypted.
Should you have any questions about our privacy practices or this Privacy Policy, please email us at privacy@gable.ai.

​
Security

  • Gable does not maintain any physical servers or virtual machines. Processing and storage is conducted on servers hosted on and managed by Amazon Web Services.
  • All data is encrypted both at rest (AES-256) and in transit (TLS).
  • Following AWS Organizations best practices, organization wide CloudTrail audit logs are stored in a central log archive account with highly restricted access.
  • Gable leverages AWS Organization Service Control Policies to enforce best practices for all accounts created in the organization.
  • Access to all critical systems and production environments is centrally managed by our Identity Provider (Okta), which enforces multi-factor authentication. Accounts are automatically provisioned and decommissioned by our identity provider. Gable does not allow user/password auth for any critical systems, or production environments. Access to all systems is routinely audited.
For any questions, or to report an issue, contact security@gable.ai.