Updated · Markdown version

Security

Odrivyn keeps call content on your computer and sends it out only for the moment it takes to transcribe or answer. This page explains how that works and lists every provider that receives your data.

1. The desktop app

  • We write the app in Rust with Tauri. It uses the WebView2 engine that ships with Windows instead of bundling its own browser.
  • Windows keeps the app's window out of screen captures (display affinity WDA_EXCLUDEFROMCAPTURE), so screen shares and recordings do not show it.
  • The app stores transcripts, answers and recaps in a local database in %APPDATA%\Odrivyn. Protect it the way you protect the rest of your Windows account, for example with BitLocker.
  • The app keeps its sign-in credential in Windows Credential Manager and never stores your password.
  • We sign every installer and update. The app checks the signature against a public key built into it and refuses an update that does not match.

2. Signing in

You approve each computer from your browser with a short pairing code. The app never sees your password. Signing out in the app cancels that computer's approval on our side too.

3. Data in transit and at rest

  • Every connection between the app, our API and our providers uses TLS.
  • The app streams audio straight to AssemblyAI with a short-lived token that our API issues for one session.
  • Our database provider and storage provider encrypt data at rest.
  • Uploaded files are private. No public link points to them, and only our API can read them from storage.

4. Access to your data

  • Our API scopes every file and search to your account, or to your company when a file sits in its brain. A guessed file ID returns nothing.
  • Owners and admins manage people and the company brain; members cannot invite people or change roles.
  • Our logs record that a request happened, not the words of a call or the content of a file.

5. Reporting a problem

Send security issues to contact@odrivyn.com. We reply within two working days and credit reporters who want it.

6. Subprocessors

Every provider outside Odrivyn that processes your data, and what it receives.

ProviderReceivesPurposeLocation
AssemblyAIMeeting audioReceives meeting audio from the desktop app while you listen and returns the transcript, under its data processing terms.United States
OpenAIQuestions, transcript excerpts, screenshots you send, file passagesWrites answers, recaps and practice questions when you choose the OpenAI answer model (the default).United States
Google (Gemini)Questions, transcript excerpts, file textWrites answers when you choose the Gemini model, turns your files into search vectors, and reads scanned pages (OCR).United States
OpenRouterQuestions and transcript excerptsCarries Gemini requests when we route them through OpenRouter instead of calling Google.United States
Brave SearchSearch queriesRuns a web search when a typed question needs information that is not in your files.United States
ApifyWeb addresses you addReads the web pages you add as material.European Union
Cloudflare (R2)Files you uploadStores the original files you upload and the signed desktop installers.Global (Cloudflare network)
NeonAccount, company and file-index dataHosts our Postgres database: accounts, companies, usage counts, and the text passages and search vectors of your files.United States
VercelRequests to our website and APIHosts the website and API, and measures page performance with cookie-free Web Analytics and Speed Insights.United States
UpstashRate-limit countersCounts requests per account for a few minutes to stop abuse.United States
AblyDocument and release identifiersTells your desktop app when a web page finished reading or an update is ready. It carries no file content.United States
StripePayment and billing detailsTakes payments and manages subscriptions. We never see your card number.European Union and United States
ResendYour email address and nameSends account, billing and invitation emails.United States

See also: Privacy policy · Terms of service