Privacy Policy

1. Overview

lxzl ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our workflow automation platform.

2. Information We Collect

Account Information

When you create an account, we collect your email address and authentication credentials. Passwords are hashed using Argon2id and are never stored in plaintext.

Workflow Data

We store the workflows you create, including node configurations, execution history, and run results. This data is stored locally in your instance's SQLite database.

Credentials

API keys and secrets you store in the credentials vault are encrypted using AES-256-GCM before being written to the database. Decryption occurs only at runtime when a workflow execution requires it.

MCP Server Configuration

When you register MCP (Model Context Protocol) servers, we store connection configuration including server names, transport type, commands, and URLs. Secret fields such as environment variables and authentication headers are encrypted using the same AES-256-GCM vault used for credentials. Plaintext secrets exist only in memory during active connections.

Usage Data

We may collect anonymous usage metrics such as node types used, execution counts, and error rates to improve the Service. This data does not include your workflow content or personal information.

3. How We Use Your Information

• To provide and maintain the Service
• To execute your workflows and process data as configured
• To store and retrieve your encrypted credentials
• To maintain run history for debugging and replay
• To improve the Service based on anonymous usage patterns

4. Data Storage & Security

Your data is stored in a SQLite database using WAL (Write-Ahead Logging) mode for performance and reliability. The database file resides on the server hosting your lxzl instance.

Security measures include:

• AES-256-GCM encryption for stored credentials
• Argon2id password hashing
• Sandboxed code execution with keyword guards and resource limits
• SSRF protection blocking private network access from workflow HTTP requests
• Input validation and payload size limits across all API endpoints

5. Third-Party Services

Your workflows may interact with third-party services including:

• AI Providers — Ollama (local, no data leaves your machine), Anthropic, OpenAI
• Email Services — Resend, SendGrid, SMTP
• Webhook Endpoints — any URL your workflows are configured to call
• Integration APIs — Slack, Notion, and other configured integrations
• MCP Servers — local subprocesses (stdio) or remote servers (SSE, HTTP) that your workflows call via the Model Context Protocol

When using cloud AI providers (Anthropic, OpenAI), your prompts and data are sent to their servers and subject to their privacy policies. Using Ollama (the default) keeps all AI processing local.

When using MCP servers, tool call inputs and outputs pass through the configured server. Local stdio servers process data on your machine; remote SSE/HTTP servers are subject to their operators' privacy policies.

6. Data Retention

Workflow data and run history are retained indefinitely unless you delete them. You can delete individual workflows, runs, tables, and credentials at any time through the application interface.

7. Your Rights

You have the right to:

• Access all data stored in your account
• Export your workflows and data
• Delete your account and all associated data
• Modify or correct your information

8. Children's Privacy

The Service is not intended for use by children under 13. We do not knowingly collect personal information from children under 13.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by updating the "Last updated" date. Continued use of the Service after changes constitutes acceptance.

10. Contact

For privacy-related questions, contact us at privacy@lxzl.dev.