Product telemetry is DataMind Oda's optional export of usage events: small reports about how the app is used. This page covers what an event may carry, how sending behaves, what happens when Oda quits, and the chat copies your feedback can release.
Telemetry is off until your company turns it on
No destination by default. DataMind Oda comes with no telemetry destination, so there is nowhere for events to go and nothing is collected. Turning telemetry on means naming a destination for the events; none comes with the app.
Nothing is collected on its own. The export collects nothing by itself: each event is submitted by the feature that is built to report it, and the export never scans your work for facts.
A setup choice, not a chat choice. There is no telemetry switch in Oda's Settings. The choice belongs to the setup of the copy of Oda on this computer, and it looks the same from inside every chat.
What an event can carry
An event is prepared where the usage fact happens, and it carries only what was selected for it.
A summary and simple values. A short text summary of the fact, when it happened, and simple values such as numbers, short text, or yes and no.
Not your work. Prompts, answers, file contents and credentials are not part of an event by design, and the export reads nothing on its own: no chats, no account details and no device identifiers.
No filtering on the way out. Oda does not strip or rewrite an event as it leaves; what an event may include is settled when it is prepared.
Not about a person. An event can carry the installation's anonymous id, so records from one installation line up, and never anything that identifies you. Usage reporting and the installation id explains that id and how to reset it.
Sending is best effort
Off to the side. Oda sends events in small batches on a short delay while the export is on. Sending never runs inside your turn, and a failed send is noted locally instead of holding your work up.
In memory only. Waiting events live in memory. If they cannot be sent, they are dropped: there is no outbox, no later retry and no catch-up at the next start.
No receipt. A handover to the queue is not a confirmation that the destination received the event. Delivery is best effort and never guaranteed, and no acknowledgement comes back to the app.
Quitting with telemetry on
A bounded wait. When you quit DataMind Oda, it stops sending and gives the events still waiting a short chance to leave. By default, that wait lasts no longer than 21 seconds.
An unreachable destination uses it up. If the destination cannot be reached, quitting can take that long, and whatever is still waiting when the wait ends is lost.
Chat copies released by feedback
Feedback is its own channel. When you leave feedback in a chat, DataMind Oda can send a copy of that chat's record to your company's collector, and only new feedback releases that copy. How to leave feedback, from reply ratings to the /feedback command, is on Feedback.
Two settings. Uploading is set for this installation, not per chat: off, or feedback-only, which is the usual setting. There is no setting that shares a chat without feedback.
When uploading is off. Nothing is sent, and Oda notes it locally when you record feedback: OpenTelemetry session upload is DISABLED; this feedback is not uploaded through OpenTelemetry.
What releases a copy. A remark, a dialog submission, a rating or its note that you add or change, or a rating you remove: each counts as new feedback. Asking questions, opening or restoring a chat, or reloading a part of Oda does not release a copy on its own.
Everything not yet sent. A release covers the part of the record that has not left yet, up to and including the feedback itself. What comes after it waits for the next feedback.
Branched chats. Feedback a chat inherited from the chat it branched from does not release it; new feedback left in the branch does, and it also covers what the branch inherited. See Edit, rewind and retry.
The same for every model. A release works the same whichever model and provider the chat uses.
A released copy is the chat's record as it is: your messages and Oda's answers, the arguments and results of its tool calls, the instructions it works under and the definitions of its tools, its to-do list and the summaries Oda writes when a long chat is shortened, the feedback text itself, and the folder the chat works in.
Credentials. Oda's own stored model credentials are never part of a copy. Anything that appears in the conversation itself is included, such as a password typed into a message.
Sharing rules. Oda itself adds no cleaning rules. Before a record leaves, it passes through any sharing rules set up for this Oda, and a rule can withhold a record from leaving. Rules act on the copy only: the chat saved on your computer is never changed.
Sending. Records are sent in the background while the chat runs, straight to the collector your company set up, not in the requests your chats make. Sending is best effort: a record still waiting when Oda stops can be lost, and a record that arrives twice is counted once.
Telemetry and Oda's other records
Separate from the request log. Your company's DataMind OS records Oda's requests in its own log; product telemetry is a different record. Manage DataMind Oda for your company describes that log.
Separate from feedback. Feedback you leave about a chat is its own channel and leaves only under its own upload rules, described above.
Separate from chat logging. The log part that rides a chat's requests is covered on Chat logging.
Usage reporting. What Oda may report about your installation when reporting is on, and how the installation id behaves, is on Usage reporting and the installation id.
Questions, answered
Can I turn telemetry on or off myself?
No. There is no telemetry switch in Oda, and nothing in a chat changes it. It is off until the copy of Oda on this computer is set up with a destination for the events.
Does Oda read my chats to build telemetry events?
No. An event is prepared by the feature that reports it, and the export reads no chats, no account details, no credentials and no device identifiers of its own.
Can an event contain my messages, files or credentials?
By design, no: an event carries a short text summary of the usage fact, when it happened, and simple values; your messages, files and credentials are not part of them. The export itself does not filter an event on the way out, so what an event may include is settled when it is prepared.
Do telemetry events identify me?
They can identify the installation through Oda's anonymous id; they never identify a person. The id is random, holds no account or hardware details, and ids from different computers are not joined. Usage reporting and the installation id explains it.
Can telemetry slow down my work?
No. Sending happens off to the side and never inside your turn, and an event that cannot be sent is dropped rather than kept, so nothing waits on the network while you work.
Can telemetry delay quitting DataMind Oda?
Usually not: quitting drains what is waiting and closes quickly. If the destination cannot be reached, Oda waits only for a bounded time, no longer than 21 seconds by default, and then drops what is left.
Where do telemetry events go?
To the destination your company sets up for them, and nowhere else. Oda has no telemetry destination of its own.
Is product telemetry the same as the feedback I send?
No. Feedback is something you leave about a chat on purpose; product telemetry is the optional usage-event export. They are separate channels; Chat copies released by feedback covers the feedback side.
Can uploading send more than my feedback releases?
No. Uploading is set either off or to feedback-only, and even with it on, a copy leaves only when you leave new feedback. There is no setting that shares a chat without feedback.
If I keep chatting after leaving feedback, does the new part follow?
No. A release stops at the feedback that triggered it: it covers everything up to and including that feedback, and what comes after it waits for the next feedback.
Does removing a rating undo what has left?
No. Removing a rating counts as new feedback, so it can release the part not yet sent, and it does not erase a copy that has already left.