Security Overview
Last updated July 21, 2026
This document describes current baseline technical and organizational measures for RevenueCallout. It is not a certification, penetration-test report, guarantee of absolute security, or commitment to a specific service level unless incorporated into a signed agreement.
What we store and where
Supabase is the primary database and authentication provider for hosted workspaces. We store submitted call transcripts and meeting metadata, call analyses and evidence excerpts, recorded outcomes, your documented sales process, training examples, weekly briefs, workspace settings and integration credentials. Notification delivery records also contain the destination email and message text.
Transcripts are sent to the configured AI provider for analysis. Team notifications are delivered through Resend. Connected meeting services may retain original recordings under their own policies. See our subprocessor list for providers. The database region depends on the deployed Supabase project; this page does not promise a specific country of storage.
Who can access it
Authenticated workspace members can access their workspace content. Owners control sensitive settings and deletion. Database row-level security separates customer workspaces. Server-side service credentials can access data for processing and administration; these credentials are not provided to users. Authorized operators and infrastructure providers may access data when needed to operate or support the service. This is not a zero-access or end-to-end encrypted service.
How long data stays
During beta, customer content is retained until the workspace owner deletes it or submits a verified deletion request. There is currently no automatic 30-, 60- or 90-day expiry. A fixed retention period must be agreed before uploading content that requires one. Provider backups follow their configured recovery cycles; we do not promise immediate erasure from backups. See the privacy policy for the full retention terms.
How to delete your data
The owner can request deletion by contacting the privacy email below. The authenticated workspace deletion endpoint also requires a recent sign-in and the exact confirmation DELETE WORKSPACE. The deletion flow removes workspace content from the active database and attempts to delete associated authentication users. Failed authentication deletions are queued for retry. It returns a receipt so completion or a partial failure can be tracked.
Deletion does not automatically remove copies already exported to a CRM, a meeting provider or your inbox. Provider retention applies to AI processing and backups. Pseudonymous compliance and deletion records may remain; a fixed expiry for those records has not yet been established. For a verified request or help with external copies, contact hello@revenuecallout.com.
Current controls
Tenant isolation. Customer records carry a tenant identifier and database row-level security restricts authenticated access. Server integrations must resolve tenant identity from trusted records rather than webhook payload claims.
Access and authentication. Supabase authentication protects user sessions. Owner-only functions control billing and sensitive workspace settings. Service credentials remain server-side and are not intentionally exposed to browsers.
Encryption. Production web traffic uses TLS. Hosting and database providers manage encryption for stored infrastructure data according to their platform controls.
Application security. API input and file checks, rate limits, authorization gates, tenant scoping, security headers, signed or secret-authenticated webhooks, and replay/idempotency controls reduce common abuse paths.
Resilient processing. Webhook work uses a durable database queue with bounded retries, exponential backoff, deduplication, and dead-letter status rather than relying only on one serverless request.
Logging and monitoring. Structured operational events, request identifiers, error monitoring, health checks, and scheduled diagnostics support detection and investigation. Logs are designed to avoid raw transcripts and secrets.
Development controls. Changes are version controlled and tested through automated unit, security, AI-contract, build, dependency-audit, secret-scan, and end-to-end checks before release.
Vendor controls. Production providers are inventoried on the Subprocessor List. Customer-directed integrations can be disabled and access tokens should be limited to required scopes.
Continuity and deletion. Managed hosting and database infrastructure provide platform recovery capabilities. Durable jobs preserve pending work across serverless restarts. Customer-content deletion remains subject to backup cycles and legal retention.
Shared customer responsibilities
- use unique credentials, protect email accounts, and promptly remove former users;
- grant only needed CRM, meeting, and billing permissions;
- obtain recording consent and avoid prohibited or unnecessary sensitive data;
- review AI Outputs and restrict exports to authorized recipients;
- keep source devices, meeting platforms, and connected systems secure; and
- report suspected incidents promptly.
Reporting a vulnerability or incident
Send a concise description, affected URL, reproduction steps, and contact information to hello@revenuecallout.com. Do not access other users' data, disrupt production, use automated high-volume testing, or publicly disclose an unresolved issue. We will acknowledge and triage good-faith reports.