Skip to content
A ruby held inside an obsidian vault lit by thin red lines
Security

Faces, voices and funds. Handled like it matters.

Rubi records the most sensitive moment of your relationship with a trader. Learn how that data moves, how we protect it and when it disappears.

01Your data

Protected at every step.

  1. Interview

    The trader shares their webcam, microphone and screen through an encrypted connection.

    With consent
  2. Access controls

    Access is authenticated, limited to your organization and recorded in the audit log.

    Firm access only
  3. Report

    Interview answers and trading activity are reviewed together to prepare your report.

    Within your workspace
  4. Recordings

    Recordings stay encrypted and playback access expires in minutes.

    Protected access
  5. Your team

    Reviews in the dashboard with role based permissions.

    Your decision
02Controls

What protects your data

Encryption in transit

Connections are encrypted across Rubi. Integrations require secure connections.

Encryption at rest

Stored data, backups, recordings and integration credentials are encrypted. API keys are never stored in plain text.

Tenant isolation

Data and access stay within your organization. Learning memory is built per firm and never mixed.

Least privilege

Four roles and sixteen permissions. API keys only carry the scopes you grant and can never manage members, keys or billing.

Signed media

Recordings are served through short lived signed URLs. Share links are opt in, time boxed and revocable.

Audit log

Actions by users, API keys, the system and traders, with the entity, metadata, IP and time, filterable and exportable.

03Retention

You choose how long we remember.

Retention is configurable per organization. When a period ends, media is purged and the session record goes with it. Deleting an interview removes it immediately.

60 days

Sessions, transcripts and reports by default

30 days

Video and audio recordings by default

04Data processing

Services that support Rubi

Rubi uses external service providers for the operations below. We notify customers before adding a subprocessor that handles interview data.

ServicePurpose
Service availabilityKeeping interviews and the dashboard accessible
Data retentionSecurely retaining your records for the period you choose
RecordingsSecure recording access and playback
Interview analysisInterview questions, reports and chart reviews
SpeechSpoken interviews, transcripts and captions
Live avatarOptional visual interviewer
AuthenticationDashboard authentication and organizations

Running a security review?

Write to security@rubikyt.com for our current subprocessor list, data processing details, questionnaire answers and DPA.

Security details