Skip to content
RUBI

Security and retention

What engineers and DPOs ask before connecting Rubi, answered precisely.

Retention#

DataDefaultSetting
Sessions, transcripts, reports60 daysretention_days
Video and audio recordings30 daysstream_retention_days

Both are configurable per organization in Settings. When a recording expires its media is purged and the track status becomes purged. Archiving an interview preserves its report and recordings until their retention periods end.

Media access#

  • Recordings are transferred securely and require authorized playback access.
  • POST /v1/interviews/{id}/playback returns short lived URLs with expires_at and refresh_after_ms. A leaked URL stops working within minutes.
  • Share links are opt in, expire, and can be revoked at any time.

Isolation and encryption#

  • Data is isolated by organization. API keys cannot cross tenants, and learning memory is per organization.
  • Data is encrypted in transit and at rest, including recordings and integration credentials.
  • API keys are never stored in plain text. Webhook secrets and integration keys are only displayed on creation.

Integrations#

Connectors are read only and use HTTPS base URLs only. Restrict access to Rubi's egress ranges, and rotate your key at any time by pasting the new value in the dashboard.

Audit#

The audit log records actions by users, API keys, the system and traders with the entity, metadata, IP and time. Read it in the dashboard or with the audit:read scope.

See the security overview for data protection and subprocessor information.