Security
Interview audio is the sensitive asset.
Written for InfoSec, legal and delivery leadership: how a recording moves, what guards it at each step, and what isn’t in place yet. No compliance theatre.
At a glance
- Isolation
- Row-level, per organization
- In transit
- TLS 1.3
- At rest
- AES-256, private storage
- Training on your data
- Never
Found something? Write to security@oneloop.work. Acknowledged within one business day.
01The data flow
Follow one recording, end to end.
Eight stops from the meeting tab to the audit log. The browser keeps it first, and nothing after that is reachable without a signed request.
Meeting tab
Meet, Teams, Zoom web
Audio is captured from the browser tab the round runs in. No bot joins the call and nothing is installed on the meeting.
stored first
Local store
IndexedDB
Every take lands in the browser before any upload starts, so a dropped connection never costs a recording.
TLS 1.3
Ingest API
Verified receipt
Segments arrive numbered and SHA-256 hashed through an idempotent retry queue. A missing segment is flagged, never papered over.
AES-256
Private storage
No public bucket
Audio rests encrypted in private object storage. It is reached only through short-lived signed URLs the API issues after an access check.
signed URL
Speech-to-text
No database keys
Transcription runs in its own worker that holds no database credentials, on OneLoop compute or, on Enterprise, inside your network.
transcript
Scoring
Zero retention
Competency scoring runs under zero-data-retention terms that forbid training on your transcripts. Every score carries the quote behind it.
evidence
Your workspace
Row-level security
Every row carries its organization, and the database clamps every query to the signed-in one. Playback is a signed link that expires.
logged
Audit log
Exports as CSV
Deletions, restores, retention and role changes are written as they happen. Taking the export is logged too.
02Controls
Enforced underneath, not promised on top.
Each control lives in the database, the storage layer or a contract, where a bug in the screen can’t switch it off.
- 01
Tenant isolation in the database
Every business row carries an organization id that cannot change, and row-level security clamps every query to the signed-in organization.
org_id = current_org_id()
- 02
Encrypted both ways
TLS 1.3 from the extension to every service. Audio, transcripts and the database rest under AES-256.
TLS 1.3 · AES-256
- 03
Links that expire
Audio tables have no client-readable policy at all. Playback and download go through signed URLs issued after an access check.
Signed, short-lived
- 04
Local-first capture
Takes are written to the browser before upload and retried until the server confirms receipt. A flaky network costs time, never audio.
IndexedDB, then upload
- 05
Every segment accounted for
Segments are numbered in order and hashed with SHA-256, so a gap or a changed byte shows up loudly instead of shifting timestamps.
Sequence + SHA-256
- 06
Never used for training
Scoring runs under zero-data-retention terms that contractually forbid training on your transcripts, rubrics or notes.
Zero data retention
- 07
Roles as data
Permissions are rows, not code. A firm can model its own roles and scope a grant to one organization or the whole tenant.
Scoped grants
- 08
Retention you set
Audio, transcripts and whole interviews each get their own window. A server-side sweeper enforces it, so the setting is not a suggestion.
Enforced server-side
- 09
A log for every change
Deletions, restores, retention and role changes are written to an audit log the owner reads in Settings and exports as CSV.
Exports are logged too
03Retention and deletion
You set the clock. The server keeps it.
The workspace owner sets a window per data type. Dropping audio keeps the transcript, scores and quotes; dropping a transcript keeps the scores and the quotes behind them.
Settings, Privacy, Retention
Interview audio
30 days to a year
Transcript, scores and quotes stay
Transcripts
90 days to two years
Scores and the quotes behind them stay
Whole interviews
One to three years
Everything goes, on the same day
Live
In every list, report and reminder.
Recently deleted
30 daysHidden everywhere for 30 days, restorable with its recording, transcript and scores.
Removed for good
Storage included. This step cannot be undone.
04Residency and sub-processors
One region, named in your contract.
Audio, transcripts and scores live in one hosting region, named in your contract. Picking a region per organization isn’t available yet. On Enterprise, transcription can run inside your own network, which for most firms is the deciding answer rather than the region flag.
The current list is issued with the DPA and named in your contract. The categories do not change:
- Cloud hosting
- Application, API and database hostingNamed at contract
- Object storage
- Encrypted interview audio at restNamed at contract
- Speech-to-text
- Transcription computeYours on Enterprise, OneLoop’s otherwise
- Model provider
- Competency scoring, no-training contractNamed at contract
- Email delivery
- Assignment and notification emailNamed at contract
05Honest ledger
What isn’t here yet.
Most security pages in this category are a wall of badges. These are the open loops those pages leave out, and each one closes here the day it actually closes.
No SOC 2 report yet
OneLoop is pre-certification and won’t imply otherwise. Today you get this page, a questionnaire response and time with the people who wrote the code.
No penetration test report yet
Scheduled before the first Enterprise contract goes live. You get the report and the remediation list, not a summary of it.
Desktop meeting apps are out of scope
Capture is browser-tab based. If your client insists on the Teams desktop app, this does not work, and no setting changes that.
06Your review
Send your questionnaire.
We answer every line.
Book twenty minutes with the people who built the capture pipeline and the database policies. Bring the hard questions.