Privacy Policy

Effective date: March 4, 2026

1. Data we process

• Account profile data (name, email, authentication metadata)
• Rule definitions and run metadata
• Operational logs for diagnostics and reliability

2. Purpose of processing

Data is used to authenticate users, execute configured automations, support debugging, and maintain service reliability.

3. Credentials and secrets

API credentials should be managed through secure environment configuration. Sensitive values must not be intentionally exposed in rule payloads or prompts.

4. Data sharing

We do not sell personal data. Data sharing is limited to infrastructure and integration needs required to operate the service.

5. Data retention

Rule and run records are retained for operational traceability unless removed by platform administrators.

6. Security practices

Security controls include authentication checks, CSRF protection for web forms, request IDs, and bounded error logging.

7. Policy updates

This policy may be updated as the product evolves. Material changes will be reflected by updating the effective date on this page.