DataMind Oda keeps your work on this computer, and everything it sends goes to your company's DataMind server. This page covers the account Oda uses, when it refuses a server, where its data lives, and how it updates itself.
Settings > DataMind account shows your user, your company and the server Oda is signed in to. From there, Change server points Oda at a different DataMind address, and Log out signs you out.
Sign-in always happens in your usual browser, so your company's single sign-on and device-compliance policies apply exactly as they do for any other company page. See Install and sign in for the first sign-in, and Your DataMind account and server for what each account action does.
The first time you point Oda at a server, Oda checks the address before the sign-in starts. One of three checks can refuse it, each with its own message:
There is no certificate bypass: Oda does not connect to a server it cannot verify. When a refusal appears, the message on screen says which case it is; Troubleshooting lists the messages and what to do.
Oda keeps your work on your computer.
Every network call DataMind Oda makes goes to the server you signed in to, and nowhere else. That includes the server check on first run, the sign-in, chat and model calls, web search and page reading, the company data tools, and update checks and downloads.
No request goes to any other origin, and the app sends no telemetry of its own. If your company turns on anonymous usage reporting, Usage reporting and the installation id describes what that sends.
DataMind Oda updates from your company's server, not from an outside update service. That server publishes the installer and the version details Oda checks, so your company controls which version you get.
Oda never installs an update while a task is running. To check for an update yourself, or when one will not install, see Update DataMind Oda.
On the first run, Oda checks the server before the sign-in starts. It refuses an address that is not a DataMind server, a server that needs a newer version of DataMind Oda, and a certificate this computer does not trust. Check the DataMind URL you copied from your company's DataMind OS; Troubleshooting has the message for each case and what to do.
No. There is no certificate bypass: Oda does not connect to a server whose certificate this computer cannot verify. Ask your administrator to make the certificate trusted on your computer.
Sign-in opens in your usual browser, so your company's single sign-on and device-compliance policies apply exactly as they do for any other company page. When you finish, you return to Oda signed in.
Yes. The credential Oda saves is protected by Windows data protection, in your Windows app-data folder. The short-lived credential used while Oda runs stays in memory only.
No. Every network call the app makes goes to your company's server: the sign-in, chat and models, web search and page reading, the company data tools, and updates. The app sends no telemetry of its own; the only reporting is the anonymous usage reporting your company can turn on, described in Usage reporting and the installation id.
Your company's server. Oda takes updates from the DataMind server you signed in to; that server publishes the installer and the version details, never an outside update service.
No. Oda never installs an update while a task is running. If you want to stop a task first, see Chat with Oda; for the full update flow, see Update DataMind Oda.
No. Oda keeps to its own home folder; the home folder of another installation, even an older one, is not read.