Call Recording & Storage

Overview

Sulus stores call recordings, transcripts, and logs securely by default, and also supports routing recordings to your own cloud storage if you need full control over retention.

By default, Sulus stores call recordings, transcripts, and logs securely in the cloud:

• Recordings, logs, and transcripts are encrypted at rest and in transit
• Access is controlled through your API credentials
• Artifacts are automatically cleaned up based on your account's retention policy

Your account's specific default retention period is configurable in your dashboard settings.

Call recordings and logs are stored in a private bucket and cannot be downloaded directly from URLs returned in webhooks or API responses. To retrieve them, you must use authenticated endpoints with your private API key, which return short-lived signed URLs.

Signed URLs returned by these endpoints expire after a short period. Always request a fresh URL from the API rather than caching the redirect target.

If you need full control over retention, you can configure custom storage to send recordings to your own infrastructure:

• AWS S3
• Google Cloud Storage
• Cloudflare R2
• Azure Blob Storage
• Supabase Storage

With custom storage, your own bucket's retention policies apply, giving you complete control over how long recordings are kept.

For HIPAA-enabled organizations, call recordings and logs are stored in Sulus's private HIPAA-compliant storage by default. Configuring custom storage is optional and redirects storage to your own infrastructure instead.

In summary, Sulus's default storage covers most use cases securely out of the box, and custom storage gives you a path to full retention control when your organization's policies require it.