Snapshot 53445

Document
Trust center
URL
https://e6data.com/security
Fetched
HTTP status
200
Content type
text/html
Fetch mode
static
Size
160063 bytes
SHA-256 (raw)
4517fd98e6b02961ab6f2cecbda6172be8aec60670a64ae64ca1e71ed04c5b21
SHA-256 (normalized text)
c750e232274efc316bc5c1ef55a9fb6a1b864e1d6fb7212a935a23e736eb244d

Normalized text

Scripts and page chrome removed; this is what change detection compares.

SOC 2
Independently audited security controls
ISO 27001:2022
Certified information security management
ISO 27017:2015
Cloud-specific security controls
ISO 27018:2019
Protection of personal data in the cloud
HIPAA
Safeguards for protected health information
GDPR
EU data protection and processing rights
Audit reports, certificates, sub-processors and security controls are published in our Trust Center.
THE ARCHITECTURE
Your data stays in your account
The architecture separates a Data Plane from a Control Plane, so your data never leaves your environment.
DATA PLANE · YOUR AWS ACCOUNT
Holds the actual data and the query engine. It runs entirely inside your account.
CONTROL PLANE · e6data-MANAGED
Receives only metadata and metrics for orchestration. Never your data.
HOW IT IS SECURED
Least privilege, end to end
Customer-owned deployment
The engine deploys into an isolated Kubernetes namespace inside your own AWS EKS cluster, via Terraform scripts that are public and auditable.
Least-privilege access
Read-only access to the S3 buckets and Glue catalog you specify, plus a separate bucket for schema metadata. Nothing more.
IAM, scoped per service
Permissions are granted through IAM OIDC for a specific service account. Granular S3 controls, and MFA required for every deployment.
No e6data personnel access
Employees have no access to the production Control Plane and no pathway to your Data Plane. All inter-plane traffic is application-to-application.
Full audit visibility
Kubernetes audit and authenticator logs, S3 access logging on by default, CloudTrail for IAM and STS, and IP allowlisting via EKS authorized networks.
Residency stays in force
e6data runs where your tables already live, so your existing governance and data-residency controls apply unchanged.
WHAT LEAVES THE DATA PLANE
Metadata, never data
Only operational metadata is sent to the Control Plane. Query Editor results stream to your browser through the Control Plane - they are not retained on e6data servers, not written to disk, and inaccessible to employees.
Infrastructure and cluster metrics (CPU, memory, I/O)
Query counts and durations - SQL text masked, hashes only
Schema information (table and column names)
User identity, for query attribution
Read the full detail
Certifications, audit reports, sub-processors, control details and the deployment model are published in our Trust Center.
Trust Center →privacy@e6data.com