Last updated May 21, 2026
Security Overview
How Jexi approaches access, workflow controls, monitoring, and incident handling.
Jexi is built around least privilege, workspace boundaries, auditability, controlled integrations, encrypted transport, and ongoing improvement of security controls.
Security program
- Administrative, technical, and organizational safeguards appropriate to the nature of the service and data processed.
- Access controls for customer workspaces and internal systems.
- Monitoring for errors, abuse, unusual activity, and security events.
- Operational recovery processes for critical systems.
- Review and improvement of controls as the product and customer requirements mature.
Access management
Customer administrators are responsible for inviting the right users, removing access when people leave, configuring least-privilege roles, and limiting integration scopes. Jexi personnel access production systems only when needed for operations, support, security, legal compliance, or contractual obligations.
Workflow controls
Sensitive workflows should be configured with approvals, audit logs, and escalation paths. Customers should test workflows before production deployment and monitor outcomes after launch.
Credential handling
Customers should protect and rotate API keys, OAuth tokens, service accounts, passwords, and connected-system credentials. If a credential may have been exposed, customers should revoke or rotate it and notify Jexi where the exposure may affect the service.
Vulnerability reporting
If you believe you found a security issue, email hello@jexi.com with steps to reproduce, affected URLs or accounts, potential impact, and safe contact details. Please do not access, modify, delete, disrupt, or exfiltrate data that is not yours.
No perfect security
No internet service is perfectly secure. Jexi works to protect the service with reasonable safeguards, but customers remain responsible for their own users, endpoints, policies, connected accounts, and workflow configuration.