Ask an engineering team whether they would upload their agent sessions to somebody else's server, and watch the pause. Sessions carry source, credentials that slipped into a paste, customer names, and the internal argument about whether to ship.
So there is no Motif cloud to opt out of. You run the server; it is one process and one SQLite file behind a reverse proxy. Redaction runs on the developer's machine before upload, with ten high-precision patterns on by default. The only outbound call the product can make is to the model provider you configure for memory, and that is off unless you turn it on.
The uncomfortable part is that the sensitivity is not obvious until you look. A session is not a diff. It contains the paths on your disk, the environment variable you pasted while debugging, the customer name in the failing test fixture, and the sentence where someone said the vendor contract is a problem. None of that is in the repository, and all of it is in the history.
This is why the privacy model is not a setting page. Sessions arrive personal and stay that way until a project is deliberately marked team-visible, and that boundary is enforced on every read path on the server rather than only on the list you happen to see. Redaction runs before upload, on the machine that owns the session, because a secret that reaches the server has already leaked. Excluding a path can also withdraw what was sent before you thought to exclude it.
None of that would be worth much if you had to take our word for it. The server is one process and one SQLite file that you run; the code is Apache-2.0; there is no telemetry and nothing phones home. The only outbound call the product can make is to the model provider you configure yourself for session memory, and that feature is off until you turn it on.