How Production Data is Collected, Stored, and Protected
EKAS connects to your MES, ERP, and SCADA systems to ingest production events, quality records, and downtime logs. All data is encrypted in transit and at rest, isolated by tenant, and never used for model training or cross-customer analytics.
Data Collection and Ingestion
EKAS connects to production systems via read-only database queries, API calls, or file transfers. No data is written back to your MES or ERP. Ingestion runs on scheduled intervals; near real-time is supported for systems that expose event streams.
- Read-only access to MES/ERP databases
- TLS 1.3 encryption for all data transfer
- No write permissions to production systems
- Ingestion runs on defined schedule (hourly, daily, or event-driven)
Data Storage and Isolation
Production data is stored in PostgreSQL with row-level security enforcing tenant isolation per user role and production site. Encryption at rest via AWS KMS with customer-managed keys.
- PostgreSQL row-level security enforced per role and site
- AWS KMS encryption at rest with CMK
- No cross-tenant data access possible
- Backup retention configurable per tenant
What EKAS Does Not Do
EKAS uses enterprise cloud LLM infrastructure with a zero-training-data guarantee. Your production data is used only to answer your queries — never to train language models, never shared with other customers, and never used for cross-customer analytics.
- No model training on customer data
- No cross-customer analytics or benchmarking
- No data sharing with third parties
- Enterprise LLM inference — zero-training-data guarantee
Review Data Handling Practices
Our security packet includes detailed data flow diagrams and system access documentation.