Security and data handling.
Workspace isolation, encrypted sensitive data, verified callbacks, and a clear record of every dispatch decision.
- Sensitive data
- AES-256-GCM
- API keys
- Hashed at rest
- Result webhooks
- Signed + replayable
- Call audio
- Not ingested or stored
What Tremi stores.
The information needed to run your workflow and explain what happened.
Workflow and conversation data
Recipient contact details, inputs, message content, workflow versions, selected provider resources, app event payloads, and configured actions. Run evidence includes delivery events, structured results, and transcripts returned by your providers, including AI text conversations. Tremi does not ingest or store call recording audio.
Account and operational data
Account information, workspace access, billing and support records, connection details, suppressions, and security events. Sensitive workflow data and provider credentials are encrypted at rest; API keys are hashed.
Retention and workspace deletion
Information is retained as reasonably needed to provide Tremi, meet contractual or legal obligations, resolve disputes, and protect the service. Retention depends on data type and customer agreement.
A workspace owner can delete the workspace through Tremi or request validated deletion. Limited information may remain temporarily in backups, fraud-prevention records, security logs, or legally required records.
Read the retention policy
Security controls
Access checks protect the workspace. Verification protects incoming evidence. Dispatch checks decide whether the next attempt should still happen.
Workspace data boundary
Every workflow, provider connection, API key, run, event, and webhook is authorized against its workspace.
Protected secrets and payloads
Provider credentials, recipients, variables, content, snapshots, evidence, and transcripts are encrypted at rest.
Verified provider evidence
Provider callbacks are signature-checked, deduplicated, and normalized before they can change run state.
Safer dispatch decisions
Recipient suppressions are checked before dispatch, and uncertain provider acceptance stops for attention.
Keep the facts
behind each decision.
A run retains its published version, selected resources, provider receipts, and result delivery history. Operators can investigate uncertainty without sending another message.
Verify result signatures
A clear division
of responsibility.
Tremi operates the orchestration
Workspace authorization, encrypted storage, provider callback verification, idempotency, suppressions, immutable run snapshots, and signed results.
You control the communication
Consent and lawful basis, provider accounts, registrations, recipient lists, content, disclosures, sending windows, and escalation policy.
Providers process their part of the workflow
Retell handles AI calls and conversations; Twilio and SendGrid handle their configured channels. Provider retention, recordings, and account settings remain subject to each provider’s policies and your agreements. Deleting a Tremi workspace does not itself delete records held in your provider or CRM accounts.
Connected apps follow your configuration
You select the accounts, event mappings, and actions. Pipedream manages credentials for accounts connected through Pipedream Connect.
See what information is processed
Planning a healthcare workflow?
Business Associate Agreements are available. Contact security@tremi.ai for a security review of your intended workflow and provider setup.
We will review what data the workflow needs, where it flows, and the provider arrangements required for your use case.
Report a security issue.
Include the affected surface, steps to reproduce, and supporting evidence you can safely share.