Security and privacy
Customer conversations are sensitive. We treat them that way.
RepBrief handles recorded conversations with named individuals. Isolation, access control, and deletion are product features, not footnotes.
Tenant isolation
Every business record belongs to exactly one workspace. Access is enforced at the data layer against your memberships, not by hiding things in the interface. Switching workspaces changes every screen.
Encryption and access to audio
Audio is stored in a private bucket, encrypted in transit and at rest. Playback uses short-lived signed links generated for your session; there is no public URL for a recording.
Role-based access
Roles determine who can see recordings, review insights, configure a CRM connection, approve a sync, read the audit log, or change retention.
Retention and deletion
Set separate retention windows for audio, transcripts, and insights. Deletion is permanent, requires confirmation, and is recorded in the audit log.
Audit logging
Access, exports, shares, CRM writes, role changes, and deletions are logged with actor, time, resource, and outcome — including denied attempts.
Recording consent
RepBrief prompts for consent acknowledgement and records it, but recording law differs by jurisdiction and RepBrief does not make a recording lawful. Responsibility for consent stays with the person recording.
AI limitations
Model output can be wrong. Summaries, insights, and action items are labelled as AI generated, carry a confidence score, cite the transcript, and require human review before they are treated as agreed.