Privacy Policy
Last updated: April 30, 2026
This Privacy Policy explains how Teckel collects, uses, and protects information when customers use the Teckel platform.
Information We Collect
Teckel may collect:
- Account information, such as name, email address, organization membership, and authentication metadata.
- Site configuration, such as domains, install status, action definitions, required fields, destinations, and integration settings.
- Action activity, such as registry reads, calls, submitted fields, missing inputs, completions, failures, pages, and integration outcomes.
- Technical data, such as IP address, device and browser information, logs, diagnostics, and request metadata.
- Support communications and other information provided directly to Teckel.
How We Use Information
Teckel uses information to:
- Provide, secure, maintain, and improve the platform.
- Authenticate users and manage organization, site, action, and integration settings.
- Publish customer-approved action metadata and route completed action payloads to customer-configured destinations.
- Measure readiness, usage, action activity, completions, failures, and high-level conversion outcomes.
- Communicate about the service, including support and important product updates.
Customer Content
Customers control the action definitions, required fields, destinations, and integration settings they configure in Teckel. Customers are responsible for ensuring they have the right to submit and process information through their configured actions and destinations.
Service Providers and Subprocessors
Teckel uses third-party service providers to operate, secure, and improve the platform. These providers may process limited customer or personal data on Teckel's behalf for purposes such as hosting, authentication, database services, application monitoring, and transactional email.
Current Teckel subprocessors include:
| Subprocessor | Purpose | Data categories |
|---|---|---|
| WorkOS | Authentication, organization membership, and session management | User account data, organization identifiers, authentication metadata |
| Supabase | Database and application data services | Organization data, site configuration, action configuration, activity events |
| Cloudflare | Application hosting and edge delivery | Request metadata, application logs, public site assets |
| Sentry | Error monitoring and application diagnostics | Error traces, request metadata, diagnostic context |
| Resend | Transactional email sent by Teckel | Email addresses, message content needed for delivery |
This list covers providers Teckel uses to run the service. It does not list optional destinations or integrations that customers choose to connect for their own action workflows.
Teckel may also share information when required by law, to protect rights and security, or in connection with a business transaction.
Retention
Teckel retains information for as long as needed to provide the service, comply with legal obligations, resolve disputes, enforce agreements, and maintain security. Customers may request deletion according to their agreement with Teckel.
Security
Teckel uses administrative, technical, and organizational safeguards designed to protect information. Customer data is protected with row-level security, encryption at rest, and HTTPS/TLS encryption in transit.
Teckel publishes customer-approved action metadata to agents while keeping delivery settings and connected integration credentials private to authorized workspace members. No system is perfectly secure, so customers should limit workspace access to authorized users.