Trust and Security

ToolJet combines encryption, role-based permissions and auditability for internal apps built visually, with AI or through coding agents. Match the controls to your plan, review generated queries and test access before releasing an app.

• Encryption in transit. ToolJet uses TLS to encrypt data transmitted between users and its servers, protecting information as it moves.
• Encryption at rest. Sensitive data stored on ToolJet's servers is encrypted at rest. For Self-hosted deployments, configure storage and infrastructure protections for your environment.
• Role-based access. Control access to apps and resources with role-based permissions. Give users and connected accounts only the access they need. Authentication and access controls
• AES-256-GCM credential encryption. Data source credentials are encrypted using AES-256-GCM and are not shared with AI servers or model providers. On Self-hosted deployments, they remain inside your deployment. Credential security details

Your data is not training data. ToolJet does not use customer data to train or improve AI models, and does not permit its third-party LLM providers to do so. AI data usage policy

Control the context AI receives. Requests can include prompts, app context, schemas, and data read through connected credentials. Restrict data-source permissions; discovery is not limited to schemas. Treat logs containing prompts or responses as sensitive.

Review SOC 2 audit information, ISO 27001, and GDPR compliance resources in our Trust Center. Explore our controls and policies

Control the deployment, the gateway, and the model endpoint to meet your data requirements.

Self-host ToolJet, use our AI gateway. Run ToolJet on your infrastructure and send AI requests outbound to ToolJet's hosted gateway. Your deployment initiates a key-authenticated connection, and the gateway cannot initiate a connection into your deployment. Replies return over the connection your deployment opens.

Keep AI on your infrastructure. With Enterprise add-ons, deploy the AI gateway on-premises and connect a supported model endpoint inside your network. Discuss deployment

Builder BYOK is available on Enterprise plans for both Cloud and Self-hosted. Requests use ToolJet's managed AI server with your provider keys and do not consume ToolJet AI credits; provider usage is billed separately. On-premises gateway hosting is a separate Self-hosted Enterprise add-on. Fully internal inference also requires a supported local model endpoint.

Outbound-only connectivity controls network access, not request contents. AI requests can include context from the data sources you make available. Review AI data usage

Separate environments, controlled releases. Enterprise plans include multiple deployments. Run development, staging, and production as separate ToolJet instances, with AI enabled or disabled for each deployment.

• Development (AI enabled). Build with AI using test or sanitized data and limited data-source permissions.
• Staging (AI disabled). Pull app definitions with GitSync. Configure staging credentials and test before release.
• Production (AI disabled). Promote reviewed apps with production-only credentials and controlled access.

Promote apps with GitSync, and configure secrets separately in each deployment. Deployment guide

No internet, still ToolJet. With the air-gapped deployment add-on for Self-hosted Enterprise, ToolJet runs without internet access, including its licensing system. Platform operation and license validation work offline; if AI is enabled, use a local gateway and model. Keep required data sources, identity services, and Git repositories within your isolated network. Plan an air-gapped deployment

Running with restricted outbound access instead? For ToolJet-managed AI, allow outbound HTTPS to api-gateway.tooljet.ai and python-server.tooljet.ai, as listed in the AI setup guide. Your selected data sources, model endpoints, Git hosts, email services, and identity providers may require additional access. Environment variables let you disable telemetry, update checks, and other optional outbound features. Review the configuration reference for your release.

We monitor our systems for suspicious activity and security incidents. Our response plan covers containment, communication with affected parties, and remediation to help prevent recurrence. Review our security controls

Our Trust Center documents change-management and application security controls. For your own apps, review changes before release, separate development from production, and keep deployment dependencies up to date. Review the app release lifecycle

Protect your accounts and maintain the infrastructure you operate.

• Use strong, unique passwords and two-factor authentication.
• Review permissions for users and connected data sources.
• Keep devices, applications, and Self-hosted infrastructure updated.

Use the audit logging and observability controls available for your plan to review activity and support security monitoring. Set appropriate access and retention for logs.

Our privacy policy explains data collection, use, retention, and deletion requests, including applicable legal retention requirements. Contact us to request deletion of your account or personal information. Read the privacy policy

Make security part of your deployment plan. Review your requirements and Enterprise add-ons with our team. Talk to our team or visit the Trust Center.