Security.
Updated July 13, 2026
1. Architecture
ConnXL is split into a control plane we run and a data plane you run. The dashboard defines functions, users, and connections; the gateway executes queries inside your network and serves results directly to the add-in. Row-level data never transits ConnXL infrastructure.
2. The gateway
The gateway runs on your infrastructure and makes outbound connections only — no inbound firewall rules, no ports exposed to us. It authenticates to the control plane with mutual TLS: at enrollment it exchanges a one-time token for a client certificate issued by our private certificate authority, and every connection thereafter presents that certificate. Certificates are per-gateway and can be revoked instantly. The gateway pulls configuration rather than accepting pushes. Stop the gateway, and all serving stops with it.
3. Secrets handling
Connection credentials are encrypted with AES-256-GCM the moment they are saved, stored encrypted at rest, and released only to your gateway at execution time. They are never displayed back in full, never written to logs, and access to them is restricted to what is needed to operate the Service.
4. Identity and access
Sign-in is federated through GitLab, Google, Microsoft, or LinkedIn — there are no ConnXL passwords to phish or leak. Access is role-based and scoped per organization, administrators can suspend members instantly, and sessions expire automatically.
5. Encryption
TLS 1.2 or higher protects every connection, including add-in-to-gateway traffic inside your network. Configuration and secrets are encrypted at rest with AES-256-GCM.
6. Operational security
Production access follows least privilege, every administrative action is logged, and infrastructure changes are defined as code and reviewed before release.
7. Availability
The control plane runs on cloud infrastructure with routine backups. Because serving happens in your network, a control-plane outage affects configuration changes only — existing functions keep serving from the gateway's cached configuration.
8. Compliance
We do not currently hold a SOC 2 or similar third-party security certification — the practices on this page describe our actual controls, and this page is updated as they evolve. For organizations subject to GDPR or similar data-protection law, contact us to discuss a data-processing agreement.
9. Vulnerability disclosure
We welcome coordinated disclosure. Report issues to contacto@innmotrix.com — we acknowledge reports within one business day and keep you informed through resolution. We do not pursue legal action for good-faith research.