1. Scope and roles
This Privacy Policy explains how Wattson, Inc. collects, uses, discloses, and protects information through the Tremi website, accounts, APIs, and outbound orchestration service.
When a customer submits recipient, workflow, or provider data to Tremi, the customer generally determines why that data is processed and Tremi processes it on the customer's instructions. The customer's own privacy notices may also apply to recipients and other end users.
2. Information we collect
Account and workspace information
- Name, email address, authentication details, team membership, role, workspace settings, and support communications.
- Subscription status, billing references, plan and credit usage, and related transaction records. Payment card details are handled by our payment provider rather than stored directly by Tremi.
Workflow and service information
- Workflow definitions, content, timing, stop conditions, variables, external identifiers, recipient destinations, metadata, connected-app mappings, and completion-action settings submitted by customers.
- Provider resources and revisions, connected-account identifiers and health, app event payloads, action results, run state, delivery receipts, callbacks, suppressions, result webhooks, operational evidence, and transcripts returned by connected providers.
- Tremi configures its Retell integration not to ingest recording audio and does not store call recordings.
Credentials and technical information
- Encrypted communication-provider credentials, connected-app configuration, and signing material; hashed Tremi API secrets; API-key names, prefixes, and scopes. Pipedream manages credentials for accounts connected through Pipedream Connect.
- Request identifiers, timestamps, IP and security logs, browser and device data, page paths, theme preference, and diagnostic information needed to operate and protect the service.
3. How we use information
We use information to provide accounts and billing, compile and execute workflows, connect customer-selected systems and communication providers, process configured triggers, stops, and actions, deliver run results, maintain evidence, support customers, prevent abuse, investigate incidents, and comply with legal obligations.
We may also use aggregated or de-identified operational information to understand reliability and improve Tremi. We do not use customer service data to train third-party foundation models unless a customer separately authorizes that use in writing.