Skip to content
Security

Faces, voices and funds. Handled like it matters.

Rubi records the most sensitive moment of your relationship with a trader. Here is exactly how that data moves, where it lives and when it disappears.

01Architecture and data flow

Five hops, all encrypted.

  1. Trader browser

    Webcam, microphone and screen recorded in 10 s chunks, uploaded over TLS to presigned URLs.

    interview.rubikyt.com
  2. Rubi API

    Authenticates every call, scopes it to your organization, writes the audit log.

    api.rubikyt.com
  3. Workers

    Assemble media, transcribe, run deterministic floors and the AI report.

    private network
  4. Storage and streaming

    Encrypted object storage, signed playback that expires in minutes.

    Cloudflare
  5. Your team

    Reviews in the dashboard with role based permissions.

    cockpit.rubikyt.com
02Controls

What protects your data

Encryption in transit

TLS 1.2 or later on every surface, HSTS preloaded on our domains. Connectors refuse non HTTPS base URLs.

Encryption at rest

Databases, backups, object storage and integration credentials are encrypted at rest. API keys are stored as SHA-256 hashes.

Tenant isolation

Every record carries its organization and every query is scoped to it. The AI 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

04Subprocessors

Who helps us run Rubi

We notify customers before adding a subprocessor that handles interview data.

ProviderPurpose
RenderApplication hosting and background workers
NeonManaged Postgres database
CloudflareObject storage, video streaming, CDN and DDoS protection
AnthropicLanguage model for the interviewer and the report
OpenAISpeech to text and text to speech
GoogleSpeech and chart analysis models
DeepgramCaption timing for recordings
SimliOptional live avatar for the interviewer
ClerkDashboard authentication and organizations

Running a security review?

Write to security@rubikyt.com for our questionnaire answers and DPA.

Technical details